Is there any chance we could try this with the current v3-stable? Or, better yet, with the current v4? The reason I ask is that I have run some valgrind/DRD tests today, and that reminded me that 3.18 had a couple of "not so nice" sync primitive handlings. They should not be the issue, but it is pretty hard to use valgrind on that version. So I'll focus troubleshooting on v4. It may be that I will not be able to backport a fix, once I find it (but it is still too early to think about the details ... let's find it first ;)).
Rainer > -----Original Message----- > From: Juha Koho [mailto:jmcs...@gmail.com] > Sent: Sunday, January 25, 2009 10:32 AM > To: Michael Biebl > Cc: 509...@bugs.debian.org; Rainer Gerhards > Subject: Re: Bug#509292: rsyslog: random crashes with remote logging > > On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl <bi...@debian.org> > wrote: > > Rainer suspected atomic operations to be the root cause. This would > mean a > > problem in GCC at compile time. > > rsyslog basically depends on zlib1g and libc6. I don't expect zlib1g > to have any > > influence, so you might wanna check if libc6 has been updated on you > system. > > Just when I said I have had no problems... last night (not during cron > job) rsyslog had crashed in my client (last lines of syslog attacted). > > So I can still reproduce this bug. Do you want to be sure and wait for > another crash or do you want me to start be removing the $ActionQueue* > directives from configuration? > > Regards, > Juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
