On Wed, 2 Sep 2009, Rainer Gerhards wrote: > David, > > thanks for this test. The outcome is obviously other than I > hoped/expected, but that makes it very useful. Obviously I have been > looking for the wrong root cause. > > Any abort information you can provide would be useful. Even more useful > would be if you could try out some earlier releases. Not sure if that is > possible from a feature point of view. > > If it is, I would appreciate if you could give v3-stable a try and, if > and only if that fails, too, checkout v3.18.6 and try that one. The > 3.18.6 is the version that Debian ships and so I know it has a lot of > testers and received a lot of bug-finding attention (I thankfully > receive lots of very qualified bug reports from the Debian > community :)). > > Please let me know what is possible. In any case, the 4.2.0 failure even > more points to environment-specific problems.
I haven't gone back to the 3.x series, but I did several more runs with 4.2.0 doing the folloiwng killall syslogd; tcpdump -n -s 0 -w rsyslog.sniff-10 -i eth0 & rsyslogd -c4 -x -d >rsyslog.debug-10 2>&1 ; killall tcpdump; syslogd -r -h ; mv /core /core-4.2.0-10 I have several complete steps, as well as several partial sets of data. I will gzip them and attempt to send them to you directly. David Lang > Rainer > > On Tue, 2009-09-01 at 18:11 -0700, [email protected] wrote: >> I got a core file with 4.2.0 >> >> I did git checkout -f v4.2.0 configure --enable-imfile and installed the >> result. >> >> I will go through the core file either later tonight or in the morning. >> >> in this case it did take a while for it to die. (over an hour) >> >> David Lang > > > _______________________________________________ > 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
