[syslog-ng] [Bug 161] Syslog-ng stops processing after reload
bugzilla at bugzilla.balabit.com
bugzilla at bugzilla.balabit.com
Fri Feb 24 11:00:40 CET 2012
https://bugzilla.balabit.com/show_bug.cgi?id=161
--- Comment #1 from Balazs Scheidler <bazsi at balabit.hu> 2012-02-24 11:00:34 ---
Thanks for the detailed report.
hmm. the main thread is stuck during reload all the other threads are sitting idle.
The main thread is stuck in a call to writev() or is busy looping in writev(), and the core just happened to be within the kernel.
can you please check the arguments passed to the writev() call?
e.g. please issue the following commands:
(gdb) frame 1
(gdb) p *self
That should display the argument values passed to writev(). Thanks.
--
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the syslog-ng
mailing list