1753753 Members
4978 Online
108799 Solutions
New Discussion юеВ

sftp connection closed

 
SOLVED
Go to solution
Ahmed_58
Regular Advisor

sftp connection closed

Hi,
I'm new with sftp, it working for some system but not for all, the error I'm getting after entring the password ...

Request for subsystem 'sftp' failed on channel 0
Connection closed

see below for more detail please....

#sftp -vvv telegram@bat-bcdr
Connecting to bat-bcdr...
OpenSSH_4.4p1-hpn12v11, OpenSSL 0.9.7l 28 Sep 2006
HP-UX Secure Shell-A.04.40.005, HP-UX Secure Shell version
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper
debug2: ssh_connect: needpriv 0
debug1: Connecting to bat-bcdr [10.40.3.46] port 22.
debug1: Connection established.
debug1: identity file /home/cduser/.ssh/id_rsa type -1
debug1: identity file /home/cduser/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1+sftpfilecontrol-v1.2-hpn12v17
debug1: match: OpenSSH_4.7p1+sftpfilecontrol-v1.2-hpn12v17 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.4p1-hpn12v11
debug2: fd 4 setting O_NONBLOCK
debug3: RNG is ready, skipping seeding
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,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:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 121/256
debug2: bits set: 503/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /home/cduser/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 7
debug3: check_host_in_hostfile: filename /home/cduser/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 8
debug1: Host 'bat-bcdr' is known and matches the RSA host key.
debug1: Found key in /home/cduser/.ssh/known_hosts:7
debug2: bits set: 495/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/cduser/.ssh/id_rsa (0)
debug2: key: /home/cduser/.ssh/id_dsa (0)
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug3: start over, passed a different list publickey,password,keyboard-interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/cduser/.ssh/id_rsa
debug3: no such identity: /home/cduser/.ssh/id_rsa
debug1: Trying private key: /home/cduser/.ssh/id_dsa
debug3: no such identity: /home/cduser/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 1
Password:
debug3: packet_send2: adding 32 (len 20 padlen 12 extra_pad 64)
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 0
debug3: packet_send2: adding 48 (len 10 padlen 6 extra_pad 64)
debug1: Authentication succeeded (keyboard-interactive).
debug2: fd 5 setting O_NONBLOCK
debug2: fd 6 setting O_NONBLOCK
debug1: Final hpn_buffer_size = 131072
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug1: Sending subsystem: sftp
debug2: channel 0: request subsystem confirm 1
debug2: fd 4 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: tcpwinsz: 32768 for connection: 4
Request for subsystem 'sftp' failed on channel 0
Connection closed
8 REPLIES 8
Steven E. Protter
Exalted Contributor

Re: sftp connection closed

Shalom,

Look at /var/adm/syslog/syslog.log on the target system.

There is something going on at that end. This is just a normal, I didn't get let in sequence, not a lot to go on here.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Tim Nelson
Honored Contributor

Re: sftp connection closed

Questions:

1) is the user telegram on bat-bcdr have a erstricted account ? ( e.g. no shell, or other shell ? User must have a shell to allow sftp even if no sh or ksh then it must have /opt/ssh/utils/sftponly

2) Is there any firewalls in the path ?

Ahmed_58
Regular Advisor

Re: sftp connection closed

hi,
The syslog.log display following;

May 9 08:45:58 bat-bcdr ftpd[18776]: FTP server (Revision 1.008 Version wuftpd-
2.6.1 Mon Feb 27 13:48:06 GMT 2006) ready.
May 9 08:46:00 bat-bcdr telnetd[18793]: getpid: peer died: Error 0
May 9 08:55:03 bat-bcdr sshd[18906]: Accepted keyboard-interactive/pam for tele
gram from 10.3.4.20 port 63898 ssh2

Jeeshan
Honored Contributor

Re: sftp connection closed

Salam Ahmed

DId you check that the target system enable the ssh or sftp?
a warrior never quits
Ahmed_58
Regular Advisor

Re: sftp connection closed

hi,
yes it shows it is running...
# ps -ef | grep ssh
root 15614 15612 1 09:06:20 pts/ta 0:00 grep ssh
root 24880 1 0 14:42:14 ? 0:00 /opt/ssh/sbin/sshd
Jeeshan
Honored Contributor

Re: sftp connection closed

hi again

your syslog doesn't point anything regarding this. but i suspect there shouwld be an entry like bellow in syslog.log

error: subsystem: cannot stat /usr/local/libexec/sftp-server:
No such file or directory

and

subsystem request for sftp failed, subsystem not found

right?????

did you found anything like that?
a warrior never quits
Jeeshan
Honored Contributor
Solution

Re: sftp connection closed

Hi

Take a look at this link

http://brneurosci.org/linuxsetup54.html
a warrior never quits
Ahmed_58
Regular Advisor

Re: sftp connection closed

Thanks all, it is workinf now.