Project

General

Profile

Actions

Bug #3604

closed

When using rsyslog with a version > 5.7.1 on the server, some reports may be dropped, leading to NoAnswer on the server

Added by Nicolas CHARLES almost 11 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Rsyslog introduced a "rate limiting" feature in rsyslog 5.7.1 ( http://www.rsyslog.com/tag/rate-limiting/ )
So we can face log message like

imuxsock begins to drop messages from pid 30351 due to rate-limiting

along with incomplete reporting on the server.

A workaround ( ref http://www.gossamer-threads.com/lists/rsyslog/users/8513 ) is to add the config

$SystemLogRateLimitInterval 0

However, this should be added only for version that support it (I guess 5.7.1, but I couldn't find where it was introduced)

Actions

Also available in: Atom PDF