Bug #4127
closed
The rsyslog version > 5.7.1 drops messages if there is more than 200 messages in 5 seconds and could lead to 'No Answer' status of all nodes
Added by Matthieu CERDA about 11 years ago.
Updated about 11 years ago.
Category:
System techniques
Description
The rSyslog rate limiting bug fix is defined but not called in the Techniques.
In promises.st, the check_rsyslog_version bundle is defined but not included in the bundlesequence.
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/239
- Status changed from Pending technical review to Pending release
Applied in changeset policy-templates:commit:560d79d506303c0291c17fcd4389b9070b3f8cfb.
Applied in changeset policy-templates:commit:cd7009f1e405258f32ee15378ecaa641a1cffca4.
- Subject changed from The rSyslog rate limiting bug fix is defined but not called in the Techniques to The rSyslog version > 5.7.1 drops messages if there is more than 200 messages in 5 seconds and could lead to 'No Answer' status of all nodes
- Subject changed from The rSyslog version > 5.7.1 drops messages if there is more than 200 messages in 5 seconds and could lead to 'No Answer' status of all nodes to The rsyslog version > 5.7.1 drops messages if there is more than 200 messages in 5 seconds and could lead to 'No Answer' status of all nodes
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.9 which was released today.
Check out:
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by Jonathan CLARKE 
Updated by Nicolas PERRON