This document provides troubleshooting information for LogListener 2.2.4 and earlier. For information on troubleshooting the latest version, see Server Group Exceptions.
An exception occurred with log collection, and the associated server group is found to be exceptional.
The heartbeat between the server group and the CLS system is interrupted, resulting in failure to collect and report logs. Possible causes for the server group exception include:
Troubleshoot problems according to the above causes.
Check whether the IP address added to the server group is correct.
cd loglistener/tools && ./check.sh
Check whether the network is connected by running the following command:
telnet <region>.cls.myqcloud.com 80
<region> is the abbreviation for the region where CLS resides. For more information on regions, see Available Regions.
The following code appears upon normal network connection. Otherwise, connection fails. Check the network and ensure normal connection.
Check whether LogListener processes are running normally. Go to the installation directory and run the following command:
cd loglistener/tools && ./p.sh
Normally, there are three processes:
bin/loglistenerm -d #Daemon process bin/loglistener --conf=etc/loglistener.conf #Main process bin/loglisteneru -u --conf=etc/loglistener.conf #Update process
If any process fails, restart it. Go to the installation directory and run the following command:
cd loglistener/tools && ./start.sh
See the following figure:
cd loglistener/etc && cat loglistener.conf