Operational Defect Database
BugZero found this defect 1011 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1040277
Syslog-ng issue may cause logging to stop and possible reboot of a system
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP TMOS
Affected releases:
13.0.0
13.0.0 HF1
13.0.0 HF2
13.0.0 HF3
13.0.1
13.1.0
13.1.0.1
13.1.0.2
13.1.0.3
13.1.0.4
13.1.0.5
13.1.0.6
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1040277: Syslog-ng issue may cause logging to stop and possible reboot of a system ... A syslog-ng issue with remote logging to an invalid remote syslog server may lead to logging via syslog-ng to stop. ... For software version 13.1 only it may lead to BIG-IP unexpectedly rebooting due to host watchdog timeout, typically within hours to day or two after syslog-ng gets hung up. ... The cessation of logging happens at the time of the last 'Syslog connection broken' in /var/log/messages before reboot. ... That message will appear without a preceding 'Syslog connection established' just before it with same timestamp. ... At this time syslog-ng typically spins, using near 100% CPU. ... Very rarely syslog-ng hangs in a non-functional state. ... Invalid syslog-ng server configuration or broken connection from BIG-IP toward configured syslog-ng remote server. ... A server is configured as a remote syslog destination on the BIG-IP, but it or an intervening system responds to stream of...
