Re: ssh hangs when executing a command

Further to my initial note above:

More log information:

Running sshd -d from a root shell on the laptop(delta). Captured the
debug output to a file.

Ran "ssh -v delta /bin/pwd" on the desktop.

It looks like the client and the server are BOTH requesting the other
to send the "no-more-sessions@xxxxxxxxxxx" and are in a deadly

Here are the pertinent (i.e., tail) portions of the debug information.
--------desktop doing the ssh -v invocation--------------

debug1: Next authentication method: publickey
debug1: Trying private key: /home/bill/.ssh/identity
debug1: Trying private key: /home/bill/.ssh/id_rsa
debug1: Offering public key: /home/bill/.ssh/id_dsa
debug1: Server accepts key: pkalg ssh-dss blen 433
debug1: read PEM private key done: type DSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
---->debug1: Requesting no-more-sessions@xxxxxxxxxxx
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending env LANGUAGE =
debug1: Sending env LC_ALL = en
debug1: Sending command: /bin/pwd

------------laptop doing the sshd -d invocation ------
Accepted publickey for bill from port 49782 ssh2
debug1: monitor_child_preauth: bill has been authenticated by
privileged process
debug1: temporarily_use_uid: 500/500 (e=0/0)
debug1: ssh_gssapi_storecreds: Not a GSSAPI mechanism
debug1: restore_uid: 0/0
debug1: SELinux support disabled
debug1: PAM: establishing credentials
debug1: PAM: establishing credentials
debug1: permanently_set_uid: 500/500
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 0 win 2097152
max 32768
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
---->debug1: server_input_global_request: rtype no-more-
sessions@xxxxxxxxxxx want_reply 0
User child is on pid 3522

(----> indicates the log entries in question)

Both ends of the communication were hung at the point where the above
logs end.

Still looking for help.


Bill Lee