Bug ID 1200682
Summary rsyslog hangs during shutdown
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Tumbleweed
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee screening-team-bugs@suse.de
Reporter oliver@schwabedissen.name
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Since one of the last snapshots my system takes very log to shutdown. I found
that there is a 90 second timeout when trying to stop system logging services.

The message I see is

"A stop job is running for system logging service (1 min 30 sec)"

After 90 seconds rsyslog is killed and shutdown continues.

I also see this when trying to stop rsyslog on a running system (systemctl stop
rsyslog.service):

Jun 19 09:03:14 frodo systemd[1]: Stopping System Logging Service...
Jun 19 09:04:44 frodo systemd[1]: rsyslog.service: State 'stop-sigterm' timed
out. Killing.
Jun 19 09:04:44 frodo systemd[1]: rsyslog.service: Killing process 1783
(rsyslogd) with signal SIGKILL.
Jun 19 09:04:44 frodo systemd[1]: rsyslog.service: Killing process 1787
(in:imklog) with signal SIGKILL.
Jun 19 09:04:44 frodo systemd[1]: rsyslog.service: Killing process 1788
(rs:main Q:Reg) with signal SIGKILL.
Jun 19 09:04:44 frodo systemd[1]: rsyslog.service: Main process exited,
code=killed, status=9/KILL
Jun 19 09:04:44 frodo systemd[1]: rsyslog.service: Failed with result
'timeout'.
Jun 19 09:04:44 frodo systemd[1]: Stopped System Logging Service.

I found a thread about this in the openSUSE forums:
https://forums.opensuse.org/showthread.php/571409-Ninety-second-shutdown-delay-quot-A-stop-job-is-running-for-system-logging-service-quot?p=3135179

Some tried to replace rsyslog with syslog-ng which solved the problem. But this
is a workaround and I think a fix should be found.


You are receiving this mail because: