search for: chan_shutdown_write

...Tmp/ zoopy@core.stuff.net:~/Tmp/ zoopy@core.stuff.net's password: building file list ... done created directory /home3/zoopy/Tmp/ ./ _viminfo agrb agrb-tmp bubbleSort-occur.txt current.tar eltst.ba find.txt orig-tst.ba orig.bashrc pinghome.ba search.ba tags track-rep.ba tst tst.ba ./ channel 0: chan_shutdown_write: close() failed for fd5: Resource temporarily una vailable read error: Connection reset by peer _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

...debug1: Received SIGCHLD. debug1: session_by_pid: pid 31997225 debug1: session_exit_message: session 1 channel 2 pid 31997225 debug1: session_exit_message: release channel 2 debug1: channel 2: write failed debug1: channel 2: output open -> closed debug1: channel 2: close_write debug1: channel 2: chan_shutdown_write: shutdown() failed for fd13: Transport endpoint is not connected debug1: session_free: session 1 pid 31997225 debug1: channel 2: read<=0 rfd 13 len 0 debug1: channel 2: read failed debug1: channel 2: input open -> drain debug1: channel 2: close_read debug1: channel 2: input: no drain shortcut...

...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: Socket operation on non-socket rsync: read error: Connection reset by peer rsync error: error in rsync protocol data stream (code 12) at /tmp/rsync-2.5.6/io.c(177) I've tried many different command lines, but nothing seems to help. edw450-1-1 is a Solarix box here, r...

...channel %d: obuf empty", c->self); @@ -369,6 +414,27 @@ } } static void +chan_wont_write2(Channel *c) +{ + debug("channel %d: wont write", c->self); + switch (c->ostate) { + case CHAN_OUTPUT_OPEN: + debug("channel %d: output open -> closed", c->self); + chan_shutdown_write(c); /* ?? */ + c->ostate = CHAN_OUTPUT_CLOSED; + break; + case CHAN_OUTPUT_WAIT_DRAIN: + debug("channel %d: output drain -> closed", c->self); + chan_shutdown_write(c); + c->ostate = CHAN_OUTPUT_CLOSED; + break; + default: + debug("channel %d: chan_wont_write for o...

...Received SIGCHLD. debug1: session_by_pid: pid 620560410 debug1: session_exit_message: session 0 channel 0 pid 620560410 debug2: channel 0: request exit-status confirm 0 debug1: session_exit_message: release channel 0 debug2: channel 0: write failed debug2: channel 0: close_write debug2: channel 0: chan_shutdown_write: shutdown() failed for fd7: Socket is not connected debug2: channel 0: output open -> closed debug2: channel 0: read 0 from efd 9 debug2: channel 0: ibuf_empty delayed efd 9/(0) debug2: channel 0: read 0 from efd 9 debug2: channel 0: ibuf_empty delayed efd 9/(0) debug2: channel 0: read 0 from ef...

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,

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

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

...read debug2: channel 3: input open -> drain debug2: channel 3: ibuf empty debug2: channel 3: send eof debug2: channel 3: input drain -> closed debug2: channel 3: rcvd eof debug2: channel 3: output open -> drain debug2: channel 3: obuf empty debug2: channel 3: close_write debug2: channel 3: chan_shutdown_write: shutdown() failed for fd 6: Transport endpoint is not connected debug2: channel 3: output drain -> closed debug2: channel 3: rcvd close debug2: channel 3: send close debug2: channel 3: is dead debug2: channel 3: garbage collecting debug1: channel 3: free: direct-tcpip: listening port 5000 for l...

...still_open()) break; rekeying = (xxx_kex != NULL && !xxx_kex->done); diff -u openssh-2.9.9p2/nchan.c openssh-2.9.9p2J/nchan.c --- openssh-2.9.9p2/nchan.c Thu Sep 20 13:33:33 2001 +++ openssh-2.9.9p2J/nchan.c Thu Sep 27 22:09:31 2001 @@ -81,7 +81,7 @@ /* helper */ static void chan_shutdown_write(Channel *); -static void chan_shutdown_read(Channel *); +void chan_shutdown_read(Channel *); /* * SSH1 specific implementation of event functions @@ -524,7 +524,7 @@ c->self, c->wfd, strerror(errno)); } } -static void +void chan_shutdown_read(Channel *c) { if (compat20 &a...

...it declaration of function `gethostname' cipher.c: In function `cipher_by_name': cipher.c:450: warning: implicit declaration of function `strcasecmp' log.c: In function `log_facility_number': log.c:224: warning: implicit declaration of function `strcasecmp' nchan.c: In function `chan_shutdown_write': nchan.c:464: warning: implicit declaration of function `shutdown' packet.c: In function `packet_connection_is_on_socket': packet.c:196: warning: implicit declaration of function `getpeername' packet.c: In function `packet_connection_is_ipv4': packet.c:218: warning: implicit de...

...read debug2: channel 3: input open -> drain debug2: channel 3: ibuf empty debug2: channel 3: send eof debug2: channel 3: input drain -> closed debug2: channel 3: rcvd eof debug2: channel 3: output open -> drain debug2: channel 3: obuf empty debug2: channel 3: close_write debug2: channel 3: chan_shutdown_write: shutdown() failed for fd9: Invalid argument debug2: channel 3: output drain -> closed debug2: channel 3: rcvd close debug3: channel 3: will not send data after close debug2: channel 3: send close debug2: channel 3: is dead debug2: channel 3: garbage collecting debug1: channel 3: free: direct-tc...

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

...hannel_still_open()) break; rekeying = (xxx_kex != NULL && !xxx_kex->done); diff -ur openssh-3.0p1/nchan.c openssh-3.0p1J/nchan.c --- openssh-3.0p1/nchan.c Thu Oct 11 19:35:06 2001 +++ openssh-3.0p1J/nchan.c Tue Nov 13 15:55:52 2001 @@ -81,7 +81,7 @@ /* helper */ static void chan_shutdown_write(Channel *); -static void chan_shutdown_read(Channel *); +void chan_shutdown_read(Channel *); /* * SSH1 specific implementation of event functions @@ -533,7 +533,7 @@ c->self, c->wfd, strerror(errno)); } } -static void +void chan_shutdown_read(Channel *c) { if (compat20 &a...

...one debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: chan_shutdown_write: channel 0: (i0 o1 sock -1 wfd 6 efd 7 [write]) debug2: channel 0: output drain -> closed debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype eow at openssh.com reply 0 debug2: channel 0: rcvd eow debug2: chan_shutdown_read: cha...

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 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"

...el 0: request exit-status confirm 0 Jul 7 11:52:16 TOTO sshd[19553]: debug3: send packet: type 98 Jul 7 11:52:16 TOTO sshd[19553]: debug1: session_exit_message: release channel 0 Jul 7 11:52:16 TOTO sshd[19553]: debug2: channel 0: write failed Jul 7 11:52:16 TOTO sshd[19553]: debug2: channel 0: chan_shutdown_write (i0 o0 sock -1 wfd 11 efd 14 [ignore]) Jul 7 11:52:16 TOTO sshd[19553]: debug2: channel 0: send eow Jul 7 11:52:16 TOTO sshd[19553]: debug2: channel 0: output open -> closed Jul 7 11:52:16 TOTO sshd[19553]: debug2: channel 0: read<=0 rfd 12 len 0 Jul 7 11:52:16 TOTO sshd[19553]: debug2: c...