Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
07-07-2004, 12:06 PM
|
#1
|
LQ Newbie
Registered: Mar 2004
Posts: 7
Rep:
|
Reboots locally not remotely
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?
|
|
|
07-07-2004, 12:14 PM
|
#2
|
LQ Guru
Registered: Mar 2004
Distribution: Slackware
Posts: 6,795
|
Quote:
then just as the machine finally reboots, the screen goes blank
|
Can you precise if reboot runs till the bios starts
Last edited by keefaz; 07-07-2004 at 12:16 PM.
|
|
|
07-07-2004, 12:34 PM
|
#3
|
Member
Registered: Jun 2004
Location: California - home of Slackware
Distribution: Slackware
Posts: 59
Rep:
|
Re: Reboots locally not remotely
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.........?
|
|
|
07-07-2004, 12:36 PM
|
#4
|
LQ Newbie
Registered: Mar 2004
Posts: 7
Original Poster
Rep:
|
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)
|
|
|
07-07-2004, 12:42 PM
|
#5
|
Senior Member
Registered: Jul 2003
Location: Wellington, NZ
Distribution: mainly slackware
Posts: 1,291
Rep:
|
this might sound silly but have you tried:
reboot &
or:
init 6 &
|
|
|
07-07-2004, 12:46 PM
|
#6
|
LQ Guru
Registered: Mar 2004
Distribution: Slackware
Posts: 6,795
|
or just by :
ssh "reboot"
|
|
|
07-07-2004, 02:07 PM
|
#7
|
LQ Newbie
Registered: Mar 2004
Posts: 7
Original Poster
Rep:
|
None of them work, but thanks for the suggestion.
|
|
|
07-07-2004, 02:54 PM
|
#8
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
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.
|
|
|
07-07-2004, 03:56 PM
|
#9
|
Member
Registered: Jun 2004
Location: California - home of Slackware
Distribution: Slackware
Posts: 59
Rep:
|
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.
|
|
|
07-08-2004, 01:01 AM
|
#10
|
Member
Registered: Dec 2002
Location: California
Distribution: Slackware & LFS
Posts: 799
Rep:
|
Double-posting is against the rules.
Enjoy!
--- Cerbere
|
|
|
07-08-2004, 03:28 AM
|
#11
|
LQ Newbie
Registered: Mar 2004
Posts: 7
Original Poster
Rep:
|
Yes I'm sorry I decided the slackware forum was probably a better place after I saw it.
|
|
|
All times are GMT -5. The time now is 01:33 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|