Weblog entry #19 for lykwydchykyn
For some reason, every time I do a remote upgrade, the system fails to come back up after reboot. Every time. I have to go out or send someone out to power off the server and cold boot it. After that it works fine.
I can't seem to reproduce the problem back at the office, and I'm getting nervous because the two I have left to upgrade do DHCP and DNS for some fairly large (and distant) facilities.
Can anyone hazard a guess as to why this is happening (apart from murphy's law)?
Comments on this Entry
[ Send Message | View Steve's Scratchpad | View Weblogs ]
If the machines haven't been restarted "recently" they might be coming back - but very very slowly as they run an fsck on boot?
Using a serial console will be the way to see what is happening; you might consider trying the network-console thing the kernel has to see remote messages via udp?
[ Parent | Reply to this comment ]
I'm intrigued about the serial console/UDP -- never heard of it. Do you have a link?
[ Parent | Reply to this comment ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
You'd be looking something like this.
Though in your case I guess you'll be needing to add the module directly to the kernel command line, via grub/lilo, to make sure it loads immediately. So this guide might be more appropriate to you.
[ Parent | Reply to this comment ]
I had servers not unmounting nicely at end of upgrade, I assume the change to the boot procedure or some such leaving stuff running that wouldn't normally. In my case most are either local or virtual, so I have a remote console.
[ Parent | Reply to this comment ]