Running  syslog-ng-3.5.4.1/ on CentOS 6.5 started seeing core dumps in var.log/kern approximately once per week.

The “supervising syslog-ng” process seems to restart everything so the problem is not really being noticed (except we have gaps, pauses during which logging for some systems is not occurring)

Here is /var/log/kern  from yesterday showing two process core dumps:

Feb 28 18:05:03 sl.its.uwo.ca kernel: syslog-ng[45160]: segfault at 0 ip 00007f0a767d0acc sp 00007f0a6fffca50 error 6 in libsyslog-ng-3.5.4.1.so[7f0a7679e000+8b000]

Feb 28 23:04:02 sl.its.uwo.ca kernel: syslog-ng[5442]: segfault at 0 ip 00007f0a767d0acc sp 00007f0a6fffca50 error 6 in libsyslog-ng-3.5.4.1.so[7f0a7679e000+8b000]

What is the approach I should use to investigate this (seemingly random) seg fault problem?

Dave Lacerte

UWO.ca