Bug 119 - Occassionally, SSH failed to connect and timeout after 2 hrs!
Summary: Occassionally, SSH failed to connect and timeout after 2 hrs!
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: -current
Hardware: ix86 Linux
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-16 12:26 AEDT by Angus Lau
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angus Lau 2002-02-16 12:26:48 AEDT
Output with ssh -vvv
=====================
Tue Feb 12 04:10:04 HKT 2002
OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f
debug1: Seeding random number generator^M
debug1: Rhosts Authentication disabled, originating port will not be trusted.^M
debug1: ssh_connect: getuid 0 geteuid 0 anon 1^M
debug1: Connecting to vtms_hbbak [10.37.70.213] port 22.^M
debug1: Connection established.^M
debug3: Bad RSA1 key file /root/.ssh/identity.^M
debug2: key_type_from_name: unknown key type '-----BEGIN'^M
debug3: key_read: no key found^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f
debug1: Seeding random number generator^M
debug1: Rhosts Authentication disabled, originating port will not be trusted.^M
debug1: ssh_connect: getuid 0 geteuid 0 anon 1^M
debug1: Connecting to MYHOST [10.20.30.40] port 22.^M
debug1: Connection established.^M
debug3: Bad RSA1 key file /root/.ssh/identity.^M
debug2: key_type_from_name: unknown key type '-----BEGIN'^M
debug3: key_read: no key found^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug3: key_read: no space^M
debug2: key_type_from_name: unknown key type '-----END'^M
debug3: key_read: no key found^M
debug1: identity file /root/.ssh/identity type 1^M
debug1: unknown identity file /root/.ssh/id_rsa^M
debug1: identity file /root/.ssh/id_rsa type -1^M
debug1: unknown identity file /root/.ssh/id_dsa^M
debug1: identity file /root/.ssh/id_dsa type -1^M
ssh_exchange_identification: read: Connection reset by peer^M
debug1: Calling cleanup 0x8061610(0x0)^M
Tue Feb 12 06:11:39 HKT 2002
==============================
Normally should read
=====================
.....
debug1: unknown identity file /root/.ssh/id_rsa^M
debug1: identity file /root/.ssh/id_rsa type -1^M
debug1: unknown identity file /root/.ssh/id_dsa^M
debug1: identity file /root/.ssh/id_dsa type -1^M
debug1: Remote protocol version 1.99, remote software version OpenSSH_2.5.2p2^M
debug1: match: OpenSSH_2.5.2p2 pat ^OpenSSH^M
.....
Comment 1 Kevin Steves 2002-03-31 05:22:56 AEST
what is the timeout issue?  timeouts can be caused by filters
that maintain connection state and have timeouts; or TCP keepalives
or ???

this should probably be "invalid"
Comment 2 Angus Lau 2002-04-01 14:13:43 AEST
Before I make ssh connection, the time is 'Tue Feb 12 04:10:04 HKT 2002'. 
After the ssh failed to connect (ssh_exchange_identification: read: Connection 
reset by peer), the time is Tue Feb 12 06:11:39 HKT 2002. ssh waits for 2 hrs 
before declaring the connection fails!

Comment 3 Damien Miller 2002-04-17 12:51:33 AEST
OpenSSH doesn't second-guess your TCP stacks connect() function. There are
patches to implement shorter timeouts, see Bug #91
Comment 4 Damien Miller 2004-04-14 12:24:18 AEST
Mass change of RESOLVED bugs to CLOSED