[Bug 1012883] New: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30)
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883 Bug ID: 1012883 Summary: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: jeckferson@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- It's an upstream systemd bug as described in: https://github.com/systemd/systemd/issues/1615 It also manifested in 42.2. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c1
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c2
--- Comment #2 from Kyaw Thu Soe
From reading the journalctl logs, it had something to do with coredump. I found klauncher started coredumping just before the 90s time lapse. I will report the log when it happen again. Also I updated the bios yesterday. Apparently, not all machine live through this problem hence it might be hardware-related.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c3
--- Comment #3 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c4
--- Comment #4 from Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c5
--- Comment #5 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c6
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c7
--- Comment #7 from Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c8
--- Comment #8 from Franck Bui
I will permanently set log level to debug from now on.
Unfortunately, that won't really help as systemd doesnt show the hanging processes that prevents the user session to be closed hence to shutdown the system even in debug mode. However I built a test package that includes such traces which will help us to identify the culprit (hopefully). Could you install the following repo on your affected system and try to reproduce ? In order to do that, please do: zypper ar http://download.opensuse.org/repositories/home:/fbui:/branches:/openSUSE:/Fa... systemd-with-debug-trace zypper dup --repo systemd-with-debug-trace Also make sure to have the journal in persistent mode: mkdir -p /var/log/journal and then reboot until you can reproduce the issue. Once done please show the content of the journal of the previous boot (journalctl -b -1 and search for the "FOO" string). Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c9
--- Comment #9 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c10
--- Comment #10 from Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c11
--- Comment #11 from Franck Bui
Created attachment 705719 [details] multiple
and what about trying the testing package in comment #9 ? and please do not send all journals from your system... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c12
--- Comment #12 from Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c13
--- Comment #13 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c14
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c15
--- Comment #15 from Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c16
--- Comment #16 from Franck Bui
One can find more of this occurrence in the previous attachment named "multiple" by searching the word "timed out". To my relief, systemd 232v is in Factory staging and possibly will come out any minute now. It will perhaps bring an end to the problems of coredump or timesyncd, which I think are the root causes.
Currently I don't think coredump nor timesyncd is your problem. And you can easily check that by disabling both of them and see if the problem goes away. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c17
--- Comment #17 from Kyaw Thu Soe
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
Tomáš Chvátal
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c18
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c19
Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c20
--- Comment #20 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
Manfred Hollstein
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c21
--- Comment #21 from Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c22
Felix Miata
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c24
Axel Braun
Stopped User Login Management Started Show Plymouth Power Off Screen Tell Plymouth To Jump To initramfs was skipped because of a failed condition check (ConditionPathExists=/run/initramfs/bin/sh)
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c25
Jazz
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883
http://bugzilla.opensuse.org/show_bug.cgi?id=1012883#c26
--- Comment #26 from Jazz
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com