Bug 615804

Summary: Disconnecting: Received open failure for non-opening channel 82.
Product: [Fedora] Fedora Reporter: Jan Kratochvil <jan.kratochvil>
Component: opensshAssignee: Jan F. Chadima <jchadima>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jchadima, mgrepl, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-29 09:19:23 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
full log none

Description Jan Kratochvil 2010-07-18 18:53:16 EDT
Created attachment 432741 [details]
full log

Description of problem:
Using Red Hat Bastion connection and it broke.

Version-Release number of selected component (if applicable):
peer: You should know (SSH-2.0-OpenSSH_4.3).

How reproducible:
Seen at least the second time.  Reproducibility like once a month.

Steps to Reproduce:
ssh -v -N -p 330
This time it lasted only about 10 hours.
Actual results:
Non-public channel 82, type 16.
Disconnecting: Received open failure for non-opening channel 82.

Expected results:
Continued connection.

Additional info:
~/.ssh/config: http://dyn.jankratochvil.net/nethome/.ssh/config?view=co
I hope this error cannot be due to the TCP connection problem.
Comment 1 Jan Kratochvil 2010-08-02 18:50:38 EDT
Another crash:

debug1: channel 79: new [stdio-forward]
debug1: getpeername failed: Bad file descriptor
debug1: multiplexing control connection
debug1: channel 80: new [mux-control]
debug1: channel_connect_stdio_fwd x86-64-5c-m2.test.redhat.com:22
debug1: channel 81: new [stdio-forward]
debug1: getpeername failed: Bad file descriptor
debug1: channel 80: free: mux-control, nchannels 82
debug1: channel 81: free: direct-tcpip: listening port 0 for x86-64-5c-m2.test.redhat.com port 22, connect from port 65535, nchannels 81
Disconnecting: Received open failure for non-opening channel 79.
debug1: compress outgoing: raw data 1277477, compressed 861025, factor 0.67
debug1: compress incoming: raw data 48766389, compressed 45244300, factor 0.93
Comment 2 Jan Kratochvil 2010-08-28 11:40:50 EDT
Disconnecting: Received open failure for non-opening channel 79.
debug1: compress outgoing: raw data 25928784, compressed 22897156, factor 0.88
debug1: compress incoming: raw data 880616222, compressed 842125435, factor 0.96
Comment 3 Bug Zapper 2011-06-01 09:31:20 EDT
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2011-06-29 09:19:23 EDT
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.