Project

General

Profile

Bug #10949

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 6 months ago. Updated 6 months ago.

Status:
Released
Priority:
N/A
Category:
Initial promises & sys tech
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
35

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

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

Associated revisions

Revision 45019897
Added by Alexis MOUSSET 6 months ago

Fixes #10949: Agent output contains error because of new syslog service checks

History

#1 Updated by Alexis MOUSSET 6 months ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#2 Updated by Benoît PECCATTE 6 months 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

#3 Updated by Alexis MOUSSET 6 months 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

#4 Updated by Alexis MOUSSET 6 months ago

  • Status changed from Pending technical review to Pending release

#5 Updated by Alexis MOUSSET 6 months ago

  • Parent task set to #8168

#6 Updated by Alexis MOUSSET 6 months 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.

Also available in: Atom PDF