[Bug 749035] New: System hangs after entering Runlevel 0 on a sysvinit Shutdown (cause known)
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c0 Summary: System hangs after entering Runlevel 0 on a sysvinit Shutdown (cause known) Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andrew.williams@gmx.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120215 Firefox/10.0.2 SeaMonkey/2.7.2 Messages just before the hang include error while loading shared libraries libsystemd-daemon.so.0 INIT: no more processes left in this runlevel (the first of those lines may look slightly different) The system then hangs. I have normally done an ESC by then so I get to see the messages but they are not logged. Whatever - I know the cause and have a workaround. - My system has /usr (and /var, so this does not get logged) as separate partitions. - Package systemd places libsystemd-daemon.so.0 in /usr/lib64 - /usr has been unmounted by the time I get to this point. Obviously the workaround is to copy libsystemd-daemon.so.0 from /usr/lib64 to /lib64, I assume a final fix would be to put there in the first place. Reproducible: Always Steps to Reproduce: 1. Have /usr as a seperate partition 2. add init=/sbin/sysvinit to /boot/grub/menu.1st 3. shutdown, directly from a command-line or indirectly via kde4 Actual Results: The system hangs after entering runlevel 0. shutdown -r does not reboot, shutdown -h does not power off. I have no problems with loss of data, everything had already been cleanly unmounted. Expected Results: reboot or system halt with power off -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c kk zhang <kkzhang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@novell.com AssignedTo|bnc-team-screening@forge.pr |nld10-bugs-qa@forge.provo.n |ovo.novell.com |ovell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c1 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lmuelle@suse.com AssignedTo|nld10-bugs-qa@forge.provo.n |fcrozat@suse.com |ovell.com | --- Comment #1 from Lars Müller <lmuelle@suse.com> 2012-03-30 22:17:34 CEST --- The analysis sounds correct. And the missing reassignment to Frederic is one more reason to automate the process based on the data we already maintain in the Open Build Service. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c2 --- Comment #2 from Andrew Williams <andrew.williams@gmx.net> 2012-03-30 20:37:50 UTC --- The workaround is still effective one month later. I did have to copy the file from /usr/lib64 to /lib64 a couple of times after updates to the package but only because I wanted to keep things consistent. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c3 --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2012-04-02 08:33:03 UTC --- if you use sysvinit as a init system, you should install sysvinit-init: systemd tools to shutdown the system are working as "best effort" under non-systemd environment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c4 --- Comment #4 from Lars Müller <lmuelle@suse.com> 2012-04-02 10:46:51 CEST --- See also http://en.openSUSE.org/openSUSE:Most_annoying_bugs_12.1 in particular the section about: Bug #725917 Problem: System is switched from sysvinit to systemd during upgrade. Workaround: is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c5 --- Comment #5 from Andrew Williams <andrew.williams@gmx.net> 2012-04-02 14:49:22 UTC --- @Lars Müller, Comment No 4 Thank you, I can confirm that this works. I am not sure I agree with the "most annoying bug" classification, I originally followed a sysvinit tip from alt.linux.suse because systemd initialisation took 300 seconds and left me in a state where SuSEfirewall on the NIC addressing the internal network was blocking all traffic. I had to assume that SuSEfirewall was allowing everything on the external NIC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c6 Serg openSUSE-user <devel.openSUSE.org@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |devel.openSUSE.org@gmail.co | |m --- Comment #6 from Serg openSUSE-user <devel.openSUSE.org@gmail.com> 2012-08-15 04:30:26 EEST --- *** Bug 775025 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=775025 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=749035 https://bugzilla.novell.com/show_bug.cgi?id=749035#c7 systemd maintainers <systemd-maintainers@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #7 from systemd maintainers <systemd-maintainers@suse.de> 2014-01-15 11:33:35 UTC --- Hmm .. I'll close this bug as WONTFIX, as we do not switch back to SysVinit. For 12.1 it is possible to use SysVinit (I've done this by my self) and for and openSUSE afterwards the only supported init system is systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com