Bug 98756 - SSH Connections Hang/Timeout on large amounts of text output under redhat linux 8.0
Summary: SSH Connections Hang/Timeout on large amounts of text output under redhat lin...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openssh
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL: http://www.openssh.org
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-08 15:43 UTC by Nick Lange
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-07-15 21:53:59 UTC
Embargoed:


Attachments (Terms of Use)
list of packages for our particular install (3.59 KB, text/plain)
2003-07-08 15:43 UTC, Nick Lange
no flags Details

Description Nick Lange 2003-07-08 15:43:01 UTC
On a minimized redhat 8.0 install commands like strace, or untarring a large
file will cause the session to slow to a crawl and freeze. I suspect that this
is actually any command with large amounts of output but cannot confirm.
Furthermore, we have several redhat linux boxes with other package sets
including this that do not exhibit this behaviour. Therefore, I suspect that the
package may be the cause... but exactly which I do not know.
(I've tried switching from en_US.utf-8 to en_US to no avail)

We are using Putty .53b as a client; however, I can not confirm this to be a bug
with their software.

SSH Packages:
openssh-3.4p1-2
openssh-server-3.4p1-2
openssh-clients-3.4p1-2


example command:
strace ssh image@<host> cat somefile

the strace will begin and you can watch the output slow to a crawl, and finally
 stop after an unknown period of time (in a couple cases).

I have 


Additional info:
See attached package list.

Comment 1 Nick Lange 2003-07-08 15:43:48 UTC
Created attachment 92800 [details]
list of packages for our particular install

package list

Comment 2 Nick Lange 2003-07-15 21:53:59 UTC
The Bug is in PuTTY, not OpenSSH.

rpm -qail done from within a putty terminal direct induces the lockup.
rpm -qail done through a known good server connecting the the problem server w/
openssh client works flawlessly.
rpm -qial from console of known good server to problem server works flawlessly.
Will follow up with the putty team.

Thanks,
nick



Note You need to log in before you can comment on or make changes to this bug.