Bug ID 913849: Syslog-ng periodically logs nothing for 20 seconds

Last Modified: Aug 05, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 16.0.0

Opened: Jun 03, 2020
Severity: 3-Major

Symptoms

Once per minute, syslog-ng logs nothing for 20 seconds.

Impact

When using DNS names to specify remote syslog destinations and DNS is unreachable, syslog-ng re-attempts to resolve the name every 60 seconds. This resolution has a 20 seconds timeout, and blocks the syslog process from writing logs to disk during that time. Note that the logs are buffered, not lost, and will still be written to disk (with the correct timestamps) once the DNS query times out.

Conditions

-- A remote syslog server is specified by hostname, forcing syslog-ng to resolve it. -- the DNS resolution times out (for example, if the DNS server is unreachable)

Workaround

None.

Fix Information

None

Behavior Change