Project

General

Profile

Actions
Copy link

Bug #7098

closed

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

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

Status:
Released
Priority:
N/A
Assignee:
Matthieu CERDA
Category:
System integration
Target version:
3.0.9
Pull Request:
https://github.com/Normation/rudder-t...
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 open — 2 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
Copy link
 #1

Updated by Alexis Mousset almost 10 years ago

  • Related to 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
Actions
Copy link
 #2

Updated by Alexis Mousset almost 10 years ago

  • Category set to System integration
  • Target version set to 3.0.9
Actions
Copy link
 #3

Updated by Alexis Mousset almost 10 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions
Copy link
 #4

Updated by Alexis Mousset almost 10 years ago

  • Status changed from In progress to New
  • Assignee deleted (Alexis Mousset)
  • Target version changed from 3.0.9 to 2.10.17
Actions
Copy link
 #5

Updated by Alexis Mousset almost 10 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions
Copy link
 #6

Updated by Alexis Mousset almost 10 years ago

The problem is that the postinstall makes the substitution, and does not restart the service.

Actions
Copy link
 #7

Updated by Alexis Mousset over 9 years ago

  • Target version changed from 2.10.17 to 3.0.9
Actions
Copy link
 #8

Updated by Alexis Mousset over 9 years ago

  • Related to Bug #5991: On a freshly installed node, rsyslog is dropping messages added
Actions
Copy link
 #9

Updated by Alexis Mousset over 9 years ago

The problem was found in #5991, but in the other way: rsyslog was not restarted in rsyslogConf because check_log_system was evaluated before.

Actions
Copy link
 #10

Updated by Alexis Mousset over 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Matthieu CERDA
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/731
Actions
Copy link
 #11

Updated by Alexis Mousset over 9 years ago

  • Status changed from Pending technical review to In progress
Actions
Copy link
 #12

Updated by Matthieu CERDA over 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Nicolas CHARLES
  • % Done changed from 0 to 100
  • Pull Request changed from https://github.com/Normation/rudder-techniques/pull/731 to https://github.com/Normation/rudder-techniques/pull/732
Actions
Copy link
 #13

Updated by Alexis Mousset over 9 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #15

Updated by Matthieu CERDA over 9 years ago

  • Status changed from Pending release to Released
  • Assignee changed from Nicolas CHARLES to Matthieu CERDA
  • Target version changed from 3.0.8 to 3.0.9
  • % Done changed from 100 to 0
Actions
Copy link

Also available in: Atom PDF