rebooting with telnet or ssh
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff and none of them worked. Raul
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
What response did you get from those commands? Did the machine reboot or did it stay at the same run level? This type of action is a risky one, especially if you on the other side of the globe from the machine you're rebooting. The biggest problem occurs when telnetd/sshd does not start after reboot ;-) -Kastus
Raul
It says the typical: Warning! The system is going is being rebooted(or something like this) Then I get back bash $. What I do then is I su in, and I run the runlevel command and I get: 3 6 which means that is supposed to be in rebooting runlevel! but it stays there. And dont worry about the distance, I am on a station which is two meters away from the server. Is there any other way around to get done a remote reboot? Thanks, Raul On Fri, 11 May 2001, Konstantin (Kastus) Shchuka wrote:
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
What response did you get from those commands? Did the machine reboot or did it stay at the same run level?
This type of action is a risky one, especially if you on the other side of the globe from the machine you're rebooting.
The biggest problem occurs when telnetd/sshd does not start after reboot ;-)
-Kastus
Raul
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
* Raul Gutierrez Segales
It says the typical: Warning! The system is going is being rebooted(or something like this)
Then I get back bash $. What I do then is I su in, and I run the runlevel command and I get: 3 6 which means that is supposed to be in rebooting runlevel! but it stays there.
Well, I cannot see why shutdown -r now should not work as root. Any other messages? -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
none, no other messages only The system is going down for reboot NOW! then I press enter and it gives me back bash. If it matters, I don think it does you should know that first, as I am using telnet(but it is the same with ssh) I log in with my normal user account and then I su in, because as you might know already SuSE has a default securtiy rule of not allowing remote root login. Do you think that makes a diference? Anyways, thanks for your help, and I am still looking, with your help, at a way for rebooting my server. Raul
* Raul Gutierrez Segales
none, no other messages only The system is going down for reboot NOW! then I press enter and it gives me back bash. If it matters, I don think it does you should know that first, as I am using telnet(but it is the same with ssh) I log in with my normal user account and then I su in, because as you might know already SuSE has a
Do you do 'su' or 'su -' ? -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
only su, why? On Fri, 11 May 2001, Mads Martin [iso-8859-1] J�rgensen wrote:
* Raul Gutierrez Segales
[May 11. 2001 15:05]: none, no other messages only The system is going down for reboot NOW! then I press enter and it gives me back bash. If it matters, I don think it does you should know that first, as I am using telnet(but it is the same with ssh) I log in with my normal user account and then I su in, because as you might know already SuSE has a
Do you do 'su' or 'su -' ?
-- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
* Raul Gutierrez Segales
only su, why?
Could you try with 'su -'. I doubt that it makes any difference, but in this case, it is all that springs to my mind right now. _From 'man su' -, -l, --login make the shell a login shell -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
ok, hold on, I am going to try On Fri, 11 May 2001, Mads Martin [iso-8859-1] J�rgensen wrote:
* Raul Gutierrez Segales
[May 11. 2001 15:18]: only su, why?
Could you try with 'su -'. I doubt that it makes any difference, but in this case, it is all that springs to my mind right now.
_From 'man su'
-, -l, --login make the shell a login shell
-- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
I have tried su - and I do get a shell login as I said, I thought as perhaps you thought it would be more powerful then regular su, but unluckily nothing. Any more ideas? Thanks for your help. Raul On Fri, 11 May 2001, Raul Gutierrez Segales wrote:
only su, why?
On Fri, 11 May 2001, Mads Martin [iso-8859-1] J�rgensen wrote:
* Raul Gutierrez Segales
[May 11. 2001 15:05]: none, no other messages only The system is going down for reboot NOW! then I press enter and it gives me back bash. If it matters, I don think it does you should know that first, as I am using telnet(but it is the same with ssh) I log in with my normal user account and then I su in, because as you might know already SuSE has a
Do you do 'su' or 'su -' ?
-- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
You said that after you get the 'system is going down'
message, you press enter. If you don't do that, what
happens? Does it just hang?
--Tim
--- Raul Gutierrez Segales
I have tried su - and I do get a shell login as I said, I thought as perhaps you thought it would be more powerful then regular su, but unluckily nothing. Any more ideas? Thanks for your help. Raul
On Fri, 11 May 2001, Raul Gutierrez Segales wrote:
only su, why?
On Fri, 11 May 2001, Mads Martin [iso-8859-1] J�rgensen wrote:
* Raul Gutierrez Segales
[May 11. 2001 15:05]: none, no other messages only The system is going down for reboot NOW! then I press enter and it gives me back bash. If it matters, I don think it does you should know that first, as I am using telnet(but it is the same with ssh) I log in with my normal user account and then I su in, because as you might know already SuSE has a
Do you do 'su' or 'su -' ?
-- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
yes it does, why?anyways it already rebooted, but I dont know it was clean, do you know any command to see the status(level of contigency of my hard drive). Thanks for your help. Raul On Fri, 11 May 2001, Tim Erlin wrote:
You said that after you get the 'system is going down' message, you press enter. If you don't do that, what happens? Does it just hang?
--Tim
--- Raul Gutierrez Segales
wrote: I have tried su - and I do get a shell login as I said, I thought as perhaps you thought it would be more powerful then regular su, but unluckily nothing. Any more ideas? Thanks for your help. Raul
On Fri, 11 May 2001, Raul Gutierrez Segales wrote:
only su, why?
On Fri, 11 May 2001, Mads Martin [iso-8859-1] J�rgensen wrote:
* Raul Gutierrez Segales
[May 11. 2001 15:05]: none, no other messages only The system is going down for reboot NOW! then I press enter and it gives me back bash. If it matters, I don think it does you should know that first, as I am using telnet(but it is the same with ssh) I log in with my normal user account and then I su in, because as you might know already SuSE has a
Do you do 'su' or 'su -' ?
-- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
humm interesting.... I just telnetted to my linux box as non root did su <password> then Im root, I do shutdown -r now and the linux machine reboots then befor I physically log on to the linux box, I telnetted again to the machine and loged on as non root no problem seems to work here Im using windows 98 telnet to the suse 7.1 kernel 2.4.0-4GB rob Raul Gutierrez Segales wrote:
It says the typical: Warning! The system is going is being rebooted(or something like this)
Then I get back bash $. What I do then is I su in, and I run the runlevel command and I get: 3 6 which means that is supposed to be in rebooting runlevel! but it stays there. And dont worry about the distance, I am on a station which is two meters away from the server. Is there any other way around to get done a remote reboot? Thanks,
Raul
On Fri, 11 May 2001, Konstantin (Kastus) Shchuka wrote:
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
What response did you get from those commands? Did the machine reboot or did it stay at the same run level?
This type of action is a risky one, especially if you on the other side of the globe from the machine you're rebooting.
The biggest problem occurs when telnetd/sshd does not start after reboot ;-)
-Kastus
Raul
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s+:+ a+ C+++ UL++++ P+ L++ E- W+++ N+++ o K- w O- M- V- PS PE Y PGP t- 5- X R* tv-- b++ DI- D G e* h* r- y++ ------END GEEK CODE BLOCK------
yeah I know it is odd, anyways, would you mind taking a look at /etc/inetd.conf and searching to see if thereis any comment about remote rebooting, perhaps: $ less /etc/inetd.conf | grep reboot(or shutdown) thanks, Raul On Fri, 11 May 2001, dizzy73 wrote:
humm interesting....
I just telnetted to my linux box as non root did su <password> then Im root, I do shutdown -r now and the linux machine reboots then befor I physically log on to the linux box, I telnetted again to the machine and loged on as non root no problem
seems to work here
Im using windows 98 telnet to the suse 7.1 kernel 2.4.0-4GB
rob
Raul Gutierrez Segales wrote:
It says the typical: Warning! The system is going is being rebooted(or something like this)
Then I get back bash $. What I do then is I su in, and I run the runlevel command and I get: 3 6 which means that is supposed to be in rebooting runlevel! but it stays there. And dont worry about the distance, I am on a station which is two meters away from the server. Is there any other way around to get done a remote reboot? Thanks,
Raul
On Fri, 11 May 2001, Konstantin (Kastus) Shchuka wrote:
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
What response did you get from those commands? Did the machine reboot or did it stay at the same run level?
This type of action is a risky one, especially if you on the other side of the globe from the machine you're rebooting.
The biggest problem occurs when telnetd/sshd does not start after reboot ;-)
-Kastus
Raul
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s+:+ a+ C+++ UL++++ P+ L++ E- W+++ N+++ o K- w O- M- V- PS PE Y PGP t- 5- X R* tv-- b++ DI- D G e* h* r- y++ ------END GEEK CODE BLOCK------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Raul Gutierrez Segales wrote:
yeah I know it is odd, anyways, would you mind taking a look at /etc/inetd.conf and searching to see if thereis any comment about remote rebooting, perhaps: $ less /etc/inetd.conf | grep reboot(or shutdown)
grepping on those words revealed nothing here is the pertinent sections of my inetd.conf hth rob time stream tcp nowait root internal time dgram udp wait root internal ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode smtp stream tcp nowait root /usr/sbin/sendmail sendmail -bs shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L login stream tcp nowait root /usr/sbin/tcpd in.rlogind talk dgram udp wait root /usr/sbin/tcpd in.talkd ntalk dgram udp wait root /usr/sbin/tcpd in.talkd pop3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/popper -s http-rman stream tcp nowait.10000 nobody /usr/sbin/tcpd /usr/sbin/http-rman swat stream tcp nowait.400 root /usr/sbin/swat swat
thanks, Raul
On Fri, 11 May 2001, dizzy73 wrote:
humm interesting....
I just telnetted to my linux box as non root did su <password> then Im root, I do shutdown -r now and the linux machine reboots then befor I physically log on to the linux box, I telnetted again to the machine and loged on as non root no problem
seems to work here
Im using windows 98 telnet to the suse 7.1 kernel 2.4.0-4GB
rob
Raul Gutierrez Segales wrote:
It says the typical: Warning! The system is going is being rebooted(or something like this)
Then I get back bash $. What I do then is I su in, and I run the runlevel command and I get: 3 6 which means that is supposed to be in rebooting runlevel! but it stays there. And dont worry about the distance, I am on a station which is two meters away from the server. Is there any other way around to get done a remote reboot? Thanks,
Raul
On Fri, 11 May 2001, Konstantin (Kastus) Shchuka wrote:
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
What response did you get from those commands? Did the machine reboot or did it stay at the same run level?
This type of action is a risky one, especially if you on the other side of the globe from the machine you're rebooting.
The biggest problem occurs when telnetd/sshd does not start after reboot ;-)
-Kastus
Raul
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s+:+ a+ C+++ UL++++ P+ L++ E- W+++ N+++ o K- w O- M- V- PS PE Y PGP t- 5- X R* tv-- b++ DI- D G e* h* r- y++ ------END GEEK CODE BLOCK------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s+:+ a+ C+++ UL++++ P+ L++ E- W+++ N+++ o K- w O- M- V- PS PE Y PGP t- 5- X R* tv-- b++ DI- D G e* h* r- y++ ------END GEEK CODE BLOCK------
well the only things i have unhashed in my inetd.conf are: ftp pop3 and telnet which I am planning to has right away cause its insecure Perhaps you need shell and a few other services to execute a few commands like the ones refered to changing the runlevel and shutting down or rebooting. Thanks, have a nice weekend you all, Raul On Fri, 11 May 2001, dizzy73 wrote:
Raul Gutierrez Segales wrote:
yeah I know it is odd, anyways, would you mind taking a look at /etc/inetd.conf and searching to see if thereis any comment about remote rebooting, perhaps: $ less /etc/inetd.conf | grep reboot(or shutdown)
grepping on those words revealed nothing here is the pertinent sections of my inetd.conf
hth rob
time stream tcp nowait root internal time dgram udp wait root internal ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode smtp stream tcp nowait root /usr/sbin/sendmail sendmail -bs shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L login stream tcp nowait root /usr/sbin/tcpd in.rlogind talk dgram udp wait root /usr/sbin/tcpd in.talkd ntalk dgram udp wait root /usr/sbin/tcpd in.talkd pop3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/popper -s http-rman stream tcp nowait.10000 nobody /usr/sbin/tcpd /usr/sbin/http-rman swat stream tcp nowait.400 root /usr/sbin/swat swat
thanks, Raul
On Fri, 11 May 2001, dizzy73 wrote:
humm interesting....
I just telnetted to my linux box as non root did su <password> then Im root, I do shutdown -r now and the linux machine reboots then befor I physically log on to the linux box, I telnetted again to the machine and loged on as non root no problem
seems to work here
Im using windows 98 telnet to the suse 7.1 kernel 2.4.0-4GB
rob
Raul Gutierrez Segales wrote:
It says the typical: Warning! The system is going is being rebooted(or something like this)
Then I get back bash $. What I do then is I su in, and I run the runlevel command and I get: 3 6 which means that is supposed to be in rebooting runlevel! but it stays there. And dont worry about the distance, I am on a station which is two meters away from the server. Is there any other way around to get done a remote reboot? Thanks,
Raul
On Fri, 11 May 2001, Konstantin (Kastus) Shchuka wrote:
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
What response did you get from those commands? Did the machine reboot or did it stay at the same run level?
This type of action is a risky one, especially if you on the other side of the globe from the machine you're rebooting.
The biggest problem occurs when telnetd/sshd does not start after reboot ;-)
-Kastus
Raul
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s+:+ a+ C+++ UL++++ P+ L++ E- W+++ N+++ o K- w O- M- V- PS PE Y PGP t- 5- X R* tv-- b++ DI- D G e* h* r- y++ ------END GEEK CODE BLOCK------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s+:+ a+ C+++ UL++++ P+ L++ E- W+++ N+++ o K- w O- M- V- PS PE Y PGP t- 5- X R* tv-- b++ DI- D G e* h* r- y++ ------END GEEK CODE BLOCK------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Fri, May 11, 2001 at 05:12:24PM -0400, Raul Gutierrez Segales wrote:
Does anybody has an idea why I am not able remotely reboot my server with ssh or telnet. The thing is that the keyboard and the graphic display card are dead. I have been looking lots of way to do this but havent found. I have tried as root from telnet and ssh the following commands: init 0 init 6 shutdown -r now halt poweroff
and none of them worked.
I guess you no longer have this problem, but since I deal with Linux boxes around the globe daily, I figured I'd give my own experiences with this in case it helps out other people. Every time I've seen a machine in this state, I've been able to do a 'ps ax | grep reboot' (or halt, or shutdown, or whatever) and find a line that looks like: 17356 ? D 0:00 reboot The 'D' means 'uninterruptible sleep', which implies (correctly) that that process isn't ever going to finish. You can't even kill -9 it. Often, a 'reboot -f' will work (that says "don't call shutdown, force reboot".) -tara
participants (6)
-
dizzy73
-
Konstantin (Kastus) Shchuka
-
Mads Martin Jørgensen
-
Raul Gutierrez Segales
-
Tara L Andrews
-
Tim Erlin