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 - Rudder - Issue Tracker

Actions

Copy link

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 almost 12 years ago. Updated almost 12 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Category:

System techniques

Target version:

2.4.1

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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); };

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas PERRON almost 12 years ago

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(\"";

Actions

Copy link

Updated by Nicolas CHARLES almost 12 years ago

I've submited a correction for the configuration; however it does not remove invalid entries from the syslog-ng that might have been configured

Actions

Copy link

Updated by Nicolas CHARLES almost 12 years ago

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