[syslog-ng] [Bug 279] New: Syslog-ng central loging server seg fault gentoo

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=279

           Summary: Syslog-ng central loging server seg fault gentoo
           Product: syslog-ng
           Version: 3.4.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: hlavacek at gmx.com
Type of the Report: bug
   Estimated Hours: 0.0


Hello, 

we have set up the following topology: 
OS gentoo: 
Linux syslog1 3.8.12-hardened #1 SMP Wed Sep 18 16:30:57 CEST 2013 x86_64 Intel(R) Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux 

syslog: 
syslog server v3.4.7 and 40 syslog clients v3.x.x. 

problem: 
After a few days (5 or 10) server experienced segfault: 
[309942.605750] syslog-ng[17117]: segfault at 8 ip 00007fdb01e66609 sp 00007fdafe1ccac0 error 6 in libsyslog-ng-3.4.7.so[7fdb01e2b000+8f000] 

and then after two days with any error syslog-ng freezed in loop (cpu 100%), strace: 
futex(0x7fdc64009ca0, FUTEX_WAIT_PRIVATE, 2, NULL 


This scenario is being periodicaly repeated. We have faced this problem also with version 3.3 of syslog. 


BACKTRACE after segfault:
syslog1 run # gdb syslog-ng -c core.syslog.201422041822
GNU gdb (Gentoo 7.6.2 p1) 7.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/sbin/syslog-ng...(no debugging symbols found)...done.
[New LWP 26604]
[New LWP 24631]
[New LWP 1932]
[New LWP 1933]
[New LWP 1710]
[New LWP 1456]
[New LWP 1931]
[New LWP 1713]
[New LWP 1749]

warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `syslog-ng --enable-core -c /var/run/syslog-ng-remote.ctl --persist-file /var/li'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f03fdb44a59 in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
(gdb) bt full
#0  0x00007f03fdb44a59 in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#1  0x00007f03fdb44b6a in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#2  0x00007f03fdb4cf35 in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#3  0x00007f03fdb6d42b in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#4  0x00007f03fdb6c3c2 in iv_run_tasks () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#5  0x00007f03fdb6ee1b in iv_main () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#6  0x00007f03fdb6d21a in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#7  0x00007f03fdb6f736 in ?? () from /usr/lib64/libsyslog-ng-3.4.7.so
No symbol table info available.
#8  0x00007f03fd5bcbd8 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#9  0x00007f03fd2f7bbd in clone () from /lib64/libc.so.6
No symbol table info available.
(gdb)


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.