On Thu, 29.09.11 00:16, Nick Urbanik (ni...@nicku.org) wrote: > Dear Folks, > > I am running Fedora 15 on a 4-core x86_64 machine which received a > power surge recently, and spontaneously rebooted. Strange behaviour > followed, so I touched /forcefsck and /.autorelabel on separate > occasions, rebooting each time. I observe the following behaviour > regardless of whether I run setenforce 0 or setenforce 1. > > 1. Graphical boot does not complete; the Nagios server starts, but > systemd announced that cups had failed, and gdm did not start up. > 2. I cannot log in on the text consoles; I can type in the username, > but no prompt appears for the password. > 3. I can log in via ssh as either myself or as root. > 4. Attempts to use su fail, but can be interrupted. > 5. Attempts to use sudo hang, and require that I kill the process > 6. Many attempts to use systemctl (for example, by itself to list the > state of all the state of all services) result in a message after a > time out, complaining about dbus timing out. > 7. A cupsd and a dbus process are both present, but apparently not > responding. > > # systemctl kill cups.service > Failed to get D-Bus connection: Failed to authenticate in time. > # systemctl > Failed to get D-Bus connection: Failed to authenticate in time.
This looks as if D-Bus is borked for some reason. Is there anything interesting in dmesg or syslog? Do you get a shell if you specify "1" and "emergency" on the kernel cmdline? Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
