On Tue, Jan 13, 2009 at 5:12 AM, Rainer Gerhards <rgerha...@hq.adiscon.com> wrote: > The primary question I have at this time is if you can reproduce the bug > without the $AllowedSender directive (or with the patch I created for > the cloned bug). If so, that would be a very good thing. From there, we
Hello Rainer, when I filed this bug report I didn't yet use the $AllowedSender directive in the server. I started to use it later on and then I discovered the reload problem. So I'm sure that this problem persists even when not using the $AllowedSender. And also note that this bug report actually applies to my _remote logging client_ and not my server (server is a dual core system). The $AllowedSender segfaults occured in my server (naturally I don't use this directive in the client...). > would need to change the config to see if it disappears if some settings > are changed (I am a bit sceptic about the async queue). That than could > lead us to the right path, even when not being able to apply any debug > settings. Oh - did I mention that the bug almost instantly disappears if > rsyslog is compiled for debugging. I initially thought that is an > artifact of limited concurrency due to debug calls, but now I tend to > believe that it actually is due to reduced speed - so on a 8-core system > we may have the issue even with debug mode (someone with a 8 way system > out there? ;)). I have been now running the recompiled version without -d option for few days and still no problems. Seems that when rsyslog is compiled with --enable-rtinst this problem disappears or at least happens very rarely. I think I need to revert back to the original version to reproduce this bug. Do you have any ideas what to try next? Regards, Juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
