On 2007-09-05, Jan-Frode Myklebust <[EMAIL PROTECTED]> wrote: > On 2007-09-04, Rainer Gerhards <[EMAIL PROTECTED]> wrote: >> >> I'd still appreciate if you could apply 1.19.4 and tell me the outcome. >> I am now working on fixing the root cause. That might take a short >> while, as I am thinking about the best *design* to fix the issue. > > OK, thanks. I've upgraded my loghost to 1.19.4 now, will let you > know if it fails again.
It failed again yesterday: *** glibc detected *** rsyslogd: corrupted double-linked list: 0xb7209028 *** ======= Backtrace: ========= /lib/libc.so.6[0x4152ce3e] /lib/libc.so.6(cfree+0x90)[0x415305d0] rsyslogd(MsgDestruct+0x73)[0x8057e93] rsyslogd[0x804de4a] rsyslogd(llExecFunc+0x3f)[0x805eb0f] rsyslogd[0x804d8aa] rsyslogd[0x804d9d7] /lib/libpthread.so.0[0x416112db] /lib/libc.so.6(clone+0x5e)[0x4159414e] I have "mon" monitoring that rsyslogd is running, and restart it when it fails. "mon" restarted rsyslogd twice (Thu Sep 6 20:38, and Fri Sep 7 03:27), but I can't find any backtrace from the second crash.. -jf _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
