Jan-Frode Myklebust wrote: > v1.19.1 hasn't been totally stable for us on RHEL5.. I think it's crashed > a couple of times this week. Here's the latest log entry from the crash: > > *** glibc detected *** rsyslogd: corrupted double-linked list: 0xb3427a98 *** > ======= Backtrace: ========= > /lib/libc.so.6[0x4152cda9] > /lib/libc.so.6(cfree+0x90)[0x415305d0] > rsyslogd[0x804ddba] > rsyslogd(llExecFunc+0x3f)[0x805e86f] > rsyslogd[0x804d80a] > rsyslogd[0x804d938] > /lib/libpthread.so.0[0x416112db] > /lib/libc.so.6(clone+0x5e)[0x4159414e] > > Is there any tricks for getting a coredump ? I've started it with > unlimited core size now, in case it goes down again.. > Hi,
could you please provide some more info on your configuration? Configuration file, options used, log entries preceding the crash, ... If logging forwarded messages, is the remote logger also rsyslog? Does it use any templates? _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
