Page 1 of 1
The Horror!
Posted: Fri Aug 04, 2006 7:48 am
by thiscatis
Hi,
We have rebooted this server however when we attached a monitor the server had a kernel panic, which is an operating system error.
If you can let me know how you would like us to proceed that would be great, however there are generally remote hands charges for any further work.
Matthew
Anyone?
Posted: Fri Aug 04, 2006 7:50 am
by feyd
huh?
Posted: Fri Aug 04, 2006 8:04 am
by thiscatis
Well, a friend of mine has a dedicated server but he left for holiday this week.
He told me to run his community, last night the server crashed and I asked for a reboot.
this is wat they sent me then..
Posted: Fri Aug 04, 2006 1:34 pm
by Benjamin
Sounds like they broke it, now they want to charge you to fix it?
Posted: Fri Aug 04, 2006 1:35 pm
by RobertGonzalez
Sounds like astions hit that one on the head. Their server had a problem with their installed linux distro, and they are asking for payment to resolve this for you? Slipshod wastes of tech support. That doesn't sound quite right.
Posted: Fri Aug 04, 2006 1:51 pm
by Chris Corbyn
Hmm... just a thought but if it's a server screw the monitor and use SSH to remote logon to it. Or use a serial connection. Easy enough. Heh.... gimme an IP and some credentials and I'll have a look at it free if it's a quick job - maybe chargeable if it's a long job

Posted: Fri Aug 04, 2006 3:50 pm
by tarnus
With a kernel panic your not going to SSH into that box. If all the hoster did was reboot it, sounds like its hosed. Your gonna either have to go look at it yourself or pay the host to look into it. There could be any number of issues at this point... what was the initial reason for the reboot?
Posted: Fri Aug 04, 2006 5:09 pm
by Chris Corbyn
tarnus wrote:With a kernel panic your not going to SSH into that box. If all the hoster did was reboot it, sounds like its hosed. Your gonna either have to go look at it yourself or pay the host to look into it. There could be any number of issues at this point... what was the initial reason for the reboot?
Kernel panic is down to the monitor being connected according to the OP. Disconnect the monitor, start the server and log in over ssh. If ssh isn't already running they'll have to connect a keyboard and do it blindly or try using a serial connection if available. Heh... I've got a few servers going purely by memory before now with no monitor and nothing to see while I type. It can be done

Posted: Fri Aug 04, 2006 5:12 pm
by Chris Corbyn
OK ignore me.... I misunderstood the reason for the panic. I thought the host were saying that the monitor had caused the panic.
Hmm... at what point does it panic? You can try fixing it by chrooting into the system from a live CD then rebuild your kernel from there. You may also get it started in single user mode to have a poke around too.
Posted: Fri Aug 04, 2006 5:38 pm
by Benjamin
Prolly a hard reboot corrupted some system files because it was running ext2 file system. Just restore from backup. You do have a backup right

Re: The Horror!
Posted: Fri Aug 04, 2006 5:58 pm
by Christopher
thiscatis wrote:Anyone?
Don't do anything! It's not your sever or your fault (we hope). The owner needs to proceed cautiously. The worst thing to do when a server crashes it to do something rash.
If it will not boot then the best thing to do is have them NOT TOUCH the current drive and install a new boot drive and then mount the old drive so you can take a look at it.
Posted: Sat Aug 05, 2006 6:29 am
by thiscatis
Ok, i'll wait till my friend comes back from a holiday, don't want to mess something up
