mirror of
https://github.com/Ylianst/MeshCentral.git
synced 2025-01-13 07:53:20 -05:00
agent debugging https://github.com/Ylianst/MeshCentral/issues/4284
This commit is contained in:
parent
a3719b2a78
commit
315a5a4209
@ -215,6 +215,37 @@ Then open your browser to http://localhost:9999 or whatever port you used.
|
||||
!!!note
|
||||
If you pause the debugger, and happen to forget about it, the agent will automatically kill itself and restart because it will think that a thread is stuck. Default debugger timeout is 10 minutes, you may find a log entry saved to disk saying "Microstack Thread STUCK", or something similar.
|
||||
|
||||
### Troubleshooting Agent connectivity
|
||||
|
||||
If an agent keeps disconnecting and reconnecting, add this line to the "settings" section of the config.json:
|
||||
|
||||
```
|
||||
"agentping": 30
|
||||
```
|
||||
|
||||
This will cause MeshCentral to "ping" the agent every 30 seconds and the agent to respond with a "pong" each time. That usually solves the issue however, it does generate more traffic. If that works, you can remove the line and try this line instead:
|
||||
|
||||
```
|
||||
"agentpong": 30
|
||||
```
|
||||
|
||||
This will cause MeshCentral to "pong" the agent every 30 seconds, the agent will not respond. This usually fixes the issue, but you have half the traffic. I would also increase the time like:
|
||||
|
||||
```
|
||||
"agentpong": 90
|
||||
```
|
||||
|
||||
This is the best, you have one way traffic to all agents every 90 seconds. The larger the number you can get away with the better.
|
||||
|
||||
If you ever get the same problem but on the browser side, you can also use one of these:
|
||||
|
||||
```
|
||||
"browserping": 30
|
||||
"browserpong": 30
|
||||
```
|
||||
|
||||
Same idea, browser side instead of agent side.
|
||||
|
||||
## Intel AMT
|
||||
|
||||
To debug issues, confirm that Intel AMT is active and there MeshCentral is not showing any red errors on the "Intel AMT" line:
|
||||
|
Loading…
Reference in New Issue
Block a user