Actions
Bug #10987
closed
No logs when (r)?syslog(-ng)? is restarted in 4.1
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
On Rudder 4.1, if syslog service is stopped, it is automatically restarted by agent
However, we don't get any log about that, only output is
R: [INFO] Executing is-active on rsyslog using the service method R: [ERROR] Promise could not be repaired, error encountered: Check if the service rsyslog is started rudder info: Executing 'no timeout' ... '/usr/sbin/service rsyslog start' rudder info: Completed execution of '/usr/sbin/service rsyslog start' R: [INFO] Executing start on rsyslog using the service method R: [INFO] Promise repaired, made a change: Run action start on service rsyslog R: [INFO] Promise repaired, made a change: Start service rsyslog R: [INFO] Promise repaired, made a change: Ensure that service rsyslog is running
Updated by 
Updated by
Actions