search for: o128

...rded 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: shutdown() failed for fd5 [i1 o128]: Tr...

...d" warning messages were observed on the linux 2.2.14 kernel with earlier release of openssh. The same happens when I used the port-forwarded HTTP connection. But this time, after accessing such http connections, I noticed that there are now cases of "[i1 o16] " as opposed to [i1 o128]" in the warning messages. Following is a copy of real warning message I collected a few minutes ago. [o128 meant the 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...

...ote-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 endpoint is not connected chan...

...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 with kernel 2.2.16. debug: channel 2:...

...nnel 0: no data after CLOSE debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug2: !channel_still_open. debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.0 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 --------------------------------- Prior to haning situation: (normal execution): debug2: callback start d...

...input drain -> wait_oclose debug1: channel 0: send ieof debug1: channel 0: rcvd oclose debug1: channel 0: input wait_oclose -> closed debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 X11 connection from X.X.X.X port 1482 (t4 r2 i8/0 o128/0 fd 4/4) Waiting for forwarded connections to terminate... The following connections are open: #2 X11 connection from X.X.X.X port 1482 (t4 r0 i4/0 o16/0 fd 8/8) debug1: Transferred: stdin 0, stdout 0, stderr 164 bytes in 1.7 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 96.3...

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

...different authentication protocol. debug1: X11 rejected 1 i1/o16 debug1: channel 1: read failed debug1: channel 1: input open -> drain debug1: channel 1: close_read debug1: channel 1: write failed debug1: channel 1: output open -> closed debug1: channel 1: close_write debug1: X11 closed 1 i2/o128 debug1: channel 1: rcvd eof debug1: channel 1: FORCE input drain Then I press CTRL-D on the client... debug1: channel 0: rcvd eof debug1: channel 0: output open -> drain debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: client_inp...

...channel 1: close_read debug1: channel 1: input: no drain shortcut debug1: channel 1: ibuf empty debug1: channel 1: input drain -> closed debug1: channel 1: send eof debug1: channel 1: write failed debug1: channel 1: output open -> closed debug1: channel 1: close_write debug1: X11 closed 1 i8/o128 debug1: channel 1: send close debug1: channel 1: rcvd close debug1: channel 1: is dead debug1: channel_free: channel 1: status: The following connections are open: #0 client-session (t4 r0 i1/0 o16/0 fd 6/7) #1 x11 (t7 r3 i8/0 o128/0 fd 9/9) X connection to ratbert:11.0 broken (explicit kill o...

...0: rcvd close debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.6 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 Wrong: debug1: Sending command: cat 1kfile debug1: channel 0: o...

...nternal error: we do not read, but chan_read_failed for istate 8 debug1: channel 0: closing efd 10 debug1: channel 0: send close debug1: channel 0: rcvd close debug1: channel 0: full closed2 debug1: channel_free: channel 0: status: The following connections are open: #0 server-session (t4 r0 i8/0 o128/0 fd 8/8) However if I comment out from session.c the call to 'chan_read_failed' (which I assume was not there previously), then I get: debug1: channel 0: close_write debug1: Received SIGCHLD. debug1: tvp!=NULL kid 1 mili 100 debug1: session_by_pid: pid 10918 debug1: session_exit_messag...

...bug1: channel 0: rcvd close debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 Failure: OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL 0x0090581f debug1:...

...When the session is shutdown (type "exit" in shell), it is hanging: - Server: ... debug1: channel 0: is dead debug1: channel_free: channel 0: server-session, nchannels 4 - Client: debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) #1 authentication agent connection (t4 r3 i1/0 o128/0 fd 7/7) debug1: channel_free: channel 0: dettaching channel user ^CKilled by signal 2. debug1: Calling cleanup 0x4000f70a(0x0) debug1: Calling cleanup 0x4000f892(0x0) Only when the client is shutdown with ^C, the connection will...

...nnel 1: no data after CLOSE debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) #1 x11 (t4 r3 i8/0 o128/0 fd 10/10) debug1: channel_free: channel 0: dettaching channel user debug1: channel 1: rcvd close debug2: channel 1: no data after CLOSE debug1: channel 1: is dead debug1: channel_free: channel 1: status: The following connections are open: #1 x11 (t4 r3 i8...

...debug: channel 0: close_read debug: channel 0: obuf empty debug: channel 0: output drain -> closed debug: channel 0: close_write debug: channel 0: send close debug: channel 0: full closed2 debug: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds debug: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug: Exit status 0 NORMAL BEHAVIOUR ssh -v gabriel "echo HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH" SSH Version Op...

...bug1: channel 0: rcvd close debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.2 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status -1 (ssh2, no -n flag, exit status is 0) 3:32pm.orangecrush: ~> ssh -v qa...

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:

...bug1: channel 0: close_read debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.0 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 127 debug1: writing PRNG seed to file /export/home/jpaint/.ssh/prng_seed Connection closed

...ug1: channel 0: send eof debug1: session_free: session 0 pid 1699 debug1: channel 0: send close debug1: channel 0: closing efd 9 debug1: channel 0: rcvd close debug1: channel 0: full closed2 debug1: channel_free: channel 0: status: The following connections are open: #0 server-session (t4 r0 i8/2 o128/0 fd 7/7) Connection closed by remote host. debug1: Calling cleanup 0x805bf00(0x0) debug1: Calling cleanup 0x8051190(0x0) debug1: Calling cleanup 0x8061f60(0x0) ------------------------------------------- Client: SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x00906...

...debug1: channel 0: rcvd eof debug1: channel 0: rcvd close debug1: channel 0: input open->closed debug1: channel 0: close_read debug1: channel 0: send close debug1: channel 0: full closed2 debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) debug1: channel_free: channel 0: dettaching channel user debug2: !channel_still_open. debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 14.5 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status -1 rsync error: unexplained error (code 255) at...