Actions
tickets #168493
openmonitor.i.o.o rsyslogd dies randomly
Status:
New
Priority:
Normal
Assignee:
-
Category:
Core services and virtual infrastructure
Target version:
-
Start date:
2024-10-19
Due date:
% Done:
0%
Estimated time:
Description
Every few days I find this:
monitor (heroes-bot, monitor.o.o, syslog.i.o.o):~ # rcrsyslog status
× rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/rsyslog.service.d
└─override.conf
Active: failed (Result: exit-code) since Thu 2024-10-17 00:23:20 UTC; 2 days ago
TriggeredBy: × syslog.socket
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 1576 (code=exited, status=1/FAILURE)
CPU: 11ms
Oct 17 00:23:20 monitor systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 5.
Oct 17 00:23:20 monitor systemd[1]: rsyslog.service: Start request repeated too quickly.
Oct 17 00:23:20 monitor systemd[1]: rsyslog.service: Failed with result 'exit-code'.
Oct 17 00:23:20 monitor systemd[1]: Failed to start System Logging Service.
Starting it again brings it up as if nothing ever happened.
I can't find any relevant log messages leading up to the crash.
I tried enabling debug logging to a file, but it generates gigabytes of data within just a few seconds, making it impossible to keep on until the crash happens again...
Updated by crameleon 4 months ago
In case we cannot figure it out, https://progress.opensuse.org/issues/166475#note-5 would implicitly solve it too. But will take some time.
The rsyslog.service unit already has Restart=on-abort. It seems it dies with a non-abort exit code. We could change it to Restart=always as a workaround (though I deem it not such good practice, as it would also restart on configuration errors or similar).
Actions