Package: linux-2.6
Version: 2.6.32-9
Severity: critical
Justification: breaks the whole system
Hello,
I have the following setup in my system: 6 x 500GB drives with software RAID6 +
encryption (luks) + LVM. This is a new installation and I'm having troubles
with encryption. Every once and a whi
On Sat, Jan 24, 2009 at 3:06 PM, Michael Biebl 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 check if libc6
On Tue, Jan 13, 2009 at 8:03 AM, Rainer Gerhards
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
> think we should see
On Tue, Jan 13, 2009 at 2:02 AM, Michael Biebl wrote:
> Rainer Gerhards wrote:
>> In my lab, I could reproduce the issue (well, without an abort,
>> unfortunately, but valgrind showed problems). The valgrind run was clean
>> after the change. I would appreciate if you could verify in your
>> envir
On Wed, Jan 14, 2009 at 9:40 AM, Michael Biebl 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 remote
> logging.
On Tue, Jan 13, 2009 at 5:12 AM, Rainer Gerhards
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
On Sat, Jan 10, 2009 at 8:14 AM, Michael Biebl 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 testing/uns
On Sat, Jan 3, 2009 at 10:22 PM, Michael Biebl 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 lo
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,
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 hav
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
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 s
Michael Biebl 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 latest version
(3.18
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 started again. I don't know if th
14 matches
Mail list logo
