Project

General

Profile

Actions

Bug #7635

closed

syslog-ng's loghost regex does not match with set line

Added by Janos Mattyasovszky over 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
1
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Hi,

Please check this:

https://github.com/Normation/rudder-techniques/commit/24ee9cd0dc7e80022d8f6d3f6ebfbe3d45c6c5b1
https://github.com/Normation/rudder-techniques/commit/39ca4bd861bbd4f8b2a11563de4e76191c87981b

The first commit changed the name of the loghost to rudder_loghost, but then the second fix reverts the regex-matching var to use a hard-coded version instead of the perviously changed variable...

-      "syslog_ng_conf_regex"  string => concat(escape("${syslog_ng_conf_prefix}"), "[^\"]+", escape("${syslog_ng_conf_suffix}"), ".*");
+      "syslog_ng_conf_regex"  string => concat("filter\ f\_local\_rudder\{facility\(local6\)\ and\ program\(\"rudder\.\*\"\)\;\}\;destination\ loghost\ \{(tcp|udp)\(\"", "[^\"]+", escape("${syslog_ng_conf_suffix}"), ".*");

The implemented Fix should please also fix the misconfigured logfiles :-)


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #5773: Syslog configuration on agent can conflict with loghostsReleasedJonathan CLARKE2014-11-13Actions
Related to Rudder - Bug #5799: system technique can only setup log settings *once* on syslog-ngReleasedJonathan CLARKE2014-11-20Actions
Actions

Also available in: Atom PDF