Reboots locally not remotely

dolem98 · 07-07-2004, 11:06 AM

I am having a really strange issue with a Slackware server that we have just set up.

It is being collocated and if they reboot it locally from the command prompt it reboots just fine. If I, however, log in from SSH and reboot it it, the reboot process starts normally but then just as the machine finally reboots, the screen goes blank.

Even stranger, I set up the machine for a while on my own network for troubleshooting, and I could reboot it through SSH on my own local network.

Any ideas?

keefaz · 07-07-2004, 11:14 AM

Quote:

then just as the machine finally reboots, the screen goes blank

Can you precise if reboot runs till the bios starts

HuMJohn · 07-07-2004, 11:34 AM

Quote:

Originally posted by dolem98
I am having a really strange issue with a Slackware server that we have just set up.

It is being collocated and if they reboot it locally from the command prompt it reboots just fine. If I, however, log in from SSH and reboot it it, the reboot process starts normally but then just as the machine finally reboots, the screen goes blank.

Even stranger, I set up the machine for a while on my own network for troubleshooting, and I could reboot it through SSH on my own local network.

Any ideas?

I can see what you are saying. When you reboot remotely (not on your own network) the screen goes blank....when it reboots, it shuts down its own network....and your ssh session will see that it is borked and blanks out.

When you set it on your own network and remotely reboot, you are probably watching the server monitor and not your own ssh session.........?

dolem98 · 07-07-2004, 11:36 AM

I don't think the BIOS loads up, it halts before that point.

HuMJohn, the SSH session of course closes on me, but the server doesn't reboot. We have had people at the collocation facility watch with a monitor hooked up, and the screen goes black. (They can however reboot it themselves from the command line)

Tuttle · 07-07-2004, 11:42 AM

this might sound silly but have you tried:

reboot &

or:

init 6 &

keefaz · 07-07-2004, 11:46 AM

or just by :
ssh "reboot"

dolem98 · 07-07-2004, 01:07 PM

None of them work, but thanks for the suggestion.

gbonvehi · 07-07-2004, 01:54 PM

dolem98, maybe there's a conflict with the kernel modules used as power managers (apm or acpi i think), if you have both on the kernel you should choose the one that suits you and don't use the other one. If they are modules you can unload the one that shouldn't be loaded. For newer machines generally the one that works is ACPI.

HuMJohn · 07-07-2004, 02:56 PM

Hrm...this is a strange one.....try this command and let us know if you find any difference or not:

shutdown -t30 -r

The -t tells shutdown to wait 30 seconds before switching to another run level, and of course, the -r is Reboot.

You can substitute the -h for the -r to see if it goes to a complete power off (via acpi or apm) and that may help you.

If you look in /etc/inittab, you will find that the infamous 'three-finger-salute' is translated to the comand: shutdown -t5 -r now.

Hope this helps somewhat.

Cerbere · 07-08-2004, 12:01 AM

Double-posting is against the rules.

Enjoy!
--- Cerbere

dolem98 · 07-08-2004, 02:28 AM

Yes I'm sorry I decided the slackware forum was probably a better place after I saw it.