openssh 2.3.0p1: chan_read_failed for istate 8

[Andreas Hartmann]

Hallo all!


I've found a repeatable problem concerning openssh 2.3.0p1 running on a
Linux-box with kernel 2.2.17. I compiled ssh from sources with
pam-support. Let me describe what I'm doing:

rsync -e ssh --delete --exclude "/Daten/test*" --exclude
/Daten/anonymous --exclude /Daten/comp_logs --exclude
/Daten/ehemalige_rwgsysm/cache --exclude
/Daten/CONFIGMAN/DATAIN/CONFIGMAN/DATAIN -va root at sysman-ftp:/Daten
/Daten

After some time of running rsync, I get in /var/log/warn of the
ssh-server the following message:
sshd[16709]: error: channel 0: internal error: we do not read, but
chan_read_failed for istate 8
and the session has been broken (it breakes at different points, not
always at the same position).

In the mailinglist, I found a patch from John Horne (15.11.2000), which
I applied. But the problem consists even with the patch, but now without
the message in warnings. Now, I enabled debugging in ssh_config. This is
what ssh-client with debugging says (with the above command; a lot of
output (more than 10.000 files) of normal working rsync cutted):

debug: Seeding random number generator
debug: ssh_connect: getuid 0 geteuid 0 anon 0
debug: Connecting to sysman-ftp [10.48.1.77] port 22.
debug: Seeding random number generator
debug: Allocated local port 630.
debug: Connection established.
debug: Remote protocol version 1.99, remote software version
OpenSSH_2.3.0p1
debug: no match: OpenSSH_2.3.0p1
Enabling compatibility mode for protocol 2.0
debug: Local version string SSH-2.0-OpenSSH_2.3.0p1
debug: send KEXINIT
debug: done
debug: wait KEXINIT
debug: got kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha
1
debug: got kexinit: ssh-dss
debug: got kexinit:
3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,aes192-
cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysa

tor.liu.se
debug: got kexinit:
3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,aes192-
cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc at lysa

tor.liu.se
debug: got kexinit: hmac-sha1,hmac-md5,hmac-ripemd160 at openssh.com
debug: got kexinit: hmac-sha1,hmac-md5,hmac-ripemd160 at openssh.com
debug: got kexinit: none,zlib
debug: got kexinit: none,zlib
debug: got kexinit:
debug: got kexinit:
debug: first kex follow: 0
debug: reserved: 0
debug: done
debug: kex: server->client 3des-cbc hmac-sha1 none
debug: kex: client->server 3des-cbc hmac-sha1 none
debug: Sending SSH2_MSG_KEX_DH_GEX_REQUEST.
debug: Wait SSH2_MSG_KEX_DH_GEX_GROUP.
debug: Got SSH2_MSG_KEX_DH_GEX_GROUP.
debug: bits set: 524/1024
debug: Sending SSH2_MSG_KEX_DH_GEX_INIT.
debug: Wait SSH2_MSG_KEX_DH_GEX_REPLY.
debug: Got SSH2_MSG_KEXDH_REPLY.
debug: Host 'sysman-ftp' is known and matches the DSA host key.
debug: bits set: 535/1024
debug: len 55 datafellows 0
debug: dsa_verify: signature correct
debug: Wait SSH2_MSG_NEWKEYS.
debug: GOT SSH2_MSG_NEWKEYS.
debug: send SSH2_MSG_NEWKEYS.
debug: done: send SSH2_MSG_NEWKEYS.
debug: done: KEX2.
debug: send SSH2_MSG_SERVICE_REQUEST
debug: service_accept: ssh-userauth
debug: got SSH2_MSG_SERVICE_ACCEPT
debug: authentications that can continue: publickey
debug: next auth method to try is publickey
debug: try pubkey: /root/.ssh/id_dsa
debug: read DSA private key done

[now, the rsync-command is running and datas are sent ...]

debug: client_input_channel_req: rtype exit-status reply 0
debug: channel 0: rcvd eof
debug: channel 0: output open -> drain
debug: channel 0: rcvd close
debug: channel 0: input open -> closed
debug: channel 0: close_read
debug: channel 0: obuf empty
debug: channel 0: output drain -> closed
debug: channel 0: close_write
debug: channel 0: send close
debug: channel 0: full closed2
debug: channel_free: channel 0: status: The following connections are
open:
  #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1)

debug: Transferred: stdin 0, stdout 0, stderr 0 bytes in 5.1 seconds
debug: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug: Exit status 0
unexpected EOF in read_timeout

I'm wondering about the message of ssh debug, that no data has been
transferred. This is not correct. There has been a lot of data
transferred until this message!

I'm using this command for about half a year (some versions of ssh ago)
and had no problems until the last change of the version from 2.2.0p1 to
2.3.0p1.


Could you please help me? If you have some more questions, feel free to
ask. I can do tests for you if you want to!

Thanks in advance
Kind regards
Andreas Hartmann