search for: client_input_channel_req

Hi All, I am not sure if this is the same thing as the hang on exit bug, so sorry if this is a duplication of previous stuff. Essetntially I am experiencing ssh hangs with about .5% - 1% of my connections. I am running 2.9p2, on Solaris 7. I actually have empirical data on the hangings, as I wrote a script to create these connections in an endless loop, setting an alarm so I could recover

.... >> > >> > > debug1: Exit status -1 > > I put in a couple of debug statements in clientloop.c where exit_status is > set. It looks like the initialization of exit_status = -1 is the only point > where the value is modified. Looking closer at the sshd log: debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0 The code for this is in session_exit_message() and looks like: if (WIFEXITED(status)) { channel_request_start(s->chanid, "exit-status", 0); packet_put_int(WEXITSTATUS(status)); packet_send();...

...(none) user.info : debug2: channel 1: rcvd adjust 1049535 is_now: 693233^M Nov 3 12:27:14 (none) user.info : debug2: channel 1: rcvd adjust 1048580 is_now: 697384^M Nov 3 12:27:22 (none) user.info : debug2: channel 1: rcvd adjust 1049529 is_now: 695099^M Nov 3 12:28:30 (none) user.info : debug1: client_input_channel_req: channel 1 rtype keepalive at openssh.com reply 1^M ............ tun0 (channel-1) is unidirectional now and I close channel-0 manualy for testing: ............ Nov 3 12:28:33 (none) user.info : debug2: channel 0: rcvd ext data 22^M Nov 3 12:28:33 (none) user.info : netmask: Unknown host Nov 3 12...

https://bugzilla.mindrot.org/show_bug.cgi?id=3550 Bug ID: 3550 Summary: Key Conflict Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org Reporter:

...annel 0: input open -> closed connection hangs at this point whereas when it doesn't hang, ssh client log looks like this: ... debug2: channel 0: write failed debug2: channel 0: close_write debug2: channel 0: send eow debug2: channel 0: output open -> closed debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0 debug1: client_input_channel_req: channel 0 rtype eow at openssh.com reply 0 debug2: channel 0: rcvd eow ... and sshd log looks like this: ... debug1: server_input_channel_req: channel 0 request eow at openssh.com reply 0 debug2: channel...

...1 debug2: fd 3 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 64 bytes for a total of 1831 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: subsystem request accepted on channel 0 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: channel 0: close_read debug2: channel 0: input open -> closed debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: chann...

...how to make it work correctly? Here's an example of what I see when I run a remote xterm, and then close it immediately: polycut:~> ssh -n mahler xterm <I immediately hit CTRL-d on the xterm and the the following error in the original shell> channel_lookup: 0: bad id: channel free client_input_channel_req: channel 0: unknown channel <I hit CTRL-c to get control of the original shell> ^CKilled by signal 2. polycut:~> Thanks, Ed Ed Phillips <ed at udel.edu> University of Delaware (302) 831-6082 Systems Programmer III, Network and Systems Services finger -l ed at polycut.nss.udel.e...

...llowing code blocks. If successful first runs code block1 and then block2, otherwise the opposite. code1: debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed code2: 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: channel 0: close_read debug2: channel 0: input open -> closed Any help appreciated.. thanks

...re-sessions at openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys-00 at openssh.com want_reply 0 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 Last login: Tue Mar 27 00:50:05 2018 from 10.1.1.53 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 debug1: channel 0: free: client-session, nchannels 1 Connection to 192.168.1.100 closed. Transferred: sent 2892, received 2564 bytes, in 0.8 seconds Bytes per second: sent 3405.9, recei...

...debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: bash -c "/bin/ls /foo" /bin/ls: /foo: No such file or directory debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 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 2 Since the expected exit status is "127", and t...

On February 9, 2016 9:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker at nexbridge.com> > Cc: OpenSSH Devel List <openssh-unix-dev at mindrot.org> > Subject: Re: Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity > [...] > This one looks odd. The ssh session itself looks OK: it authenticates then > sends a printf shell command (basically, just a way

...debug1: channel 0: read<=0 rfd 5 len 0 debug1: channel 0: read failed debug1: channel 0: input open -> drain debug1: channel 0: close_read debug1: channel 0: input: no drain shortcut debug1: channel 0: ibuf empty debug1: channel 0: input drain -> closed debug1: channel 0: send eof debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: rcvd eof debug1: channel 0: output open -> drain debug1: channel 0: rcvd close debug2: channel 0: no data after CLOSE debug2: channel 0: no data after CLOSE debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1:...

...ho $i failed; done 10 failed [sturles at ulrik]~ $ for i in `seq 1 20`; do ssh -n pat cat 8kfile > /dev/null || echo $i failed; done [sturles at ulrik]~ $ If run with -v, the difference between correctly reporting and wrong reporting instances, is the following lines: Correct: debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: Exit status 0 Wrong: debug1: Exit status -1 More verbose versions: Correct: debug1: Sending command: cat 8kfile debug1: channel 0: open confirm rwindow 0 rmax 16384 debug1: channel 0: read<=0 rfd 7 len 0 debug1: channel 0: read failed...

..... debug1: mux_client_request_session: master session id: 2 As a result, I would suggest that the above code should be fixed to emit the message at level debug1 only AND the actual message content should be fixed, too. Note that the actual verbose output already says during disconnect ... debug1: client_input_channel_req: channel 2 rtype exit-status reply 0 debug1: client_input_channel_req: channel 2 rtype eow at openssh.com reply 0 debug1: channel 2: free: client-session, nchannels 3 debug1: channel 1: free: mux-control, nchannels 2 Shared connection to remote.example.com closed. USER at LOCALDOMAIN:~ $ debug1: Co...

...hannel 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 localhost port 5000, connect from 127.0.0.1 port 50076, nchannels 4 debug1: client_input_channel_req: channel 2 rtype exit-status reply 0 debug2: channel 2: rcvd eof debug2: channel 2: output open -> drain debug2: channel 2: obuf empty debug2: channel 2: close_write debug2: channel 2: output drain -> closed debug2: channel 2: rcvd close debug2: channel 2: almost dead debug2: channel 2: gc: n...

...Entering interactive session. > debug1: pledge: network > debug1: client_input_global_request: rtype hostkeys-00 at openssh.com > want_reply 0 > debug1: Sending environment. > debug1: Sending env LANG = en_US.UTF-8 > Last login: Tue Mar 27 00:50:05 2018 from 10.1.1.53 > 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 > debug1: channel 0: free: client-session, nchannels 1 > Connection to 192.168.1.100 closed. > Transferred: sent 2892, received 2564 bytes, in 0.8 seconds > Bytes per s...

...d debug1: channel 0: input: no drain shortcut debug1: channel 0: ibuf empty debug1: channel 0: input drain -> closed debug1: channel 0: send eof debug1: channel 0: rcvd eof debug1: channel 0: output open -> drain 8:47am up 49 day(s), 17:46, 2 users, load average: 0.52, 0.49, 0.46 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: 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 ar...

http://bugzilla.mindrot.org/show_bug.cgi?id=52 ------- Comment #47 from tsi at ualberta.ca 2007-02-17 03:06 ------- (In reply to comment #46) > Yes, but that workaround doesn't need the patch. However, with latest > patch, there is no hang when I run test2.ksh and exit from the shell on > linux. But it is not the case with HP-UX. So Im wondering what the > patch is doing with

...el open 0 debug: Entering interactive session. debug: client_init id 0 arg 0 debug: Requesting X11 forwarding with authentication spoofing. debug: Sending command: echo HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH debug: channel 0: open confirm rwindow 0 rmax 16384 debug: client_input_channel_req: rtype exit-status reply 0 debug: channel 0: rcvd eof debug: channel 0: output open -> drain debug: channel 0: rcvd close debug: channel 0: input open -> closed debug: channel 0: close_read debug: channel 0: obuf empty debug: channel 0: output drain -> closed debug: channel 0: close_write...

...annel_input_status_confirm: type 99 id 0 debug2: PTY allocation request accepted on channel 0 debug2: channel 0: rcvd adjust 2097152 debug3: receive packet: type 99 debug2: channel_input_status_confirm: type 99 id 0 debug2: shell request accepted on channel 0 debug3: receive packet: type 98 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug3: receive packet: type 98 debug1: client_input_channel_req: channel 0 rtype eow at openssh.com reply 0 debug2: channel 0: rcvd eow debug2: channel 0: close_read debug2: channel 0: input open -> closed debug3: receive packet: type 96 debug2: channel 0: r...