Fixed
Created: Jul 29, 2013
Updated: Dec 3, 2018
Resolved Date: Dec 18, 2013
Previous ID: LIN3-21257
Found In Version: 6.0
Fix Version: 6.0.0.2
Severity: Severe
Applicable for: Wind River Linux 6
Component/s: Kernel
syslog-ng is run from two systems, one acts as the server and the other acts as the relay.
For example, there are two servers A and B, A is configured as syslog-ng server which receives every log from the syslog-ng client. syslog-ng in system B is configured to forward/relay every log to server A.
When the syslog-ng in system A is shutdown and log messages are sent from system B, the following warning message is seen in system B:
Jul 29 03:08:11 syslog-ng[31296]: I/O error occurred while writing; fd='9', error='Connection refused (146)'
Jul 29 03:08:11 syslog-ng[31296]: Syslog connection broken; fd='9', server='AF_INET(1.2.2.2:514)', time_reopen='10'
At system B, one can still run syslog(). When 2000 messages each of size 1000 bytes are sent, the syslog-ng's memory usage at system B increases and the memory is never freed. Memory usage observed is 1 MBytes per hour.
- Configure two syslog-ng servers (A & B),
- One (server A) receives every log from the syslog-ng client.
- The other (server B) forwards/relays every log to server A.
- Shutdown the syslog-ng in system A
- Send log messages from system B, the following warning message is seen in system B:
Jul 29 03:08:11 syslog-ng[31296]: I/O error occurred while writing; fd='9', error='Connection refused (146)'
Jul 29 03:08:11 syslog-ng[31296]: Syslog connection broken; fd='9', server='AF_INET(1.2.2.2:514)', time_reopen='10'
When 2000 messages each of size 1000 bytes are sent, the syslog-ng's memory usage at system B increases and the memory is never freed. Memory usage observed is 1 MBytes per hour.
