-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/30/2011 09:26 AM, Kay Sievers wrote:
On Mon, 2011-05-30 at 11:17 +0200, Bruno Friedmann wrote:
My actual result ( tested 15 minutes ago ) are quite bad. with systemd system-sysinit and networkmanager activated I just get no network kde refuse to start due to dbus error and a lot of others services.
cat /var/log/messages | grep -i systemd May 30 10:38:11 c-3po kernel: [ 27.616858] systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse)
May 30 10:38:11 c-3po kernel: [ 28.462252] systemd[1]: Breaking ordering cycle by deleting job sysstat.service/start
Can you try to remove or disable sysstat from the bootup? It might have dependencies in its headers with can't be resolved by systemd.
May 30 10:38:11 c-3po kernel: [ 28.462295] systemd[1]: Breaking ordering cycle by deleting job cpufreq.service/start
Care to remove cpufreq. Nothing should fiddle around with CPU governors these days. The kernel's on-demand governor is the only sensible thing to do.
May 30 10:38:11 c-3po kernel: [ 32.223395] systemd-cryptsetup[855]: Encountered unknown /etc/crypttab option 'none', ignoring.
Care to check what 'none' means to express in that file, and if that can just be removed? Did you, or Yast added it?
May 30 10:38:11 c-3po kernel: [ 32.224951] systemd-cryptsetup[855]: Volume cr_sda2 already active. May 30 10:38:11 c-3po kernel: [ 32.281183] systemd-fsck[864]: boot : propre, 63/66264 fichiers, 104813/264192 blocs May 30 10:38:11 c-3po kernel: [ 38.410953] systemd[1]: network.service: control process exited, code=exited status=2 May 30 10:38:11 c-3po kernel: [ 38.411091] systemd[1]: Unit network.service entered failed state. May 30 10:38:12 c-3po kernel: [ 39.604429] systemd[1]: nscd.service: control process exited, code=exited status=7 May 30 10:38:12 c-3po kernel: [ 39.604438] systemd[1]: Unit nscd.service entered failed state. May 30 10:38:55 c-3po kernel: [ 83.208881] systemd[1]: network.service: control process exited, code=exited status=2 May 30 10:38:55 c-3po systemd[1]: Unit network.service entered failed state. May 30 10:39:15 c-3po kernel: [ 102.540229] systemd[1]: postgresql.service: control process exited, code=exited status=1 May 30 10:39:15 c-3po kernel: [ 102.548159] systemd[1]: Unit postgresql.service entered failed state. May 30 10:41:41 c-3po systemd[1]: Reloading. May 30 10:41:42 c-3po systemd[1]: [/etc/init.d/postfix:12] Failed to add LSB Provides name sendmail.service, ignoring: File exists May 30 10:43:33 c-3po systemd[1]: dbus.service: main process exited, code=exited, status=1 May 30 10:43:33 c-3po kernel: [ 360.961086] systemd[1]: Unit dbus.service entered failed state.
The unresolvable/cyclic dependencies cause unfortunately that D-Bus does not start properly, which will let NetworkManager and a lot of other stuff fail.
Unfortunately, they tend to fail mostly silently and don't allow the administrator to log in to fix it. I've been using systemd on several systems for a while now and this is consistently the biggest hurdle, in my mind, to making it the default. I shouldn't need to work up a special target to drop into a shell in order to debug an issue in some random dependency -- especially when, sometimes, it can just be a simple package installation that can cause a complete boot failure. Without an *easy* workaround mode, I'm afraid it won't get off the ground as the default in openSUSE. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3j/m4ACgkQLPWxlyuTD7IrUwCfafgWYiN2xfMSXvDkZyiJroCu H68AnjCSYamWCFH6e+/U/1894Wkz2U4S =xxFN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org