can you identify this error message?

This error message was printed on an ssh session while 'df
-k' was hung
because of some sort of NFS problem (automounter was stuck
in the 'D'
state).

channel 3: chan_read_failed for istate 1

The cause of the problem is clear (NFS) but I'm sort of
puzzeled as to
the source of the error string.  Does any one have any idea
as to where
that error message could have originated?

Cheers,

-J

--

On Tue, Jun 26, 2007 at 03:07:28PM -1000, Joshua Hoblitt
wrote:
> This error message was printed on an ssh session while
'df -k' was hung
> because of some sort of NFS problem (automounter was
stuck in the 'D'
> state).
> 
> channel 3: chan_read_failed for istate 1
> 
> The cause of the problem is clear (NFS) but I'm sort of
puzzeled as to
> the source of the error string.  Does any one have any
idea as to where
> that error message could have originated?

Codesearch to the rescue:

  http://www.google.c
om/codesearch?q=chan_read_failed+for+istate&hl=en&bt
nG=Search+Code


I'd say it was pretty clearly an SSH error 

Dustin
-- 
gentoo-amd64gentoo.org mailing list

Joshua Hoblitt wrote:
> This error message was printed on an ssh session while
'df -k' was hung
> because of some sort of NFS problem (automounter was
stuck in the 'D'
> state).
> 
> channel 3: chan_read_failed for istate 1
> 
> The cause of the problem is clear (NFS) but I'm sort of
puzzeled as to
> the source of the error string.  Does any one have any
idea as to where
> that error message could have originated?
> 
> Cheers,
> 
> -J
> 
> --
that would be ssh barfing on you.

-- 
=======================================================
Mike Doty                      kingtaco -at- gentoo.org
Gentoo Council
Gentoo Infrastructure
Gentoo/AMD64 Strategic Lead
GPG: E1A5 1C9C 93FE F430 C1D6  F2AF 806B A2E4 19F4 AE05
=======================================================
-- 
gentoo-amd64gentoo.org mailing list

On Tue, Jun 26, 2007 at 09:01:21PM -0500, Dustin J. Mitchell
wrote:
> On Tue, Jun 26, 2007 at 03:07:28PM -1000, Joshua
Hoblitt wrote:
> > This error message was printed on an ssh session
while 'df -k' was hung
> > because of some sort of NFS problem (automounter
was stuck in the 'D'
> > state).
> > 
> > channel 3: chan_read_failed for istate 1
> > 
> > The cause of the problem is clear (NFS) but I'm
sort of puzzeled as to
> > the source of the error string.  Does any one have
any idea as to where
> > that error message could have originated?
> 
> Codesearch to the rescue:
> 
>   http://www.google.c
om/codesearch?q=chan_read_failed+for+istate&hl=en&bt
nG=Search+Code
> 
> 
> I'd say it was pretty clearly an SSH error 

Nice catch -- that must have been caused by the `reboot -f`
it took to
take the system down. ;)

-J

--