On Sat, 2006-10-21 at 19:44 +0600, Sergey N. Romanov wrote:
Hi there,
I have syslog-ng 2.0rc3 on FreeBSD 5.4.
From time to time I have problems. Syslog-ng dies with core dump.
This is output from gdb
NU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Core was generated by `syslog-ng'. Program terminated with signal 11, Segmentation fault. #0 log_writer_broken (self=0x820e080, notify_code=3) at logpipe.h:77 77 logpipe.h: No such file or directory. in logpipe.h (gdb) where #0 log_writer_broken (self=0x820e080, notify_code=3) at logpipe.h:77 #1 0x08051199 in log_writer_fd_dispatch (source=0x81f0540, callback=0, user_data=0x0) at logwriter.c:361 #2 0x0805b7b1 in g_main_context_dispatch () #3 0x0805cb76 in g_main_context_iterate () #4 0x0805cf5b in g_main_context_iteration () #5 0x080483ac in main_loop_run (cfg=0x81f1300) at main.c:162 #6 0x08048a8c in main (argc=0, argv=0x0) at main.c:420 (gdb)
In syslog-ng config I have some pipe sources. I have this problem after upgrade from 1.6 to 2.0rc3.
Any ideas why I have this problem and how to fix this?
One of the leak fixes in 2.0rc2 introduced the problem, 2.0rc1 should be safe and I'm working on a solution. -- Bazsi