Problem with 2.2.19pre9 (Connection closed.)
Hello, after upgrading to 2.2.19pre9 (+ 2 NFS-patches, IPv6 enabled) idle connections tend to shut down without a visible reason: client->ssh server Last login: Mon Feb 19 2001 18:01:12 from client.domain Sun Microsystems Inc. SunOS 5.8 Generic February 2000 You have mail. server->Disconnected; connection lost (Connection closed.). Connection to server closed. client->uname -a Linux client 2.2.19pre9 #6 Thu Feb 15 09:26:46 MET 2001 i686 unknown Here is the relevant part of a tcpdump from this session: (The whole dump can be found here: http://www.tzi.de/~mager/linux.tcpdump ) [...] 10:15:17.336759 eth0 < server.domain.ssh > client.domain.afbackup: P 2242:2294(52) ack 1790 win 24616 (DF) 10:15:17.350719 eth0 > client.domain.afbackup > server.domain.ssh: . 1790:1790(0) ack 2294 win 31856 (DF) [...] 12:15:17.158963 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:15:18.506350 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:15:21.216267 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:15:26.636121 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:15:37.475848 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:15:59.155272 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:16:42.514137 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:17:42.512562 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:18:42.511239 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:19:42.509606 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:20:42.508124 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:21:42.506655 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) 12:22:42.505090 eth0 < server.domain.ssh > client.domain.afbackup: P 2293:2294(1) ack 1790 win 24616 (DF) [...] 14:23:10.527642 eth0 > client.domain.afbackup > server.domain.ssh: . 1789:1789(0) ack 2294 win 31856 (DF) 14:23:10.528676 eth0 < server.domain.ssh > client.domain.afbackup: R 2292303093:2292303093(0) win 0 (DF) [...] Any ideas? Thanks a lot for your help!! Regards Markus -- Markus Germeier [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with 2.2.19pre9 (Connection closed.)
Jes Sorensen <[EMAIL PROTECTED]> writes:
> I only see this for connections with incoming traffic where I don't
> send something out (like irc), whereas unused ssh connections seem to
> survive fine.
Just for the record: My example was an idle ssh connection!
I believe Alan is correct. I can't remember having this problem with
another linux box. I'll try to reproduce this with a linux box.
Thanks for your quick responses. Hopefully we can resolve this before
2.2.19 comes out!
Regards
Markus
--
Markus Germeier
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with 2.2.19pre9 (Connection closed.)
Hi all,
I did some further investigation and found the following:
It seems to me that this is a linux <-> solaris problem. I have no
problems with AIX 4.1.4, IRIX 6.5 or WIN2K. However all solaris boxes
I have access to (2.6, 7, 8, sparc and intel) give me a "connection
closed" after 2h, which is (at least I blelieve so ;-) the TCP timer
for keepalive.
Tell me if I can provide you with further data to nail down this bug.
Jes: I thought about your information that ssh connections do not show
this problem. I believe you are using ssh 2.3 or 2.4 from ssh.com,
right? 2.3 introduced a rekeying-feature which exchanges new keys
every 60 minutes, so the TCP keepalive is never triggered. (Due to a
bug which is still present in 2.4, we can't use these versions at my
site.)
HTH.
Regards,
Markus
--
Markus Germeier
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
