Re: port timeout
- From: Frank Fegert <fra.nospam.nk@xxxxxx>
- Date: Fri, 29 Dec 2006 09:35:38 +0100
esokol@xxxxxxxxxx wrote:
I have an issue where it appears after 12 hours the UNIX side of a TCP
port which has been receiving "keepalive" messages from the PC side no
longer responds to that message. This causes the port to be closed as
far as I can tell. I have a port monitoring program on the PC and the
port goes away after 12 hours if the only traffic has been the
keepalive messages. If the port sends a real message within 12 hours,
the port does not close.
It works on several systems but doesn't work on another. I was
wondering if anyone could suggest some UNIX parameters I could look at
to see if there is some "12 hour" idle limit which would cause the UNIX
system not to respond..
AFAIK there's no "kill all open sockets after $TIME" parameter
on Unix systems. Unless data transfer has ceased, that is. Session
timeouts should all be handled by the server and client application.
Please provide some more information on your environment: LAN vs.
dialup? Firewall involved? Service/App./Protokoll used? If it is
a predictable connection loss after 12h, i would also suggest to
run tcpdump on the connection and truss on the server side app-
process handling that particular connection. With tcpdump you'll
be able to figure who is sending the FIN (Client or Server). With
truss, you'll be able to see if/why the server process is ending
the connection. Be aware, that tcpdump as well as truss produce
large amounts of output.
Regards,
Frank
.
- References:
- port timeout
- From: esokol
- port timeout
- Prev by Date: Help with IPv6
- Next by Date: Re: using pax in place of tar
- Previous by thread: port timeout
- Next by thread: HP 3800N print driver
- Index(es):
Relevant Pages
|
