On 14/9/12 7:21 PM, Otto Rodusek wrote:
On 14/9/12 6:51 PM, Bernhard Voelker wrote:
On 09/12/2012 05:14 PM, Carlos E. R. wrote:
When I fetch mail with fetchmail, I see this:
<5.6> 2012-09-12 17:09:03 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:07 Telcontar rsyslogd-2177 - - - imuxsock lost 187 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:09 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:13 Telcontar rsyslogd-2177 - - - imuxsock lost 226 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:15 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:19 Telcontar rsyslogd-2177 - - - imuxsock lost 144 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:21 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:25 Telcontar rsyslogd-2177 - - - imuxsock lost 248 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:27 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:31 Telcontar rsyslogd-2177 - - - imuxsock lost 196 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:35 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:37 Telcontar rsyslogd-2177 - - - imuxsock lost 119 messages from pid 21238 due to rate-limiting
The PID is that of fetchmail. How can avoid that? Hi Carlos,
it's one point how to get rsyslogd to capture all messages, but instead of trying to tune rsyslogd like Per and Otto suggested, I'd try to find out why fetchmail is sending so much messages to the syslog. What are the actual messages?
Have a nice day, Berny Hi Berny,
Thanks for your good suggestion. In fact, that's exactly what I did in my case (not sure of Carlos situation) and changing to "$SystemLogRateLimitInterval 0" in /etc/rsyslog.conf got totally rid of the "imuxsock lost ??? messages from pid ????? due to rate-limiting" messages (none over the last 24 hrs or so) however I now get TONS of the following "rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable" !! Changing params in /etc/rsyslog.conf doesn't seem to help solve this either. I'm thinking there may be some issue in the version of rsyslogd that I'm using in 12.1:
# rsyslogd -v rsyslogd 5.8.5, compiled with: FEATURE_REGEXP: Yes FEATURE_LARGEFILE: No GSSAPI Kerberos 5 support: Yes FEATURE_DEBUG (debug build, slow code): No 32bit Atomic operations supported: Yes 64bit Atomic operations supported: No Runtime Instrumentation (slow code): No
See http://www.rsyslog.com for more information.
From the rsyslog.com website it seems this version (5.8.5) (my rpm is rsyslog-5.8.5-6.4.1.x86_64) is quite out of date. On my test server, 12.2 rsyslogd does not seem to exhibit these issues, so I will try to update my server to 12.2 (rsyslog-5.8.11-2.1.3.x86_64) next week and see if that resolves the issue. Doesn't seem serious, just irritating that logs fill up!!!
Again thanks for any advice.
Best regards. Otto. Quick update: On my test server running 12.2:
# rsyslogd -v rsyslogd 5.8.11, compiled with: FEATURE_REGEXP: Yes FEATURE_LARGEFILE: No GSSAPI Kerberos 5 support: Yes FEATURE_DEBUG (debug build, slow code): No 32bit Atomic operations supported: Yes 64bit Atomic operations supported: Yes Runtime Instrumentation (slow code): No See http://www.rsyslog.com for more information. This version has support for "64bit Atomic operations supported: Yes" whilst the 12.1 version does not - maybe that's where this issue lies as both my live and test servers are 64 bit, and hence I don't see the problem on the test server whilst I do on the live server. (It could also be because the load on the test server is minimal vs the live server - go figure!!) Best regards. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org