socket closing question

[FRamsay at castelhq.com (FRamsay at castelhq.com)]

the socket is opened:

AF_INET, SOCK_STREAM

yes SO_KEEPALIVE is turned on.

I have not been able to reproduce the problem, I tore down the app and
re-started it to clear out everything.  So we'll see if it happens again.

The system doesn't have ethreal or tcpdump on it, but I'll put tcpdump on
and fire it up, if (when) the problem happens again hopefully that will
provide some insite.

                  -fjr

Frank Ramsay
Systems Programmer
Castel, Inc
100 Cummings Center
Suite 157h
Beverly, MA 01915
(978) 236 1000 (voice)
(978) 236 1197 (fax)
Email: framsay at castelhq.com


|---------+---------------------------->
|         |           kclark at CetaceanNe|
|         |           tworks.com (Kevin|
|         |           D. Clark)        |
|         |                            |
|         |           05/02/2003 10:39 |
|         |           AM               |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       FRamsay at castelhq.com                                                                                         |
  |       cc:       discuss at blu.org                                                                                              |
  |       Subject:  Re: socket closing question                                                                                  |
  >------------------------------------------------------------------------------------------------------------------------------|





FRamsay at castelhq.com writes:

> I should probably clarify, the local application did not close the
socket,
> but neither did the remote application.

What kind of socket, anyways?  SOCK_STREAM/TCP?

Is SO_KEEPALIVE set on this socket?  (note: this probably has nothing
to do with your problem)

> And yet the socket did close.  So I'm trying to figure out where the
socket
> originally closed and from there
> why the socket closed.

Can you reproduce this easily?  Can you trace what's going on on the
wire with tcpdump or Ethereal?

If you're using TCP, what is the relevant output of "netstat proto
tcp" on the two machines?

Can you trace what is going on with tcpdump?  If you're using UDP or
something else, this could be useful as well.  Sending us the relevant
output of tcpdump would be infinitely useful here...


Regards,

--kevin
--
Kevin D. Clark (kclark at CetaceanNetworks.com)
ADVERTISEMENT:  On Sunday May 4th, I'm riding my bicycle 100 miles
in the American Diabetes Association's Tour de Cure ride.  If you're
interested in sponsoring me, please send me email.