[syslog-ng] complete lockup of syslog-ng 3.4.1

[Balazs Scheidler]

Do you happen to have  suppress enabled? Or mark-mode changed from the
default? There's a fix in 3.4.2 for that.
On Jun 10, 2013 9:31 PM, "Evan Rempel" <erempel at uvic.ca> wrote:

>
> 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
>
>
> That's it.
>
> ______________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20130615/929b1ded/attachment.htm