Project

General

Profile

Actions
Copy link

Bug #3569

closed

If rsyslog is installed after another syslog, rsyslog is never used on SLES and reports will never be caught by Rudder server

Bug #3569: If rsyslog is installed after another syslog, rsyslog is never used on SLES and reports will never be caught by Rudder server

Added by Nicolas PERRON almost 13 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
2
Assignee:
-
Category:
Techniques
Target version:
2.3.13
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On SLES 11, the file /etc/sysconfig/syslog contains the variable SYSLOG_DAEMON which could be set to syslog-ng if it is installed before any other syslog. Then, the init daemon syslog will use this variable to know which syslog to start.

We should ensure that this variable is rsyslogd or empty to have a fully fonctionnal reporting on Rudder.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #7098: When syslog-ng is replaced by rsyslogd on SuSE, service is not restartedReleasedMatthieu CERDAActions
Actions
Copy link

Also available in: PDF Atom