Project

General

Profile

Bug #6421

Messages can be dropped on the node, resulting in Unknown reports on the Web Interface

Added by Nicolas CHARLES about 5 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
2
Category:
System integration
Target version:
Severity:
User visibility:
Effort required:
Priority:

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


Related issues

Related to Rudder - Bug #6382: Random sprurious "Unknown" reports in the Web InterfaceRejected2015-03-10Nicolas CHARLESActions
Related to Rudder - Bug #4281: Rsyslog filters reports when too many reports arrive simultaneouslyReleased2013-12-19Jonathan CLARKEActions
Related to Rudder - Bug #8264: Disable Repeated message reduction or reports may be lost on the relayReleased2016-05-10Jonathan CLARKEActions
Related to Rudder - Bug #8451: On Centos6.6, rsyslog is always restartedReleased2016-06-03Nicolas CHARLESActions
#1

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.12 to 2.10.13
#2

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.13 to 2.10.14
#3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.14 to 2.10.15
#4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.15 to 2.10.16
#5

Updated by Nicolas CHARLES almost 5 years ago

  • Related to Bug #6382: Random sprurious "Unknown" reports in the Web Interface added
#6

Updated by Nicolas CHARLES almost 5 years ago

  • Related to Bug #4281: Rsyslog filters reports when too many reports arrive simultaneously added
#7

Updated by Nicolas CHARLES almost 5 years ago

For clarification, this should be on the client side, not server side (it is already server side)

#8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.16 to 2.10.17
#9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.17 to 2.10.18
#10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.18 to 2.10.19
#11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.19 to 2.10.20
#12

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.20 to 277
#13

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 277 to 2.11.18
#14

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.18 to 2.11.19
#15

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.19 to 2.11.20
#16

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.11.20 to 2.11.21
#17

Updated by Jonathan CLARKE about 4 years ago

  • Tags set to Quick and important, Sponsored, Next minor release
#18

Updated by Alexis MOUSSET about 4 years ago

  • Related to Bug #8264: Disable Repeated message reduction or reports may be lost on the relay added
#19

Updated by Alexis MOUSSET about 4 years ago

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.

#20

Updated by Jonathan CLARKE about 4 years ago

  • Assignee set to Alexis MOUSSET
#21

Updated by Alexis MOUSSET about 4 years ago

  • Status changed from New to In progress
#22

Updated by Alexis MOUSSET about 4 years ago

  • 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
#23

Updated by Alexis MOUSSET about 4 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#24

Updated by Nicolas CHARLES about 4 years ago

  • Related to Bug #8451: On Centos6.6, rsyslog is always restarted added
#25

Updated by Vincent MEMBRÉ almost 4 years ago

  • 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