search for: chan_shutdown_read

...ome time I have routinely websurfed across a forwarded TCP connection using SSH. The other end of the TCP tunnel connects to a Squid proxy cache on the same machine. This usually works. But I see lots of error messages on each end of the form Jun 13 13:22:02 tunnel sshd[32378]: error: channel 0: chan_shutdown_read: shutdown() failed for fd5 [i1 o128]: Transport endpoint is not connected Jun 13 13:22:11 tunnel sshd[32378]: error: channel 2: chan_shutdown_read: shutdown() failed for fd10 [i1 o128]: Transport endpoint is not connected Jun 13 13:24:50 tunnel sshd[32378]: error: channel 0: chan_shutdown_read: shu...

...connection was closed. But o16 seems to suggest that output was open. from nchan.h: #define CHAN_OUTPUT_OPEN 0x10 #define CHAN_OUTPUT_WAIT_DRAIN 0x20 #define CHAN_OUTPUT_WAIT_IEOF 0x40 #define CHAN_OUTPUT_CLOSED 0x80 So something seems to be wrong.] chan_shutdown_read failed for #12/fd16 [i1 o16]: Transport endpoint is not connected chan_shutdown_read failed for #9/fd13 [i1 o128]: Transport endpoint is not connected chan_shutdown_read failed for #13/fd17 [i1 o128]: Transport endpoint is not connected chan_shutdown_read failed for #8/fd12 [i1 o128]: Transport end...

...here ssh established the connection to remote-host and shell prompt was displayed. Warning messages shown: These are just a few examples. Each time a new connection is made (and cut) for, say, the connection to the remote web server via port forwarding, lines similar to the following were shown. chan_shutdown_read failed for #8/fd12 [i1 o128]: Transport endpoint is not connected chan_shutdown_read failed for #8/fd12 [i1 o128]: Transport endpoint is not connected chan_shutdown_read failed for #11/fd15 [i1 o128]: Transport endpoint is not connected chan_shutdown_read failed for #10/fd14 [i1 o128]: Transport en...

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

...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: chan_shutdown_read: shutdown() failed for fd7 [i1 o128]: Transport endpoint is not connected Here's a complete debugging trace of one such forwarded channel. This is SSH1 protocol; I haven't got the setup to do SSH2 yet. The remote server is 2.0.12 F-SECURE SSH on Solaris 2.6; I am using openssh 2.1.1p4 wi...

...diff -u openssh-2.9.9p2/channels.h openssh-2.9.9p2J/channels.h --- openssh-2.9.9p2/channels.h Mon Sep 17 23:51:14 2001 +++ openssh-2.9.9p2J/channels.h Thu Sep 27 22:16:44 2001 @@ -219,6 +219,7 @@ void chan_mark_dead(Channel *); void chan_init_iostates(Channel *); void chan_init(void); +void chan_shutdown_read(Channel *); typedef void chan_event_fn(Channel *); diff -u openssh-2.9.9p2/clientloop.c openssh-2.9.9p2J/clientloop.c --- openssh-2.9.9p2/clientloop.c Mon Sep 17 23:51:14 2001 +++ openssh-2.9.9p2J/clientloop.c Fri Sep 28 12:47:09 2001 @@ -84,6 +84,7 @@ /* import options */ extern Option...

I am running OpenSSH 2.9p1 on SunOS 5.7 w/4-24-2001 patch cluster. Like many other users I am seeing the hanging session on logout with background processes. This is a huge problem for me as I centrally manage 50+ machines with rdist across ssh. Instead of just complaining about the problem I thought I would put my CS degree to use and try to track down the problem myself. For starters,

...} } diff -ur openssh-3.0p1/channels.h openssh-3.0p1J/channels.h --- openssh-3.0p1/channels.h Thu Oct 11 19:35:06 2001 +++ openssh-3.0p1J/channels.h Tue Nov 13 15:55:52 2001 @@ -218,6 +218,7 @@ void chan_mark_dead(Channel *); void chan_init_iostates(Channel *); void chan_init(void); +void chan_shutdown_read(Channel *); typedef void chan_event_fn(Channel *); diff -ur openssh-3.0p1/clientloop.c openssh-3.0p1J/clientloop.c --- openssh-3.0p1/clientloop.c Thu Oct 11 19:36:09 2001 +++ openssh-3.0p1J/clientloop.c Tue Nov 13 16:06:36 2001 @@ -84,6 +84,7 @@ /* import options */ extern Options optio...

In the changelog, there is an entry: 20001129 - (djm) Back out all the serverloop.c hacks. sshd will now hang again if there are background children with open fds. Does this mean that this is regarded as expected (and correct) behavior, that should not change in the future, or does it mean that this behavior is a known problem that someone will eventually fix? --Adam -- Adam McKenna

I'm still seeing problems when I use TCP connection forwarding across SSH to surf the web. I see lots of error messages of the form channel 1: chan_shutdown_read: shutdown() failed for fd7 [i1 o128]: Transport endpoint is not connected And I see occasional connection lockups. Both ends are running openssh-2.1.1p1. Phil

...problem: when I set up port forwarding for HTTP, running Squid at one end as an HTTP proxy and a browser at the other end (Netscape, IE) everything works fine, I can tunnel HTTP requests through OpenSSH but I keep seeing the following error messages that mess up my display really bad: channel 14: chan_shutdown_read: shutdown() failed for fd23 [i1 o16]: Transport endpoint is not connected channel 28: chan_shutdown_read: shutdown() failed for fd37 [i1 o16]: Transport endpoint is not connected (There are very many of these, they never end). I noticed that if I start the client with "ssh -q" or if I s...

...1, SSH protocols 1.5/2.0, OpenSSL 0x0090702f Error message: > rsync -e ssh -rav --exclude=SunWS_cache --exclude='*.o' --progress --stats amackenz@edw450-1-1:Code . amackenz@edw450-1-1's password: Warning: No xauth data; using fake authentication data for X11 forwarding. channel 0: chan_shutdown_read: close() failed for fd-1: Socket operation on non-socket stty: : Invalid argument stty: : Invalid argument rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) channel 0: chan_shutdown_write: close() failed for fd-1: Soc...

...g message just before we get a shell prompt when connecting to some of our servers through openssh. All our test servers are running the same software build (distribution) and the same version of openssh yet only some of them occasionally see the problem. This is the message we get: chan_shutdown_read failed for #0/fd4: Transport endpoint is not connected It is not clear what relation the warning message may have to the other 2 bugs. The warning message does not seem to indicate that shell will either hang or kill the parent sshd. I am willing to test various things to try and help i...

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

...******** *** 98,103 **** --- 98,106 ---- { debug("channel %d: read failed", c->self); switch (c->istate) { + case CHAN_INPUT_WAIT_DRAIN: + case CHAN_INPUT_CLOSED: + break; case CHAN_INPUT_OPEN: debug("channel %d: input open -> drain", c->self); chan_shutdown_read(c);

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:

...TIONS: should never update the channel states @@ -137,6 +139,28 @@ } } static void +chan_wont_read_12(Channel *c) +{ + debug("channel %d: wont read", c->self); + switch (c->istate) { + case CHAN_INPUT_OPEN: + debug("channel %d: input open -> drain", c->self); + chan_shutdown_read(c); + c->istate = CHAN_INPUT_WAIT_DRAIN; +#if 0 + if (buffer_len(&c->input) == 0) { + debug("channel %d: input: no drain shortcut", c->self); + chan_ibuf_empty(c); + } +#endif + break; + default: + debug("channel %d: chan_wont_read for istate %d", + c-...

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

On Mon, 21 Sep 2020 at 09:53, Hisashi T Fujinaka <htodd at twofifty.com> wrote: > OK, NetBSD-current amd64, NetBSD-9-amd64, and NetBSD-9-i386 all pass all > tests. MacOS, well, I always try it but it has problems. What's the problem on OS X? We test on it regularly (El Capitan and High Sierra) and the only problem I'm aware of is that the native libcrypto on High Sierra is

On 30/06/2023 09:56, Damien Miller wrote: > It's very hard to figure out what is happening here without a debug log. > > You can get one by stopping the listening sshd and running it manually > in debug mode, e.g. "/usr/sbin/sshd -ddd" Or starting one in debug mode on a different port, e.g. "-p99 -ddd"