Project

General

Profile

Actions

Bug #7098

closed

When syslog-ng is replaced by rsyslogd on SuSE, service is not restarted

Added by Alexis Mousset over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Matthieu CERDA
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

After installing rudder-server-root or rudder-server-relay, the service name is changed in /etc/sysconfig/syslog, but the syslog service is not restarted and syslog-ng keeps running.



Related issues 2 (0 open2 closed)

Related to Rudder - Bug #3569: If rsyslog is installed after another syslog, rsyslog is never used on SLES and reports will never be caught by Rudder serverReleased2013-05-02Actions
Related to Rudder - Bug #5991: On a freshly installed node, rsyslog is dropping messagesReleasedBenoƮt PECCATTE2014-12-12Actions
Actions

Also available in: Atom PDF