Juha Koho schrieb: > On Sat, Jan 3, 2009 at 10:22 PM, Michael Biebl <bi...@debian.org> wrote: >> I can reproduce this segfault when I use the $AllowedSender directive in >> rsyslog.conf and reload rsyslogd. >> rsyslog is reloaded daily via the cron job, which might explain your regular >> crashes. >> >> Could you please verify, that you no longer get the crashes, if you remove >> the >> $AllowedSender directive, so I can be sure that we are on the same track. > > Hello Michael, > > yes I can confirm that you are on the same track. I removed this > directive because of the problem I mentioned earlier and now my server > has been up since that. > > However the original reason for this bug report was that my remote > logging client crashed randomly. Sometimes during normal operation and > not during reload and of course my client does not have the > AllowedSender directive. But for some reason my client has been > running fine since I recompiled rsyslog with more debugging output > (--enable-rtinst).
So we have two issues here: 1.) The segfault on reload (triggered by cron) when using $AllowedSender. The following forum entry is very likely about the same issue [1]. This issue is easily reproducible (with 3.18.6 from testing/unstable) 2.) Random crashes in the client when forwarding messages over UDP. I can't reproduce this problem myself and it's not yet clear, what is causing this crashes. Nevertheless, I think we should split up the bug report and deal with 1.) and 2.) separately as they don't seem to be related from what I can see. What's a it troubling is though, is that you can't reproduce 2.) anymore with --enable-rtinst. This makes me suspect that it is a timing/race condition. Cheers, Michael [1]http://kb.monitorware.com/viewtopic.php?f=34&t=8857 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
