Package: syslog-ng
Version: 3.3.5-2
When executing the following command to reload the syslog-ng
configuration file:
# kill -HUP $(cat /var/run/syslog-ng.pid)
Duplicate logging issues can show up if a source is listed in the
configuration file but is not defined previously. The following log
definition would cause the issue:
# ... Other logs defined above.
log
{
source(s_sys_does_not_exist);
destination(d_sys);
};
When syslog-ng is sent a SIGHUP with the previous configurationin place,
the following errors are thrown to /var/log/messages(in duplicate)
Error in configuration, unresolved source reference;
source='s_sys_does_not_exist'
Error in configuration, unresolved source reference;
source='s_sys_does_not_exist'
Error initializing new configuration, reverting to old config;
Error initializing new configuration, reverting to old config;
At this point, all of the previously configured syslog-ng logs will be
sent in duplicate as well.This does not apply to just /var/log/messages
but every custom log defined.
If syslog-ng is sent SIGHUP a 2nd time without fixing the configuration
file,everything is logged 4 times (all at the same timestamp).
Error in configuration, unresolved source reference;
source='s_sys_does_not_exist'
Error in configuration, unresolved source reference;
source='s_sys_does_not_exist'
Error in configuration, unresolved source reference;
source='s_sys_does_not_exist'
Error in configuration, unresolved source reference;
source='s_sys_does_not_exist'
Error initializing new configuration, reverting to old config;
Error initializing new configuration, reverting to old config;
Error initializing new configuration, reverting to old config;
Error initializing new configuration, reverting to old config;
The original syntax error is not caught through the use of "syslog-ng
-s" but does prevent syslog-ng from starting if is stopped and then
restarted.
Expected behavior:
1. The error should not cause log messages to happen in duplicate.
Logging should continue identically to how it did before the SIGHUP was
issued.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
