Red Hat Bugzilla – Bug 52198
in.telnetd errors on getpeername socket operation on non-socket
Last modified: 2007-04-18 12:36:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 95)
Description of problem:
when trying to invoke the telnet daemon (vers server-17.10-i386 and server-
17.18) returns with error in.telnetd:getpeername:socket operation on non-
socket. the daemon will however, run in debug mode and accept connections
while running in debug mode. This is happening on 5 different machines off
the cd install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.signed on the console as root execute /usr/sbin/in.telnetd
Actual Results: in.telnetd: getpeername: socket operation on non-socket
Expected Results: the daemon should have started
I've poked around a few of the config files to make sure telnet was setup
in services, etc.. nothing has been added to these servers and
reinstalling with defaults isn't solving the problem.
I've managed to clear up 3/4 of my problem.. sifting through the white papers I
found an article which stated that I should type, "chkconfig telnet on" then
issue a reset to xinetd and telnet spawns now when you try to open a session.
Also I've now installed RH Linux 7.1 on additional machines. This problem
seems to ONLY happen on Compaq Deskpro EN desktop machines. These are new
machines (as of July).. Hope this is helpful. Bret
forgot to note that trying to maunally start telnet I still receive the socket
You were trying to run telnetd directly, not through (x)inetd as it should, thus
I think the desktop, where it still isn't working, isn't running it properly
from xinetd either.
Marking NOTABUG. If you still can't get it to work, please post
/etc/xinet.d/telnet settings and what you get in /var/log/messages when
restarting xinetd (at least).