Hi, I had previously noticed some peculiar log entries of the form error: error: channel 0: internal error: we do not read, but chan_read_failed for istate 8 in my logs. They were harmless as far as I was concerned. I checked the list archives, where the same logs have been reported and no solution was presented. Recently I tried to use rsync over ssh for backup purposes. The remote end runs Solaris 2.7 and the local machine RedHat Linux 7.0. It fails with the error message: unexpected EOF in read_timeout Simultaneously an error is logged in the Solaris machine error: channel 0: internal error: we do not read, but chan_read_failed for istate 8 The same command works a remote Linux machine. Note that the same log entry is printed in the remote linux logs. Is it a known problem? Thanks for any help. Sarantis -- Sarantis Paskalis
hi, please try a recent snapshot from http://bass.directhit.com/openssh_snap does it fix this problem? On Mon, Jan 08, 2001 at 07:12:13PM +0200, Sarantis Paskalis wrote:> Hi, > > I had previously noticed some peculiar log entries of the form error: > > error: channel 0: internal error: we do not read, but chan_read_failed for > istate 8 > > in my logs. They were harmless as far as I was concerned. I checked the > list archives, where the same logs have been reported and no solution was > presented. > > Recently I tried to use rsync over ssh for backup purposes. The remote > end runs Solaris 2.7 and the local machine RedHat Linux 7.0. It fails > with the error message: > > unexpected EOF in read_timeout > > Simultaneously an error is logged in the Solaris machine > > error: channel 0: internal error: we do not read, but chan_read_failed for > istate 8 > > The same command works a remote Linux machine. Note that the same log > entry is printed in the remote linux logs. > > Is it a known problem? > Thanks for any help. > > Sarantis > > > -- > Sarantis Paskalis > >
On Mon, 8 Jan 2001, Markus Friedl wrote:> hi, please try a recent snapshot from > http://bass.directhit.com/openssh_snap > does it fix this problem?Hi, Unfortunately no. I installed openssh-20010108 on both remote solaris and local linux and it stills fails with the same error. Rsync with local solaris and remote linux succeeds though. It could be an rsync bug. Btw, the in the default sshd_config the LoglevelFacility is defined as AUTHPRIV, which does not exist in Solaris. Regards, Sarantis -- Sarantis Paskalis