Original Publication Date: 01/07/2013
Updated Date: 05/27/2016
The syslog-ng utility may cause high CPU utilization, resulting in a watchdog timeout and system reboot.
This issue occurs when the following conditions are met:
If there is a disruption in the communication with the remote syslog server, the syslog-ng utility will not attempt to re-establish the connection until the syslog-ng service is restarted.
The system may crash and traffic through the BIG-IP system may be disrupted.
As a result of this issue, you may encounter one or more of the following symptoms:
ps aux | grep syslog-ngFor example:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 6394 93.0 0.0 3308 1508 ? Ss 2012 0:02 /usr/sbin/syslog-ng -p /var/run/syslog-ng.pid
warning chmand: 012a0004:4: Host CPU subsystem reset caused by *** Super I/O watchdog timeout ***
F5 Product Development has assigned ID 387640 to this issue, and has confirmed that this issue exists in the products listed in the Applies To box. For information about releases or hotfixes that resolve this issue, refer to the following table:
|Type of Fix||Fixes Introduced In||Related Articles|
|Release||11.3.0||SOL2200: Most recent versions of F5 software|
|SOL9502: BIG-IP hotfix matrix|
You can mitigate this issue by ensuring that the remote syslog server is online and restarting the syslog-ng process, by typing the following command:
bigstart restart syslog-ng