[syslog-ng] 3.0.3: Accessing unix-dgram source appears to break all logging
Markus Stalder
ms2 at lightupnet.de
Wed Aug 5 15:48:02 CEST 2009
Hello list,
my first post to the list, so hello everybody! :-) I'm on Ubuntu 8.04.2
amd64 and trying to upgrade from syslog-ng 2.0.9-1ubuntu1 to syslog-ng
3.0.3. I've both tried the on balabit.com provided amd64 .deb package and
also created an own amd64 .deb with the default settings in /debian using
dpkg buildpackage.
I have the following two sources in my config:
source s_all { internal(); unix-stream("/dev/log"); file("/proc/kmsg"
program_override("kernel: ")); };
source src { internal(); unix-dgram("/dev/log"); file("/proc/kmsg"
program_override("kernel: ")); };
Logging works just fine with the s_all source. However, as soon as I
access the src source, by, for example
destination temp_logfile { fifo("/tmp/.tivoli/.logfile."); };
log { source(src); destination(temp_logfile); };
all logging will cease. Meaning, other than
Aug 5 15:04:23 server syslog-ng[17505]: syslog-ng starting up;
version='3.0.3'
I'm not getting *anything* in my logs after restarting syslog-ng. If I
then comment destination temp_logfile ... again and restart syslog-ng,
logging works again.
The exact same config has worked just fine with 2.0.9-1ubuntu1.
Any idea what could be wrong here?
Thanks a lot!
Best regards
Markus
More information about the syslog-ng
mailing list