Juha, that's the problem with this bug, it is hard to reproduce. However, I made some progress recently and finally am able to reproduce it in my lab. I am currently posting updates on the progress via twitter at http://twitter.com/rgerhards in case you'd like to follow - and eventually add to - what I am doing (It's kind of problematic to broadcast all the details...).
So in short, I don't suggest anything at this stage. I am pretty confident, however, that removing the $ActionQueue mode will solve the issue for the time being, but of course at the cost of reduced functionality. 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
