No. not using that setting. I need to set aside some tine to get some core dumps of the segmentation faults I get in 3.4.2, so I'm not too concerned with this report. I just wanted you to have it in case it was helpful. -- Evan Rempel -------- Original message -------- From: Gergely Nagy <algernon@balabit.hu> Date: To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] complete lockup of syslog-ng 3.4.1 Evan Rempel <erempel@uvic.ca> writes:
Just thought I would throw this into the pile.
I just had OSE 3.4.1 lock up - strace shows
root 17708 17707 12 Jun03 ? 21:32:39 /usr/local/sbin/syslog-ng --cfgfile=/usr/local/etc/syslog-ng/syslog-ng.server.conf --persist-file=/var/local/syslog-ng.server.persist --pidfile=/var/run/syslog-ng.server.pid --control=/var/local/syslog-ng.server.ctl % sudo strace 17708 strace: 17708: command not found % sudo strace -p 17708 Process 17708 attached - interrupt to quit futex(0x7fe338054594, FUTEX_WAIT_PRIVATE, 51979, NULL
Are you using suppress() in your config? If so, this is suspiciously similar to the bug we corrected in 3.4.2, with the following patch: https://github.com/balabit/syslog-ng-3.4/commit/8051f1436e6415da729361875b8b... -- |8] ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq