On Mon, 2009-03-30 at 22:54 +0200, Jan Rekorajski wrote:
Sorry for possible double post, I sent the first from wrong email.
Hi, Syslog-ng 3.0.1 dies on reload (kill -HUP pid) when config file contains log { destination { program() } } directive set. 100% repeatable.
Here are the relevant config lines:
destination d_sshguard { program("/usr/sbin/sshguard -a 6"); }; # A desperate experiment #destination d_sshguard { program("read"); };
log { source(s_sys); filter(f_authpriv); destination(d_sshguard); };
From what I managed to find with strace/ltrace, syslog-ng kills the program, does not clear some data structures and then falls face down with sigsegv/term/ill trying to restart/reattach(?) to the program.
The exact same configuration works perfectly with version 2.0.10.
Hm... I've just tried to reproduce this problem with current 3.0 HEAD and also 3.0.1, but without success. Can you show me a backtrace of the failing program? You can do it using: gdb syslog-ng core (gdb) bt -- Bazsi