Project

General

Profile

Actions

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 about 11 years ago.

Status:
Released
Priority:
1
Assignee:
-
Category:
System techniques
Target version:
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 open1 closed)

Related to Rudder - Bug #7389: Syslog fails to restart due bad line in syslog-ng.confReleasedBenoƮt PECCATTE2015-11-09Actions
Actions #1

Updated by Nicolas PERRON over 11 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 #2

Updated by Nicolas CHARLES over 11 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 #3

Updated by Nicolas CHARLES over 11 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
Actions #4

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from New to Pending technical review

The pull request for correcting the invalid value is here
https://github.com/Normation/rudder-techniques/pull/18/files

Actions #5

Updated by Nicolas CHARLES over 11 years ago

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

Applied in changeset commit:3e89bb55fc59b2a171e332b1842fb126f733cdfd.

Actions #6

Updated by Nicolas CHARLES over 11 years ago

Applied in changeset commit:070faecd694cc693d6451578b01fd67221b317fa.

Actions #7

Updated by Nicolas PERRON over 11 years ago

Applied in changeset commit:7fb1dc49889ef9a9d7ffb2bd982dbf6d4eed35b0.

Actions #8

Updated by Nicolas PERRON over 11 years ago

Applied in changeset commit:d217977284065f1c9595e918059dcd2def5120fc.

Actions #9

Updated by Nicolas PERRON about 11 years ago

  • Status changed from Pending release to Released
Actions #10

Updated by Jonathan CLARKE over 8 years ago

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

Also available in: Atom PDF