Hi Lorenzo, I've gone through the material once more. Indeed, it looks like the previous tests (with the #if 1) were not really useful. Sorry for that. Please let me know the outcome of this run here.
Also, I thought about one shot we may give it at reducing complexity. I am not sure if it works out, but if it does, that would be a big benefit. Could you please try the following: Use the master branch (the one you previously used). Reduce rsyslog.conf to just the necessary inputs (ideally only imuxsock) and a SINGLE file writer, no further actions. Let that run and tell us if it aborts, too. If it does, we have outruled a lot of code and we can focus much better in our troubleshooting. On my box, I unfortunately had no success yet in reproducing the issue - even though I put a lot of stress on the machine. Will be trying more today, hopefully that brings up some results... Rainer On Fri, 2009-01-16 at 18:17 +0100, Lorenzo M. Catucci wrote: > On Fri, 16 Jan 2009, Rainer Gerhards wrote: > > RG> OK, maybe we can simplify the config, that would remove code pathes > RG> from the potential bug candidate list. Could you comment out all the > RG> $ActionQueue* settings? > RG> > > I've just restored the #if 0 in runtime/msg.c; it seems the immediate > crashes came from those two lines. Now logging. > > Servus, > > lorenzo > > > +-------------------------+----------------------------------------------+ > | Lorenzo M. Catucci | Centro di Calcolo e Documentazione | > | [email protected] | Università degli Studi di Roma "Tor Vergata" | > | | Via O. Raimondo 18 ** I-00173 ROMA ** ITALY | > | Tel. +39 06 7259 2255 | Fax. +39 06 7259 2125 | > +-------------------------+----------------------------------------------+ > _______________________________________________ rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
