N-central Troubleshooting
All ESXi Services Stale or Misconfigured, how to increase max thread count
Last Modified
Tue Mar 31 21:13 GMT 2020
Description
- All ESXi Services monitored by the probe are either in a stale or misconfigured state.
- Looking for steps on how to increase the maximum thread count
- All ESXi services are reporting stale or misconfigured, restarting probe responsible for services makes no difference
Environment
- N-able N-central
Solution
- Review number of ESXI services being monitored by the probe, ESXI services are fairly intensive and can easily overload a probe.
- NOTE: 300 - 400 ESXi services is a good number to use as a limit per probe.
- Before continuing, first remove the services for VMGuests if the client is in a clustered environment
- This is for the VMGuest services that would transition into a failed state if the VM migrates from one host to another
- If the client is monitoring via this method look at redeploying by following steps listed here
- Consider adding another probe to the environment to load balance the number of ESXi services between multiple probes
- If adding another probe is not possible, please contact support to discuss possibly increasing the number of threads the probe can use for ESXi monitoring.