Project

General

Profile

Actions

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

Added by Nicolas PERRON about 9 years ago. Updated over 7 years ago.

Status:
Released
Priority:
2
Assignee:
-
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:

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 open1 closed)

Related to Rudder - Bug #7098: When syslog-ng is replaced by rsyslogd on SuSE, service is not restartedReleasedMatthieu CERDA2015-08-12Actions
Actions #1

Updated by Nicolas PERRON about 9 years ago

  • Project changed from Rudder to 24
  • Priority changed from N/A to 2
  • Target version set to 2.3.12

I suppose it should be a CFEngine promise which sould ensure that

Actions #2

Updated by Matthieu CERDA about 9 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions #3

Updated by Nicolas PERRON about 9 years ago

  • Status changed from New to Pending technical review
  • % Done changed from 0 to 100
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/122

Pull Request URL added: https://github.com/Normation/rudder-techniques/pull/122

Jon, could you review it please ?

Actions #4

Updated by Nicolas PERRON about 9 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:9cd912052c534965b5c071c8c70e1dc90e48c1cb.

Actions #5

Updated by Jonathan CLARKE about 9 years ago

Applied in changeset commit:8168b1060eef66944f6d9f77abb7e30dfe1eb8e9.

Actions #6

Updated by Nicolas PERRON about 9 years ago

  • Subject changed from On SLES 11, if syslog-ng is installed before rsyslog, the init deamon syslog will not start rsyslog which will leads Rudder to not received any reports to If rsyslog is installed after another syslog, rsyslog is never used on SLES and reports will never be caught by Rudder server
Actions #7

Updated by Nicolas PERRON about 9 years ago

  • Status changed from Pending release to Released
Actions #8

Updated by Benoît PECCATTE over 7 years ago

  • Project changed from 24 to Rudder
  • Category set to Techniques
Actions #9

Updated by Alexis Mousset almost 7 years ago

  • Related to Bug #7098: When syslog-ng is replaced by rsyslogd on SuSE, service is not restarted added
Actions

Also available in: Atom PDF