View previous topic :: View next topic |
Author |
Message |
jsnorman Tux's lil' helper
Joined: 24 Feb 2005 Posts: 131
|
Posted: Thu Jul 06, 2006 2:52 am Post subject: Boot process hanging after local [cupsd problem?] |
|
|
EDIT - I have found the culprit, and a temporary workaround, to the problem below. Basically:
1) When I boot cupsd hangs on exec from the rc script sequence (/etc/init.d/cupsd)
2) The boot process hangs waiting for cupsd to return (I guess - there is no error message and strangely no timeout, ever)
3) xdm will load okay thankfully, and I can open a root terminal and explicitly kill the /etc/init.d/cupsd process, and followed by /etc/init.d.cupsd restart - and again strangely, it works fine
4) After killing and restarting cups, boot process finishes and my login prompts finally appear in vt0 - vt6
WHY????
ORIGINAL POST:
I have had my gentoo system (~amd64) up and running with minimal downtime for almost a year. I regularly emerge updates, sometimes with disastrous effects, but always have been able to fix the problem .. this one has me stumped.
When I boot, I can see all processes starting ok, all the way through stage 3. There are no unusual messages or errors that I can see. I have inspected the system logs to the best of my knowledge they all appear fine, nothing crashing, no errors, nothing in faillog, dmesg, or kernel logs that would be unusual.
However, on vt0 through vt6, after local is started, my login prompt never appears and it seems like everything is just hanging.
If I have xdm loading, it will load so at least I can use the computer through X, but my vt's appear to be hosed. Without X starting in the boot sequence, the system is unusable because there is not login prompt, no error, and no way to get to a shell.
Here is the really strange part - if I choose "Interactive" and just manually start EVERY process, my login prompt appears and everything is groovy.
I am also not sure WHEN this started happening. I rarely reboot, so I have done dozens of updates over 3 months or so without rebooting (I just restart the needed services instead). I only reboot this time to upgrade to the new kernel release; but using the old kernel image I now have the same issue.
Without errors, I just do not know where to look. Anyone seen anything like this before?
Jeff
EDIT - Here are the services I have running in the init scripts:
Code: | alsasound | boot
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
coldplug | boot
consolefont | boot
cupsd | default
ddclient | default
dnsmasq | default
hostname | boot default
hotplug | boot
iptables | default
keymaps | boot
lm_sensors | default
local | default nonetwork
localmount | boot
mdadm | boot
metalog | default
modules | boot
net.eth0 | default
net.lo | boot
netmount | default
portmap | default
rmnologin | boot
samba | default
serial | boot
snort | default
ulogd | default
urandom | boot
vixie-cron | default
vmware | default
xdm | default
|
Last edited by jsnorman on Mon Jul 10, 2006 4:10 am; edited 2 times in total |
|
Back to top |
|
|
Keruskerfuerst Advocate
Joined: 01 Feb 2006 Posts: 2289 Location: near Augsburg, Germany
|
Posted: Thu Jul 06, 2006 9:54 am Post subject: |
|
|
Maybe you should try to use AMD64 instead of ~AMD64.
I have a computer running a stable Gentoo 2006.0 with AMD64. |
|
Back to top |
|
|
jsnorman Tux's lil' helper
Joined: 24 Feb 2005 Posts: 131
|
Posted: Thu Jul 06, 2006 12:44 pm Post subject: |
|
|
Alas, when I started with gentoo, the stable branch was completely unusable for amd64. It only recently (this year) became good enough to use, but all my systems are ~amd64 and I do not have the time to rebuild the os and world with stable (and believe me, you cannot simply modify ~amd64 -> amd64 followed by emerge -e system; that way lies disaster). |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|