Bug #6421
closed
Messages can be dropped on the node, resulting in Unknown reports on the Web Interface
Added by Nicolas CHARLES over 9 years ago.
Updated over 2 years ago.
Category:
System integration
Description
Some rsyslog configuration contains by default the directive
$RepeatedMsgReduction on
This directive causes the messages that are identicals not to be sent. For instance, this is a by default directive on some Ubuntu ( http://serverfault.com/questions/30303/is-there-a-way-to-remove-last-message-repeated-x-times-from-logs ) (happens on Ubuntu 12.04 with rsyslog 5.8.6-1ubuntu8.9)
Techniques should probably check for this directive to remove it (or we should at least warn the user). Idealy, it would be great to simply remove repeated message for rudder messages, but I'm not sure it is feasable
- Target version changed from 2.10.12 to 2.10.13
- Target version changed from 2.10.13 to 2.10.14
- Target version changed from 2.10.14 to 2.10.15
- Target version changed from 2.10.15 to 2.10.16
- Related to Bug #6382: Random sprurious "Unknown" reports in the Web Interface added
- Related to Bug #4281: Rsyslog filters reports when too many reports arrive simultaneously added
For clarification, this should be on the client side, not server side (it is already server side)
- Target version changed from 2.10.16 to 2.10.17
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 277
- Target version changed from 277 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Translation missing: en.field_tag_list set to Quick and important, Sponsored, Next minor release
- Related to Bug #8264: Disable Repeated message reduction or reports may be lost on the relay added
Rsyslog keeps the last read value, and files in rsyslog.d are parsed after the RepeatedMsgReduction (at least on SuSE), so we only need to add it to the Rudder config file.
We also have to keep in mind that it is a global configuration that will be applied on all the logs from the machine.
- Assignee set to Alexis Mousset
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/937
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Related to Bug #8451: On Centos6.6, rsyslog is always restarted added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
Also available in: Atom
PDF