Evan Rempel <erempel@uvic.ca> writes:
We are seeing a different problem though. (happens on both 3.3.7 and 3.4.1 threaded and not threaded)
2013-02-06T23:59:05-08:00 kern.info kernel: syslog-ng[10913]: segfault at 7f819c000168 ip 00007f819c000168 sp 00007f81b33f5a48 error 15 2013-02-06T23:59:05-08:00 syslog.notice syslog-ng[7627]: Syslog connection closed; fd='13', client='AF_INET(142.104.47.145:51679)', local='AF_INET(127.0.0.1:1514)' 2013-02-06T23:59:05-08:00 daemon.crit supervise/syslog-ng[18771]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='11' [...] So there does not seem to be a memory leak, but obviously something goes wrong to get a segfault.
I can't trace this for 4-5 days, so how do we trouble shoot this?
If you could enable core dumps, and get a backtrace, that would help a lot to narrow down the issue. -- |8]