Bug 693913

Summary:	System with systemd installed does not boot without it(normal init)
Product:	[openSUSE] openSUSE 12.1	Reporter:	Christoph Obexer <cobexer>
Component:	Basesystem	Assignee:	Frederic Crozat <fcrozat>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	kay.sievers
Version:	Factory
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Christoph Obexer 2011-05-15 21:34:30 UTC

User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

Booting current factory fails for me on two different systems.
a) when booting with normal init and systemd is installed (did not try without since i do not know if it will boot at all without systemd) basically nothing is able to start because some connect on a socket with systemd in its name is not possible. the boot process halts in runlevel 1? and asks for the root password, entering "reboot" there does not even succeed then...

b) booting with systemd (adding init=/bin/systemd in grub interactive) allows me to boot both systems, however both still do not boot correctly.
one system does not start at least dbus. login -> rcdbus start starts dbus correctly(rcdbus restart does NOT!) that system seems to work properly otherwise. (the system starts in about 12 seconds which is ok and with the exception of dbus i do not seem to miss anything!)
the other however has a more complicated setup: encrypted /home. systemd asks for the password and successfully unlocks the encrypted volume. however it does not mount /home after that. extremely bad about it is that not a single vt starts a login terminal... so on that machine i have to wait for the auto login to fail, fallback to using / as home? (WTF), wait for the second fail, login as root, enter mount /home in a terminal, logout, and login as the correct user... very annoying.

Reproducible: Always

Steps to Reproduce:
1. current factory
2. instyll systemd, use normal init as default
3. reboot -> complete failure of all? services
4. reboot with init=/bin/systemd, some failed services but at least boots

package versions before the gcc switch, some packages were newer already, but not systemd and the kernel or init

Comment 1 Christoph Obexer 2011-05-16 05:40:57 UTC

I just found out what the problem is: something mounted /sys/fs/cgroup/systemd and thus /etc/rc.status tried to use systemd. unmounting it made it possible t

Comment 2 Christoph Obexer 2011-05-16 05:43:42 UTC

... sorry... to continue to boot with doing init 5, besides that the hostname was not set and after it was set new programs could not connect to the display.

Comment 3 Frederic Crozat 2011-06-17 08:22:13 UTC

how did you install systemd ? you installed factory M1 and after, used "zypper in systemd" ?

Comment 4 Christoph Obexer 2011-06-20 18:40:43 UTC

The system originated on 11.3 something and went straight to factory, from there was continually updated on factory (probably once a week or more often).

most of the time i install using zypper yes

zypper in systemd systemd-gtk

most likely.

ps.: since it was impossible to cleanly boot that machine i had uninstalled systemd again. i will try to reinstall systemd and see if i can find out more about the problem.

Comment 5 Kay Sievers 2011-06-26 15:02:12 UTC

Looks like aaa_base mounted the 'systemd' cgroup, which it shouldn't.
The aaa_base changelog contains:

  Tue May 17 12:16:26 UTC 2011 - lnussel@suse.de
  - don't mount /sys/fs/cgroup/systemd as it makes programs think
    systemd is in use

Comment 6 Christoph Obexer 2011-06-26 18:14:35 UTC

that should be it, I tried to reproduce it on both systems that showed that behavior but could not. also the boot with systemd is much better now!

so I'd say this can be closed as fixed =D

Comment 7 Frederic Crozat 2011-06-27 08:05:47 UTC

closing as FIXEd, reopen if needed