Displaying 20 results from an estimated 800 matches similar to: "istate / ostate error?"
2000 Jul 23
2
Work around Linux kernel bug provoked by nchan.c
The Linux implementation of TCP sockets has a bug which causes
shutdown(sock, SHUT_RD) to fail spuriously (ENOTCONN) if the write
side of the socket has already been shut down. If you are using SSH
port forwarding to tunnel HTTP through a firewall, nchan.c will tickle
this bug once for every HTTP exchange. You will therefore get lots of
useless, annoying error messages:
channel 2:
2000 Nov 22
2
fds closed after SIGCHLD bug still in newest version (fwd)
can someone confirm this? it does not happen on openbsd.
-------------- next part --------------
An embedded message was scrubbed...
From: Florian Wunderlich <fwunderlich at devbrain.de>
Subject: Re: fds closed after SIGCHLD bug still in newest version
Date: Wed, 22 Nov 2000 14:44:17 +0100
Size: 3926
Url:
2008 Jun 11
1
FW: ibuf_empty delayed efd
> -----Original Message-----
Damien Miller, 6/10/08 said:
>
> On Tue, 10 Jun 2008, Scott Neugroschl wrote:
>
> > I'm seeing something unusual in 5.0p1. Let me start by saying that
> I'm
> > on kind of an oddball
> > system (HP NonStop).
> >
> > What I'm seeing is that at the end of an scp session, the server
gets
> > stuck in a
2000 Jan 20
0
OpenSSH problem report on Linux 2.2.14.
I have been using OpenSSH for a while, and I would like to thank you
for the great package.
Here is a report of mysterious warning message lines, I get while I
use OpenSSH.
They don't seem to be serious, but annoying nevertheless.
version: openssh-1.2.1pre27
OS
Linux standard 2.2.14 #18 SMP Thu Jan 6 06:07:45 JST 2000 i586 unknown
(compiled with gcc 2.95.2)
Compiler
gcc -v
Reading
2000 Jan 07
2
possible clue on tcp forwarding problems
When I encounter the problem with TCP port forwarding locking up, I'll
see this on the client window (if I haven't invoked ssh with -q):
chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected
chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected
This is with Blowfish encryption. I have to kill and restart the client
when this happens.
Phil
2000 Oct 02
1
Open connections when using agent-forwarding
Hi!
I have problems with connections being left open with both 2.2.0p1 and the
latest snapshot when using agent-forwarding. (I didn't use this with older
versions, so I don't know whether this problem is older.)
Scenario:
I have a secret key that I run with ssh-agent on host "host-A". I then connect
to "host-B" using 'slogin -A host-B'. When executing a
2001 Mar 16
2
X forwarding from Linux -> Irix not working
I'm logging in from an irix machine to a linux machine (both running
openssh-2.5.1p2) and am unable to run any X applications.
I ran a verbose session and this happens:
debug: fd 6 IS O_NONBLOCK
debug: channel 0: new [X11 connection from host port 4572]
debug: X11 connection uses different authentication protocol.
debug: X11 rejected 0 i1/o16
debug: channel 0: read failed
debug: channel 0:
2001 Feb 22
3
intermittent stderr
The command "ssh ls -l /doesnotexist" gives various responses:
Running from a 200 MHz PentiumPro with dsa key added to ssh-agent:
Mistakes worst to fast machine:
To a faster 600 MHz dual processor i686 600 MHz machine:
ls: /doesnotexist: No such file or directory -- correct
nothing at all -- wrong
ls: select: Bad file descriptor -- wrong
2001 Feb 06
16
sftp client
As of Sunday evening, OpenSSH has an interactive sftp client. It should
be in the more recent snapshots.
It would be appreciated if you could test new client and find all the
bugs :) Please also have a read of the manpage and ensure that it
matches what is implemented.
I am working on fixing the ones that I know about, so please try to
stay up to date with the snapshots.
Thanks,
Damien
2002 Feb 05
0
New forkoff() and chan_wont_read/write() API
Markus,
How's this patch?
- a chan_wont_read()/chan_wont_write() API is added that is very much
like chan_read_failed()/chan_write_failed(), but for the debug
messages and chan_wont_*() don't ever call error()
The 3.0.2p1 channel_pre_x11_open() uses chan_*_failed() but looks
like it ought to use chan_wont_*() instead :)
- forkoff() no longer fakes EOF for SSHv2 (still
2007 Apr 09
10
[Bug 1306] Spurious : "chan_read_failed for istate 3" errors from sshd
http://bugzilla.mindrot.org/show_bug.cgi?id=1306
Summary: Spurious : "chan_read_failed for istate 3" errors from
sshd
Product: Portable OpenSSH
Version: 4.6p1
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo:
2001 Sep 28
1
[PATCH] fix for Linux hang on exit bug in 2.9.9p2
As you are now probably aware, the portability team for openssh still
has not fixed the hang-on-exit bug in the 2.9.9p2 release.
Attached is a patch for 2.9.9p2 that fixes the hang-on-exit bug for Linux
systems. It also adds a useful exit delay feature that has also not yet been
incorporated into the main sources.
For more information, see the SNFS (secure NFS) web page:
2000 Dec 07
1
Bugreport: Lines swallowed in std_out redirection
Hi,
we are using OpenSSH_2.3.0p1. When using non-interactive mode,
sometimes lines are swallowed from standard output:
root at hydra:~ # ssh anderson "ls -l /usr/sbin/sshd"
-rwxr-xr-x 1 root root 612344 Nov 25 20:26 /usr/sbin/sshd
root at hydra:~ # ssh anderson "ls -l /usr/sbin/sshd"
root at hydra:~ # ssh anderson "ls -l /usr/sbin/sshd"
-rwxr-xr-x 1
2000 Nov 22
0
openssh 2.3.0p1: chan_read_failed for istate 8
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
2007 May 17
4
[Bug 1306] Spurious : "chan_read_failed for istate 3" errors from sshd
http://bugzilla.mindrot.org/show_bug.cgi?id=1306
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #1281| |ok?
Flag| |
--- Comment #7 from Damien Miller <djm at
2007 Mar 23
7
4.6p1 chan_read_failed error
The 4.6p1 sshd is logging this error during remote commands or file
transfers:
error: channel 0: chan_read_failed for istate 3
Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d.
The commands and transfers work correctly, so the error message appears
to be spurious. The error message does not appear when processing logins.
Otherwise 4.6p1 is running without any apparent problems. This error
2001 Nov 14
6
[PATCH]: Patch to fix hang on exit bug under Linux and add optional exit delay
The hang-on-exit bug still hasn't been fixed in OpenSSH-3.0p1... :-(
Here again is the patch to fix this bug under Linux, updated for OpenSSH-3.0p1.
This has been exhaustively tested for six months now. It also add an exit
delay option that can be useful.
The patch does not lead to data loss under Linux.
Please see the Secure NFS page (SNFS) for further details:
2000 Nov 08
1
internal error: we do not read, but chan_read_failed
Hello,
The error message in the subject line occurs with the new 2.3.0 openssh
version and appeared in the previous snapshots on our Solaris systems. As far
as I remember it was reported, but have not seen any more about this. I have
looked into it a little bit.
First, the file session.c (line 1849 onwards):
debug("session_exit_message: release channel %d", s->chanid);
2000 May 15
0
Strange problem with X11 forwarding...
Ok...
This could be cockpit error, but I just don't see it. I've
installed OpenSSH 2.1.0 and I can't get X11 forwarding to work. I
don't recall having this problem under 1.2.3, but I don't use X11
forwarding often enough to really say that I actually saw it work
either.
Both sides are running OpenSSH-2.1.0-1 installed from rpm.
The client side is running RedHat Linux 6.1
2001 Oct 23
2
PAM problem - sshd segfault on Solaris
I'm using OpenSSH-2.9.9p2 on Solaris 8 sparc64. 2.9p2 worked fine, but
2.9.9p2+ is giving me trouble with one thing - sshd segfaults if I try to
connect and execute a command, such as "ssh machine ls". Otherwise it
works great. sshd will fork, and the child process segfaults.
CVS snapshot does the same thing.
I've narrowed this down somewhat. It will only happen if you use