Project

General

Profile

Actions
Copy link

Bug #7389

closed

Syslog fails to restart due bad line in syslog-ng.conf

Bug #7389: Syslog fails to restart due bad line in syslog-ng.conf

Added by Janos Mattyasovszky over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
System techniques
Target version:
2.10.20
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

During an OS-Update an agent was not disabled, and it somehow wrote a bad line into the config file:

server:~ # grep syslog_ng /etc/syslog-ng/syslog-ng.conf.2015_10_25_141708
${syslog_ng_conf}
server:~ #

This is very similar to Bug #3107, however, the parenthesis is different, in that Bug a fix was introduced to remove "\$\(syslog_ng_conf\)" via "bundle edit_line edit_syslog_conf_file".

We have had "${syslog_ng_conf}" in our config.

Investigations are still ongoing, how this could happen.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #3107: On Rudder 2.4.0, the reports on the nodes with syslog-ng aren't send to the server since syslog-ng can't be startedReleasedActions

Updated by Jonathan CLARKE over 10 years ago Actions
Copy link
 #1

That is rather odd, indeed. I can't see why this would happen from reading the code.

A couple of questions to help us understand:

  • Do you by any chance also have /etc/rsyslog.conf or /etc/syslog.conf files on that machine?
  • Could you find the logs the rudder-agent sent from that around that time that contain "@Log system for reports@"?

Updated by Jonathan CLARKE over 10 years ago Actions
Copy link
 #2

  • Related to Bug #3107: On Rudder 2.4.0, the reports on the nodes with syslog-ng aren't send to the server since syslog-ng can't be started added

Updated by Jonathan CLARKE over 10 years ago Actions
Copy link
 #3

  • Target version set to 2.10.20

I really don't see how this happened, but we can at least add a similar workaround to #3107 and delete that line if it appears too. This way, the problem will be temporary and automatically get fixed rather than hang around...

If you do figure any more out about how this happened, please let us know.

Updated by Jonathan CLARKE over 10 years ago Actions
Copy link
 #4

  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE

Updated by Jonathan CLARKE over 10 years ago Actions
Copy link
 #5

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/790

Updated by Jonathan CLARKE over 10 years ago Actions
Copy link
 #6

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

Updated by Vincent MEMBRÉ over 10 years ago Actions
Copy link
 #8

  • Category changed from Techniques to System techniques

Updated by Vincent MEMBRÉ over 10 years ago Actions
Copy link
 #9

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.20, 2.11.17, 3.0.12 and 3.1.5 which were released today.

Actions
Copy link

Also available in: PDF Atom