Control: found -1 3.3.5-4
Control: found -1 3.3.6-2
Cye Stoner <cye.sto...@echostar.com> writes:
> 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;
Thanks for the report, I reproduced it with the latest git master of
syslog-ng 3.3 too, so the problem applies to the latest 3.3 as well.
While I have not found a fix yet, I did notice two things:
* Fixing the configuration and reloading gets things back in order, no
matter how many times messages were duplicated before.
* Running in foreground with internal logs printed to stderr, the
problem does not appear.
I'll try to narrow this down, and provide a fix ASAP.
I'm using the following configuration to test with:
@version: 3.3
source s_internal {
internal();
};
destination d_all {
file("/tmp/all-messages.log");
};
log {
source(s_internal);
#source(s_does_not_exist);
destination(d_all);
};
--
|8]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
