Page 1 of 1

Client can't seem to connect, debug output hangs at "debug1: channel request 0: window-change" for long time

Posted: Fri May 31, 2019 7:01 am
by A-Star
Hi all,

We are having this Solaris system that is having some trouble connecting to a CoreSFTP server.

I've tried running the client in verbose mode and received the following output:

userid@localhostname:~$ ssh -v -v userid@sftphostname
Sun_SSH_2.4, SSH protocols 1.5/2.0, OpenSSL 0x100020cf
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: Default value for UseOpenSSLEngine is 0
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to sftphostname [10.178.223.105] port 22.
debug1: Connection established.
debug1: ssh_kmf_check_uri: /export/home/userid/.ssh/identity
debug1: Identity file/URI '/export/home/userid/.ssh/identity' pubkey type UNKNOW N
debug1: ssh_kmf_check_uri: /export/home/userid/.ssh/id_rsa
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug2: key_type_from_name: unknown key type '-----END'
debug1: ssh_kmf_key_from_blob: blob length is 533.
debug1: Identity file/URI '/export/home/userid/.ssh/id_rsa' pubkey type ssh-rsa
debug1: ssh_kmf_check_uri: /export/home/userid/.ssh/id_dsa
debug1: Identity file/URI '/export/home/userid/.ssh/id_dsa' pubkey type UNKNOWN
debug1: Logging to host: sftphostname
debug1: Local user: userid Remote user: userid
debug1: Remote protocol version 2.0, remote software version CoreFTP-0.3.3
debug1: no match: CoreFTP-0.3.3
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_2.4
debug1: Creating a global KMF session.
debug1: My KEX proposal before adding the GSS KEX algorithm:
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-g roup-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,x509v3-sign-rsa,x509v3-sign-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour25 6,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour25 6,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc
debug2: kex_parse_kexinit: hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha2-256-9 6,hmac-sha2-512-96,hmac-sha1-96,hmac-md5,hmac-md5-96
debug2: kex_parse_kexinit: hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha2-256-9 6,hmac-sha2-512-96,hmac-sha1-96,hmac-md5,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: i-default
debug2: kex_parse_kexinit: i-default
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug1: Failed to acquire GSS-API credentials for any mechanisms (Unspecified GS S failure. Minor code may provide more information

)
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: My KEX proposal I sent to the peer:
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-g roup-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,x509v3-sign-rsa,x509v3-sign-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour25 6,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour25 6,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,3des-cbc
debug2: kex_parse_kexinit: hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha2-256-9 6,hmac-sha2-512-96,hmac-sha1-96,hmac-md5,hmac-md5-96
debug2: kex_parse_kexinit: hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha2-256-9 6,hmac-sha2-512-96,hmac-sha1-96,hmac-md5,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: i-default
debug2: kex_parse_kexinit: i-default
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug1: KEX proposal I received from the peer:
debug2: kex_parse_kexinit: diffie-hellman-group1-sha1,diffie-hellman-group14-sha 1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256
debug2: kex_parse_kexinit: ssh-rsa,rsa-sha2-512,rsa-sha2-256
debug2: kex_parse_kexinit: aes128-cbc,aes128-ctr,3des-cbc,blowfish-cbc,aes192-cb c,aes192-ctr,aes256-cbc,aes256-ctr,rijndael128-cbc,rijndael192-cbc,rijndael256-c bc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-cbc,aes128-ctr,3des-cbc,blowfish-cbc,aes192-cb c,aes192-ctr,aes256-cbc,aes256-ctr,rijndael128-cbc,rijndael192-cbc,rijndael256-c bc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-sha2-256,hmac-sha2-512,hmac-sha2-384,hmac-sha1,h mac-md5,none
debug2: kex_parse_kexinit: hmac-sha2-256,hmac-sha2-512,hmac-sha2-384,hmac-sha1,h mac-md5,none
debug2: kex_parse_kexinit: none,none
debug2: kex_parse_kexinit: none,none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-sha2-256
debug1: kex: server->client aes128-ctr hmac-sha2-256 none
debug2: mac_setup: found hmac-sha2-256
debug1: kex: client->server aes128-ctr hmac-sha2-256 none
debug1: Host key algorithm 'ssh-rsa' chosen for the KEX.
debug1: Peer sent proposed langtags, ctos:
debug1: Peer sent proposed langtags, stoc:
debug1: We proposed langtags, ctos: i-default
debug1: We proposed langtags, stoc: i-default
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 237/512
debug1: bits set: 2088/4096
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: ssh_kmf_key_from_blob: blob length is 277.
debug1: ssh_kmf_key_from_blob: blob length is 277.
debug1: ssh_kmf_key_from_blob: blob length is 277.
debug1: Host 'sftphostname' is known and matches the RSA host key.
debug1: Found key in /export/home/userid/.ssh/known_hosts:6
debug1: bits set: 2060/4096
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: set_newkeys: setting new keys for 'out' mode
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: set_newkeys: setting new keys for 'in' mode
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug2: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: Authentications that can continue: password,publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /export/home/userid/.ssh/identity
debug1: ssh_kmf_check_uri: /export/home/userid/.ssh/identity
debug1: Trying public key: /export/home/userid/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 533 lastkey eba070 hint 1
debug1: ssh_kmf_key_from_blob: blob length is 533.
debug2: input_userauth_pk_ok: fp 60:9f:7e:a5:67:4c:d5:b1:f8:6e:f1:32:06:cf:bc:81
debug1: ssh_kmf_check_uri: /export/home/userid/.ssh/id_rsa
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey)
debug2: TCP receive buffer size: 257744 B
debug1: SSH receive window size: 1030976 B
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug2: callback start
debug1: ssh_session2_setup: id 0
debug1: channel request 0: env
debug2: Sent request for environment variable LANG=C
debug1: channel request 0: env
debug2: Sent request for environment variable LC_CTYPE=
debug1: channel request 0: env
debug2: Sent request for environment variable LC_COLLATE=
debug1: channel request 0: env
debug2: Sent request for environment variable LC_TIME=
debug1: channel request 0: env
debug2: Sent request for environment variable LC_NUMERIC=
debug1: channel request 0: env
debug2: Sent request for environment variable LC_MONETARY=
debug1: channel request 0: env
debug2: Sent request for environment variable LC_MESSAGES=
debug1: channel request 0: env
debug2: Sent request for environment variable LC_ALL=
debug1: channel request 0: pty-req
debug1: channel request 0: shell
debug1: fd 4 setting TCP_NODELAY
debug2: callback done
debug1: channel 0: open confirm rwindow 65536 rmax 32768
debug2: client_check_window_change: changed
debug1: channel request 0: window-change
Received disconnect from 10.178.223.105: 2: Idle timeout...
debug1: Calling cleanup 0x36020(0x0)
debug1: Calling cleanup 0x3dde0(0x0)
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: Calling cleanup 0x51d78(0x0)


The client just stops responding at this one line "debug1: channel request 0: window-change" for a very long time until it idle timeout.

What could be the issue?

Re: Client can't seem to connect, debug output hangs at "debug1: channel request 0: window-change" for long time

Posted: Thu Jun 06, 2019 6:38 pm
by ForumAdmin
Use sftp instead of ssh