Error message in /var/adm/syslog/syslog.log

[Orlando De Oliveira R]

Hi,

That Meant he/she has this message that he/she appears in /var/adm/syslog/syslog.log....?


Mar 11 09:27:02 lrc telnetd[23829]: getpid : peer died: Error 0
Mar 11 09:27:03 lrc telnetd[23830]: getpid : peer died: Error 0
Mar 11 09:27:04 lrc telnetd[23835]: getpid : peer died: Error 0
Mar 11 09:27:06 lrc telnetd[23842]: getpid : peer died: Error 0
Mar 11 09:27:08 lrc telnetd[23845]: getpid : peer died: Error 0
Mar 11 09:27:10 lrc telnetd[23848]: getpid : peer died: Error 0
Mar 11 09:27:14 lrc telnetd[23852]: getpid : peer died: Error 0
Mar 11 09:27:14 lrc telnetd[23853]: getpid : peer died: Error 0
Mar 11 09:27:17 lrc telnetd[23894]: getpid : peer died: Error 0
Mar 11 09:27:18 lrc telnetd[23907]: getpid : peer died: Error 0
Mar 11 09:27:20 lrc telnetd[23910]: getpid : peer died: Error 0
Mar 11 09:27:22 lrc telnetd[23914]: getpid : peer died: Error 0

Thank you,

Orlando

[Armin Feller]

The message tell us that there where telnet requests which has unexpectedly been closed by requestor. Please check which system requests telnet access to your system.

Regards,
Armin

[Steve Steel]

Hi


Indeed closing telnet . Maybe in a script

Use verbose logging with #inetd -l.
The client ip or hostname is logged to /var/adm/syslog/syslog.log when the telnet makes the connection and inetd starts telnetd .

Steve Steel

[Paula J Frazer-Campbell]

Hi

These can be caused by users not logging off and just closing their window.

Paula

[Charlie Rubeor]

These all happened within twenty seconds. Does this happen very often?

If it does happen frequently, I would check the kernel parameters npty, nstrpty and nstrtel. It's possible that you are hitting the limit, in terms of allowable telnet sessions.

[Jeff Schussele]

Hi Orlando,

These are indeed caused by the telnet client closing unexpectedly.
It *almost* looks like a network issue - like a router between server & client dropped & all clients on the other side were just chopped off. But that's just speculation...

Rgds,
Jeff

[Fernando Silveira]

I had the same problem but the reason is that my application uses telnet as a way to verify the validity of an IP address. The problem is that i have no idea of how to close the connection in a friendly way... i used the shutdown() function and closesocket() and it still logs the same message.

If you have a running process which connects to telnet, you might have the same behavior if not disconnecting in a proper way.

[Monit Kapoor]

This error could also come if the system is out of npty's and won;t allow newer telnet sessions.

The fix is configure kernel parameters "npty" and "nstrpty" to a higher value.