Bug #3107
closed
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 by Nicolas PERRON over 11 years ago.
Updated over 11 years ago.
Category:
System techniques
Description
On Rudder 2.4, the nodes using syslog-ng have a bad configuration file which prevent them to start syslog-ng.
This wrong configuration seems to be an unexpanded variable:
diff -Naurw /var/rudder/modified-files/_etc_syslog-ng.conf.cf-before-edit /etc/syslog-ng.conf
[...]
filter f_local_rudder{facility(local6) and program("rudder.*");};destination loghost[...]
+$(syslog_ng_conf)
log { source(src); filter(f_console); destination(console); };
It seems that a "any::" is missing on the Techniques (although this is not the case on the Policy Template [branch 2.3] ):
diff --git a/techniques/system/common/1.0/promises.st b/techniques/system/common/1.0/promises.st
index 7529295..4e6b132 100644
--- a/techniques/system/common/1.0/promises.st
+++ b/techniques/system/common/1.0/promises.st
@@ -320,6 +320,7 @@ bundle agent check_log_system {
"syslog_ng_source" string => "s_sys";
+ any::
"syslog_conf_comment" string => "# Autogenerated by rudder, do not edit${const.n}";
"syslog_ng_conf_prefix" string => "filter f_local_rudder{facility(local6) and program(\"rudder.*\");};destination loghost {tcp(\"";
I've submited a correction for the configuration; however it does not remove invalid entries from the syslog-ng that might have been configured
- Subject changed from On Rudder 2.4.1~rc1, the reports on the nodes with syslog-ng aren't send to the server since syslog-ng can't be started to 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
- Description updated (diff)
- Target version changed from 2.4.2 to 2.4.1
- Status changed from New to Pending technical review
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:3e89bb55fc59b2a171e332b1842fb126f733cdfd.
Applied in changeset commit:070faecd694cc693d6451578b01fd67221b317fa.
Applied in changeset commit:7fb1dc49889ef9a9d7ffb2bd982dbf6d4eed35b0.
Applied in changeset commit:d217977284065f1c9595e918059dcd2def5120fc.
- Status changed from Pending release to Released
- Related to Bug #7389: Syslog fails to restart due bad line in syslog-ng.conf added
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by