On 25.06.2014 15:53, Paulraj Samikannu wrote:
I see the following messages on the production server, any special log setting requirement or is our stunnel generating too many messages too fast?
Jun 25 06:13:35 pprccmfaap001 rsyslogd-2177: imuxsock begins to drop messages from pid 171059 due to rate-limiting Jun 25 06:15:34 pprccmfaap001 rsyslogd-2177: imuxsock lost 47 messages from pid 171059 due to rate-limiting
Can't comment on the specifics of stunnel, but rsyslogd brought rate limiting on the UNIX socket by default into a world where maintainers of daemons have never thought much about what *PID* may be attached to the messages they send to the syslog.
dovecot (logging per-connection messages through the master process all the time) and OpenVPN (dumping config, including the persisted assignment of pool IPs to clients, into syslog at startup) are the most affected software on my end, and yes, I happily raise the rate limit to whatever the former needs.
# grep -A 2 imuxsock /etc/rsyslog.conf $ModLoad imuxsock # provides support for local system logging (e.g. via logger command) $SystemLogRateLimitInterval 5 # Default: 5 (seconds) $SystemLogRateLimitBurst 1500 # Default: 200 (messages)
Regards, J. Bern