Bugzilla – Bug 6331
Build 106a Live CD sometimes boots only to console login
Last modified: 2009-02-12 10:16:51 UTC
You need to log in before you can comment on or make changes to this bug.
The build 106a live CD images booted and installed correctly under Virtual Box, but when booting on the metal of my Tecra M5, the boot only reaches the console login prompt and stops. Logging in as jack, we observe that nwam is in maintenance, with the following in the log: [ start + 1.15s Enabled. ] [ start + 2.37s Executing start method ("/lib/svc/method/net-nwam start"). ] svcprop: Couldn't find property group `system' for instance `svc:/system/svc/restarter:default'. [ start + 2.41s Method "start" exited with status 0. ] [ start + 3.65s Stopping because all processes in service exited. ] [ start + 3.66s Executing stop method ("/lib/svc/method/net-nwam stop"). ] /lib/svc/method/net-nwam[73]: /usr/bin/pkill: not found [No such file or directory] [ start + 3.68s Method "stop" exited with status 0. ] This repeats until startd decides it's restarting too rapidly and places it in maintenance, which blocks multi-user from coming online, hence no desktop. Once logged in to the console, issuing "svcadm clear nwam" allows NWAM to come online and the desktop to be started.
*** Bug 6404 has been marked as a duplicate of this bug. ***
I also have this problem, except on a system upgraded from b105 to b106. My experience matches the reporter's where clearing the nwam error will allow all the other services to start successfully. I have also found that if I boot in reconfigure mode, nwam doesn't throw any errors in the first place.
*** Bug 6430 has been marked as a duplicate of this bug. ***
same observed with b106 live CD on a toshiba Tecra M9
I also see this on a Sony Vaio. I've recently upgraded from build 99 to 106.
Some basic investigation and discussion indicates that the svcprop error message shown in the log occurs on every non-reconfiguration boot, so it's a red herring. The problem here appears to be nwamd exiting for no apparent reason. Reassigning to networking, marking as release blocker.
Now being tracked in bugster via CR 6804774.
*** Bug 6459 has been marked as a duplicate of this bug. ***
*** Bug 6782 has been marked as a duplicate of this bug. ***