Project

General

Profile

Actions
Copy link

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 over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
1
Assignee:
Jonathan CLARKE
Category:
System techniques
Target version:
2.6.9
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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.

Actions
Copy link
 #1

Updated by Matthieu CERDA over 10 years ago

  • 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

PR available.

Actions
Copy link
 #2

Updated by Matthieu CERDA over 10 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset policy-templates:commit:560d79d506303c0291c17fcd4389b9070b3f8cfb.

Actions
Copy link
 #3

Updated by Jonathan CLARKE over 10 years ago

Applied in changeset policy-templates:commit:cd7009f1e405258f32ee15378ecaa641a1cffca4.

Actions
Copy link
 #4

Updated by Nicolas PERRON over 10 years ago

  • 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
Actions
Copy link
 #5

Updated by Nicolas PERRON over 10 years ago

  • 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
Actions
Copy link
 #6

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.9 which was released today.
Check out:

Actions
Copy link

Also available in: Atom PDF