On Thursday 29 January 2009 11:30:46 Michael Biebl wrote:
I've prepared packages which include this fix. They are available
from [1], but currently i386 only
Michael,
Are you intending to upload these packages to unstable?
One week to proposed lenny release and your package is still shown
Subject: Re: Bug#509292: rsyslog: random crashes with remote logging
Rainer Gerhards wrote:
Is there any chance we could try this with the current v3-stable?
Or,
better yet, with the current v4? The reason I ask is that I have run
some valgrind/DRD tests today, and that reminded me that 3.18 had
...@bugs.debian.org
Subject: Bug#509292: rsyslog: random crashes with remote logging
OK, thanks to the help of Lorenzo Catucci, I was able to pinpoint one
problem that can cause a race. I will write up the details soon, but
this requires some time ;) I think I have a fix for the debian_lenny
branch
Cc: Juha Koho; 509...@bugs.debian.org
Subject: Bug#509292: rsyslog: random crashes with remote logging
OK, thanks to the help of Lorenzo Catucci, I was able to pinpoint one
problem that can cause a race. I will write up the details soon, but
this requires some time ;) I think I have a fix
...@gmail.com]
Sent: Sunday, January 25, 2009 10:32 AM
To: Michael Biebl
Cc: 509...@bugs.debian.org; Rainer Gerhards
Subject: Re: Bug#509292: rsyslog: random crashes with remote logging
On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl bi...@debian.org
wrote:
Rainer suspected atomic operations
Rainer Gerhards wrote:
Is there any chance we could try this with the current v3-stable? Or,
better yet, with the current v4? The reason I ask is that I have run
some valgrind/DRD tests today, and that reminded me that 3.18 had a
couple of not so nice sync primitive handlings. They should not
On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl bi...@debian.org wrote:
Rainer suspected atomic operations to be the root cause. This would mean a
problem in GCC at compile time.
rsyslog basically depends on zlib1g and libc6. I don't expect zlib1g to have
any
influence, so you might wanna
-Original Message-
From: Juha Koho [mailto:jmcs...@gmail.com]
Sent: Sunday, January 25, 2009 10:32 AM
To: Michael Biebl
Cc: 509...@bugs.debian.org; Rainer Gerhards
Subject: Re: Bug#509292: rsyslog: random crashes with remote logging
On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl bi
On Tue, Jan 13, 2009 at 8:03 AM, Rainer Gerhards
rgerha...@hq.adiscon.com wrote:
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
Juha Koho wrote:
Could this bug had been caused by a bug in a library that rsyslog uses
that would have been updated in the past week or so?
Rainer suspected atomic operations to be the root cause. This would mean a
problem in GCC at compile time.
rsyslog basically depends on zlib1g and
On Wed, Jan 14, 2009 at 9:40 AM, Michael Biebl bi...@debian.org wrote:
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
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
Juha,
I have finally been able to review the material that came with this bug
report. Thanks for all the good info, but it looks everything was
related to the $AllowedSender bug, not to the race condition (which I,
too, think exists).
... more inline below...
On Sat, 2009-01-10 at 20:12 +0200,
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
Rainer Gerhards wrote:
Juha,
I have finally been able to review the material that came with this bug
report. Thanks for all the good info, but it looks everything was
related to the $AllowedSender bug, not to the race condition (which I,
too, think exists).
... more inline below...
On
clone 509292 -1
retitle -1 rsyslog: segfault on reload when using $AllowedSender
thanks
Juha Koho wrote:
On Sat, Jan 10, 2009 at 8:14 AM, Michael Biebl bi...@debian.org wrote:
So we have two issues here:
1.) The segfault on reload (triggered by cron) when using
$AllowedSender. The following
On Sat, Jan 10, 2009 at 8:14 AM, Michael Biebl bi...@debian.org wrote:
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
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
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,
Juha Koho wrote:
Hello again,
now I manually ran rsyslogd reload in the server and I managed to
crash rsyslog and here's the last lines of the debug output. Hopefully
this helps. This happened when I just ran /etc/init.d/rsyslogd
reload.
Hi Juha,
I can reproduce this segfault when I use
Hello again,
now I manually ran rsyslogd reload in the server and I managed to
crash rsyslog and here's the last lines of the debug output. Hopefully
this helps. This happened when I just ran /etc/init.d/rsyslogd
reload.
Regards,
Juha
5596.889182006:main queue:Reg/w0: main queue: entering rate
Hello,
here's some more information regarding this bug. I had been running my
client which had previously crashed almost once a day for several days
in debug mode. Suddenly I noticed that rsyslog was running but no log
entries were written to any log files. I started to investigate the
case and I
Juha Koho wrote:
Hello,
here's some more information regarding this bug. I had been running my
client which had previously crashed almost once a day for several days
in debug mode. Suddenly I noticed that rsyslog was running but no log
entries were written to any log files. I started to
Michael Biebl wrote:
I've put Rainer, the upstream author on CC, please keep the CC on replies.
Rainer,
I forgot to mention, as you missed the initial bug report, that you can find the
complete log in the BTS at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509292
Cheers,
Michael
--
Why
Hello,
something strange happened now with my remote logging server after
compiling rsyslog with --enable-rtinst and running it in debug mode.
During last night the server had crashed completely; DHCP server
failed to give IP addresses and I was unable to log in via SSH or
access NFS shares. I
Michael Biebl bi...@debian.org wrote:
Could you try to run rsyslog in debug mode:
rsyslogd -c 3 -d
I have been running rsyslog in debug mode for a couple of days now
without problems. But... this morning my remote logging server had
crashed which has never happened before. Server has the
Hello,
now my remote logging server had crashed while doing rsyslogd reload
in a daily cron job. Client has been running fine since I started
running it in debug mode. I'll attach the debugging output just before
the crash.
Those $Action* and $WorkDirectory directives are not used in the
server
Juha Koho wrote:
Package: rsyslog
Version: 3.18.5-1
Severity: critical
Justification: causes serious data loss
Hello,
I have noticed that rsyslog randomly crashes with remote logging
(client) enabled. This happens almost once a day and all log messages
are lost until rsyslog is
28 matches
Mail list logo
