System Log error: xinetd -Transport endpoint is not connected

then · 12-08-2002, 03:36 AM

Hi

I got the following the following errors in my freshly-installed RH8 system, I can't make any sense of them
****************************
xinetd[960]: warning: can't get client address: Transport endpoint is not connected
xinetd[904]: warning: can't get client address: Transport endpoint is not connected
xinetd[893]: warning: can't get client address: Transport endpoint is not connected
*******************************
I custom installed RH with NO web-servers and with Sendmail and Postfix as my MTAs. No other software has been installed.

I would appreciate any guidance / tips to help me understand these errors.

Thanks and Regards
theN

irish_rover · 12-08-2002, 09:00 AM

Ok one way to track it down is to.......

Disable all of the xinetd processes and then turn them all back on one at a time and see who is causing the problem.

You might want to take a look at webmin just to make this a bit easier. www.webmin.com

askmemyname · 01-02-2008, 08:36 AM

The problem is the wait = yes option. For TCP connections xinetd seems to try and pass sockets around, instead of starting the server and redirecting STDIN/STDOUT.

Set wait = no for TCP streams. This is what I did to fix this exact same problem I was having. Below is my final configuration in /etc/xinetd.d/myservice:

Code:

service mycustomservice
{
        disable         = no
        type            = UNLISTED
        server          = /home/askmemyname/myservice.pl
        id              = mycustomservice-stream
        socket_type     = stream
        protocol        = tcp
        user            = root
        wait            = no
        port            = 12345
}