topic Socket IP behaviour, when EPIPE? in Operating System - HP-UX

Socket IP behaviour, when EPIPE?

Enrico Venturi — Mon, 30 Jun 2003 14:40:58 GMT

Hello again,
I've two processes exchangig data via an IP connection; at a certain moment one of them writes data on a socket and receives errno = EPIPE;
I'm sure that the remore reader dodn't close the socket and didn't exit or aborted the communication.
My question is: are there any causes local to the writer processes affecting the result of the data sending?
Is it possible that the processes chain from one machine to the other one is interrupted on the local sender side?
I've no more explaination for this problem ...
thanks
Enrico

Re: Socket IP behaviour, when EPIPE?

Massimo Bianchi — Mon, 30 Jun 2003 14:53:41 GMT

Hi,
did you checked the PATH ?

I found some with the EPIPE error,
like

PHNE_18553
or latest arpa PHNE_28538

HTH,
Massimo

Re: Socket IP behaviour, when EPIPE?

Michael Steele_2 — Mon, 30 Jun 2003 16:18:37 GMT

Sockets / ports can be reviewed with 'netstat' and 'lsof'.

lsof -i tcp:#### (* where port number = #### *)
lsof -i udp:####

netstat -an | grep -i ####

Also use 'tcpdump' to review ip messages coming into the socket from the sending host.

tcpdump ####

Here's were you can get:

tcpdump:

http://hpux.cict.fr/hppd/hpux/Networking/Admin/tcpdump-3.6.2/

lsof:

http://hpux.cict.fr/hppd/hpux/Sysadmin/lsof-4.64/

Re: Socket IP behaviour, when EPIPE?

Umapathy S — Mon, 30 Jun 2003 16:34:24 GMT

Venturi,
EPIPE is generated when you try to write to a socket that is already dead. Check the pattern of this happening.
Run the applications through tusc to pinpoint.
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.5/

HTH,
Umapathy