On Tue, Jan 13, 2009 at 8:03 AM, Rainer Gerhards <rgerha...@hq.adiscon.com> wrote: > I'd actually start with removing the $ActionQueue* directives, as they > cause additional asynchronizity. But the important thing is it first get > back to a state where we can (somewhat) reliably reproduce the bug. I > think we should see at least 3 aborts in a row before we do any changes. > The reason is that we otherwise do not know if the config changed caused > the situation to improve or that was just a random non-abort. That's the > issue I have run into all time so far...
Hello all, now this bug gets interesting... It has been over a week now since I reverted back to the original rsyslog version with remote logging activated and configuration file as it was originally when I had these crashes. Well... now there has been no problems although originally I had these crashes almost once a day. So currently I have been unable to reproduce this bug anymore. Could this bug had been caused by a bug in a library that rsyslog uses that would have been updated in the past week or so? Regards, Juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
