Troubleshooting Linux Collectors

We’ve compiled some helpful tips for troubleshooting common Linux Collector issues. Name Service Caching Daemon (NSCD) The LogicMonitor Collector makes DNS queries to resolve the hosts it is monitoring and to determine which LogicMonitor servers to report data to. If you are running an NSCD, you should make sure that it respects positive DNS TTLs. … Continued

Troubleshooting Windows Collectors

We’ve compiled some helpful tips for troubleshooting common Windows Collector issues. Error 1069 A common error encountered for Windows Collectors: Error 1069: The service did not start due to a logon failure. The account used to run the LogicMonitor Collector service on Windows must have “Log on as a service” rights on the host machine’s … Continued

Using the Collector Debug Facility

Overview You can use the Collector Debug Facility to remotely run debug commands on your Collector. This is helpful for troubleshooting issues with data collection and is typically used on the advice of LogicMonitor support. Note: The history of Collector debug commands is preserved in the Audit Log. Accessing the Collector Debug Facility There are … Continued

Restarting Collectors

When you need to restart a Collector, you can do so from within LogicMonitor or from the Collector host. Note: You can only use LogicMonitor to restart the Collector while it is up and running. If the Collector is down or dead, you will need to restart it from the Collector host. Restart from LogicMonitor … Continued

Restarting Collector

You can restart a collector from the LogicMonitor platform or from the collector host. When the collector is up and running, you can restart the collector from the LogicMonitor platform. If the collector is down or dead, you have to restart it from the collector host. Restarting from LogicMonitor Portal To restart a collector from … Continued