On 2007-11-20, Peter Vrabec <[EMAIL PROTECTED]> wrote:
>
> This bug is my nightmare. I really don't know what to do. I run 2 syslogs in
> valgrind during a weekend. Sendind message via UDP on 64 architecture,
> messages generated every 1/3sec. RESULT: no segfault. :-(
I'd just like to again point out that we're seeing this regularly
on *32-bit* RHEL5. It's a quite heavily loaded server (1-2 GB udp-syslogs a
day), and it's been failing at these times:
Mon Sep 3 01:25:05 2007
Mon Sep 3 15:54:19 2007
Tue Sep 4 23:16:05 2007
Thu Sep 6 20:38:05 2007
Fri Sep 7 03:27:19 2007
Sat Sep 8 06:42:34 2007
Mon Sep 10 21:57:35 2007
Thu Sep 13 11:06:49 2007
Fri Sep 14 08:59:50 2007
Fri Sep 14 14:41:04 2007
Sat Sep 15 14:17:05 2007
Sun Sep 16 09:10:49 2007
Sun Sep 16 15:43:34 2007
Mon Sep 17 22:00:04 2007
Thu Sep 20 17:43:19 2007
Fri Sep 21 17:27:49 2007
Sun Sep 23 05:32:49 2007
Sun Sep 23 15:18:49 2007
Mon Sep 24 11:37:49 2007
Mon Sep 24 12:31:04 2007
Mon Sep 24 23:29:19 2007
# upgraded to rsyslog-1.19.8-1, running with MALLOC_CHECK_=2
Thu Sep 27 14:18:48 2007
Fri Sep 28 21:10:17 2007
Fri Oct 5 06:54:02 2007
Fri Oct 26 14:26:08 2007
Sun Nov 4 08:55:22 2007
Wed Nov 7 17:15:52 2007
Sat Nov 10 03:09:38 2007
Sat Nov 10 20:07:07 2007
So, with 1.19.8-1 it's gotten quite a bit better for us.
Unfortunately I haven't been able to get any core dumps,
even with DAEMON_COREFILE_LIMIT='unlimited' in
/etc/sysconfig/rsyslog and doing a "cd /var/log/syslog"
before starting rsyslogd in the init-script. Is there
anything else we need to do to get coredumps ?
-jf
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
