connection reset by peer error (17 Views)
Reply
Occasional Contributor
Shariq Siddiqui
Posts: 3
Registered: ‎01-07-2001
Message 1 of 3 (17 Views)

connection reset by peer error

Hi,
On the console "connection reset by peer" meesages appear. I was wondering what could be causing this to happen. Any help is appreiciated.
TIA

Shariq
If you cannot achieve it the first time. DON'T try again!!!
Please use plain text.
Honored Contributor
Berlene Herren
Posts: 1,514
Registered: ‎10-11-1999
Message 2 of 3 (17 Views)

Re: connection reset by peer error

Could be caused by duplicate IP address on network. check nettl.LOG

#netfmt -f /var/adm/nettl.LOG00 > /tmp/file
#more /tmp/file

Could be caused by PC users not exiting applications gracefully, instead just "x-ing" them.

Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
Please use plain text.
Trusted Contributor
Craig Gilmore
Posts: 121
Registered: ‎01-08-2001
Message 3 of 3 (17 Views)

Re: connection reset by peer error

Basically the message:

connection reset by peer

is a catch all message. All that this means is that there was a TCP connection to another system that received a RST packet. The cause for this reset is as numerous as the types of applications you run on your system. The fact that this appeared on the console is of interest. First, check to make sure that the system logging deamon (syslogd) is properly running and you are getting messages posted to syslog. The message should log in /var/adm/syslog/syslog.log.

The only reason that this message would log to either the console or the syslog is that the process that controls the socket connection is either a system process (inetd) or the controlling process has previously died.

Is this something to be concerned about? It depends on whether you are getting work done or if this reset is causing work to stop. You can tell this by complaints or by applications failing. No failing applications or complaints... No issue.

I've not seen a duplicate IP address cause this error, but there is always a first time.

The PC application could cause this, but it would have to be one that cared about the network stack. Most don't and don't issue a close on the open socket. In my experience they wait for the keepalive process to clean up after them.
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation