Project

General

Profile

Actions
Copy link

Bug #7389

closed

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

Added by Janos Mattyasovszky about 9 years ago. Updated almost 9 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 startedReleased2012-12-26Actions
Actions
Copy link

Also available in: Atom PDF