Linux – Hang and broken pipe when rebooting over ssh

linuxpiperedhatssh

I'm trying to reboot one box from another, using the following command:

ssh 10.0.0.26 'reboot --force'

I expect this to block for a short while until the other box reboots, then return. What I see happening is no activity for a while, then if I press a key, I get "Write failed: Broken pipe".

The reboot of the other box works just as expected, but I'd like to clear up the output on the local box, ideally without just hiding it all in /dev/null.

I'm using OpenSSH 5.3p1 on Redhat 6.

Edit: I've foundmy own solution; I'll add this as an answer below. Seems I can't accept this just yet, though. I guess this is to give others a chance to come in with a better solution.

Best Answer

You can schedule reboot instead of just rebooting immediately. Have a look at this post.

Related Solutions

SSH – How to Perform Diff Over SSH

You can do it with Bash's process substitution:

 diff foo <(ssh myServer 'cat foo')

Or, if both are on remote servers:

diff <(ssh myServer1 'cat foo') <(ssh myServer2 'cat foo')

Ssh – Rebooting access point via SSH with pexpect… hangs. Any ideas

In your first scenario (rebooting from ssh login): If your device is really rebooting, then all processes are killed, including the one connected to your ssh client. You shouldn't have to login after a reboot to kill old processes, since they cannot exist! I suspect your ssh client is not gracefully handling the forcible closing of the connection on the remote side, and so it hangs. You should be able to just close/kill it on your local system.

Sorry, I don't know much about expect, so I have no advice about its particular issues. However, if you want to script a remote reboot, it may be possible to set up passwordless ssh login via a keyfile, and then just do ssh root@mydevice reboot.

Best Answer

Related Solutions

SSH – How to Perform Diff Over SSH

Ssh – Rebooting access point via SSH with pexpect… hangs. Any ideas

Related Topic