"telnetd[18284]: getpid: peer died: Error 0"

[Sandeep_2]

Hi Admins,

I have N4000 server with HP-UX V11:00, 64 bit installed on it. User are getting disconnected randomly. After investigating, I found that /var/adm/syslog/syslog.log contains the error "telnetd[18284]: getpid: peer died: Error 0 "
This is newly installed server & latest patch bundle is applied on that server.

I don't know what is causing this problem.

Thanks,
Sandeep.

[Rita C Workman · Accepted solution]

Well, since you are already covered for latest patches...

What do you have ntpy and nstrpty set to in your kernel?
You may need to increase these. They take very little memory...so don't worry there. I think the default is something like 60 or 90.
On my systems I have it set to 800....

Just a thought,

[James R. Ferguson]

Hi:

Modify (regenerate) your kernel parmeters as follows:

npty 400
nstrpty 400
nstrtels 400

...JRF...

[Sandeep_2]

Hi,

I have already set the npty, nstrpty & nstrtels to 400. But the problem still continues.

Thanks,
Sandeep.

[Timothy Czarnik]

Sandeep,

This is a longshot, but if you have the shell environment variable TMOUT set, after the specified period of inactivity the login will terminate automatically.

Can you check to see if you are setting the TMOUT variable anywhere in your profiles, or if it is somehow getting set somewhere else?

Hope this helps!

-Tim

[Sandeep_2]

Hi all,

The TMOUT is set to 0 for all users.


Thanks,
Sandeep.

[Timothy Czarnik]

Sandeep,

I've not used the TMOUT variable, so I don't know if setting this to 0 means to timeout after 0 seconds of inactivity or to not timeout at all.

If it were me, and the TMOUT variable is set to 0 (meaning you don't want to use it), I'd get rid of it in the profiles altogether and see if it makes a difference.

-Tim

[Kofi ARTHIABAH]

Are your users going through some sort of firewall? because if they are then its possible that they are being dropped on TCP expiration.

The was a posting a couple of months ago,
http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0xedba119c3420d411b66300108302854d,00.html

but that pointed to the ARPA patch installation.