No subject

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.

      </pre>
    </blockquote>
    <pre wrap="">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
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I can't get it to dump core unfortunately, all I get is:

# syslog-ng -f /etc/syslog-ng/syslog-ng.conf

Apr 15 11:25:25 sith syslog-ng[26571]: syslog-ng starting up; version='3.0.1'
Apr 15 11:25:25 sith sshguard[26576]: Started successfully [(a,p,s)=(6, 420, 1200)], now ready to scan.

# kill -HUP 26571

Apr 15 11:25:33 sith sshguard[26576]: Got exit signal, flushing blocked addresses and exiting...
Apr 15 11:25:33 sith sshguard[26576]: Run command "/usr/sbin/iptables -F sshguard ; /usr/sbin/ip6tables -F sshguard": exited 1.
Apr 15 11:25:33 sith syslog-ng[26571]: WARNING: Your configuration uses a newly introduced reserved word as identifier, please use a different name; keyword='syslog', filename='/etc/syslog-ng/syslog-ng.conf', line='77'
Apr 15 11:25:33 sith syslog-ng[26571]: Configuration reload request received, reloading configuration;
Apr 15 11:25:33 sith sshguard[26585]: Started successfully [(a,p,s)=(6, 420, 1200)], now ready to scan.
Apr 15 11:25:33 sith syslog-ng[26571]: Termination requested via signal, terminating;
Apr 15 11:25:33 sith sshguard[26585]: Got exit signal, flushing blocked addresses and exiting...
Apr 15 11:25:33 sith syslog-ng[26571]: syslog-ng shutting down; version='3.0.1'

Jan
  </pre>
</blockquote>
<br>
Hi,<br>
<br>
I also have tried to reproduce this issue but without success:<br>
<br>
Apr 23 19:52:42 pzolee-laptop syslog-ng[7281]: syslog-ng starting up;
version='3.0.1'<br>
Apr 23 19:52:42 pzolee-laptop sshguard[7283]: Started successfully
[(a,p,s)=(6, 420, 1200)], now ready to scan.<br>
Apr 23 19:52:58 pzolee-laptop pzolee: test message<br>
#kill -HUP 7281<br>
Apr 23 19:53:12 pzolee-laptop sshguard[7283]: Got exit signal, flushing
blocked addresses and exiting...<br>
Apr 23 19:53:12 pzolee-laptop syslog-ng[7281]: Configuration reload
request received, reloading configuration;<br>
Apr 23 19:53:12 pzolee-laptop sshguard[7304]: Started successfully
[(a,p,s)=(6, 420, 1200)], now ready to scan.<br>
Apr 23 19:53:12 pzolee-laptop sshguard[7283]: Run command
"/sbin/iptables -F sshguard ; /sbin/ip6tables -F sshguard": exited 1.<br>
Apr 23 19:53:16 pzolee-laptop pzolee: test message2<br>
<br>
I tested it with sshguard-1.4rc3.<br>
Could you tell me the version of your sshguard?<br>
It will be very useful to run syslog-ng with strace:<br>
strace -s 256 /opt/syslog-ng/sbin/syslog-ng -F<br>
<br>
Regards,<br>
Zoltan<br>
</body>
</html>

--------------050506040703070003020708--