I have tweaked rsyslog. $SystemLogRateLimitInverval 2

$SystemLogRateLimitBurst 50 *.* /var/log/everything

and dropped down on my log level for slapd. I can already see rsyslog is not reporting as much and so far no imuxsock drops. I'll watch it over the next few days and post the results.

Thanks Nik..

Scot

On Fri, Oct 31, 2014 at 11:40 AM, Dominik George nik@naturalnet.de wrote:

Hi Scott,

...

Thanks for responding Nik. I have rsyslog 5.8.10-9 running but I do see the following....

rsyslogd-2177: imuxsock lost 426 messages from pid 17944 due to rate-limiting

This is repeated multiple times.

I guess that 17944 is the PID of your running slapd.

In this case, you are having the same issue as I once had - slapd will segfault sometimes when syslog drops its messages.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689025

Updatign to Debian wheeze fixes the issue.

-nik

--On Friday, October 31, 2014 4:30 PM -0500 Scot Hollingsworth scoth@rcsd.ms wrote:

Had another stop with slapd.  This time I changed  /etc/rsyslog.conf  $SystemLogRateLimitInterval 0

I'm not sure you think this is at all related to syslog. There's nothing you've provided that indicates any useful information at all to the cause, and a pointer to a random bug in Debian's bug tracker about a debian caused issue that was unrelated to OpenLDAP for the ancient version they had (2.4.31) that was *fixed* by updating to OpenLDAP 2.4.39, is likely to remain unrelated.

If you want to know *why* it's dying, enable core dumps, and provide a gdb backtrace.

--Quanah

--

Quanah Gibson-Mount Server Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration