On Wed, 2009-01-14 at 08:40 +0100, Michael Biebl wrote: > I don't think the $AllowedSender directive has any influence on the crashes > Juho > experiences on his rsyslog clients (as he only used those directive on the > rsyslog server). > Why do you suspect that the $AllowedSender fix might have an influence on > this?
I don't suspect it has - I was wrong ;) I think I was too-focussed on the quad core issue that I didn't even read the config correctly. I thought the crashes happened on the server. I now need to reevaluate the material - or maybe it is simpler if I just follow what happens now. > Then we have the random crashes on the client (tracked as #509292). Juho's > rsyslog.conf is at [1]. The only clue so far is, that it is related to multi > core machines (>= 4 cores). I'm not convinced that it is related to remote > logging. > Juho, could you strip down your rsyslog.conf step by step (i.e. first remove > the > remote logging, then the $ActionQueue* directives, then the imklog plugin, > then > the different rules), which will help us to narrow down this bug. 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... Rainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
