HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Showing results for 
Search instead for 
Did you mean: 

getpid: peer died: Error 0

Go to solution
Khalid Shakoor
Regular Advisor

getpid: peer died: Error 0

Hi Guruz,

One of my client facing unexpected cluster lock Queries error in lock disk,The issue was the path was change on one of my node then we updated the vglock configuration and compile the binary again and run the cluster again,Cluster was up running and we tested also fail over,Every thing is working fine and there is no more message unexpected cluster lock Queries.

Now after finish that job on same server we continuously received telnetd[7481]: getpid: peer died: Error 0 message in syslog and interval is 5 min,

I really appreciated if some body help me to resolved that issue.

Asif Sharif
Honored Contributor

Re: getpid: peer died: Error 0

Laurent Menase
Honored Contributor

Re: getpid: peer died: Error 0

Usually this is due to telnet sessions aborted by a reset - or syn/reset attack/tests.
- it can be due to a duplicate ip, the other system reseting the connection
- it can be due to a vulnerability scanner.

So the best is to take an nettl trace at interface layer, and check patch revision
- with some very old 11.11 or 11.23 ARPA patch version, we may get read() returning 0.

Khalid Shakoor
Regular Advisor

Re: getpid: peer died: Error 0