Project

General

Profile

Actions

Bug #10949

closed

Bug #8168: If syslog service is stopped, it is not restarted automatically by rudder-agent, so agent doesn't report anything

Agent output contains error because of new syslog service checks

Added by Alexis Mousset almost 7 years ago. Updated almost 7 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
35
Name check:
Fix check:
Regression:

Description

E| compliant     packageManagement         Package                   vim                Presence of package vim in any version was correct
E| n/a           packageManagement         Post-modification script  vim                No post-modification script was set to run
R: [INFO] Executing is-active on syslog using the systemctl method
R: [INFO] Executing is-active on syslog-ng using the systemctl method
R: [ERROR] Promise could not be repaired, error encountered: Check if the service syslog-ng is started
rudder     info: Executing 'no timeout' ... '/bin/systemctl --no-ask-password start syslog-ng.service'
   error: Finished command related to promiser '/bin/systemctl --no-ask-password start syslog-ng.service' -- an error occurred, returned 5
rudder     info: Completed execution of '/bin/systemctl --no-ask-password start syslog-ng.service'
R: [INFO] Executing start on syslog-ng using the systemctl method
   error: Method 'ncf_services' failed in some repairs
R: [ERROR] Promise could not be repaired, error encountered: Run action start on service syslog-ng
   error: Method 'service_action' failed in some repairs
R: [ERROR] Promise could not be repaired, error encountered: Start service syslog-ng
   error: Method 'service_start' failed in some repairs
R: [ERROR] Promise could not be repaired, error encountered: Ensure that service syslog-ng is running
   error: Method 'service_ensure_running' failed in some repairs
R: [INFO] Executing is-active on rsyslog using the service method
rudder     info: Deleted file '/var/rudder/cfengine-community/state/rudder_expected_reports.22483.csv.tmp'


Subtasks 1 (0 open1 closed)

Bug #10959: We should only use the "syslog" service on SLES11ReleasedBenoît PECCATTEActions
Actions #1

Updated by Alexis Mousset almost 7 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions #2

Updated by Benoît PECCATTE almost 7 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 35
Actions #3

Updated by Alexis Mousset almost 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1155
Actions #4

Updated by Alexis Mousset almost 7 years ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Alexis Mousset almost 7 years ago

  • Parent task set to #8168
Actions #6

Updated by Alexis Mousset almost 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.4 which was not released (see changelog for details), and is available in Rudder 4.1.5.

Actions

Also available in: Atom PDF