Operating System - HP-UX
1752815 Members
6092 Online
108789 Solutions
New Discussion юеВ

"inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

 
TheJuiceman
Super Advisor

"inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

Hello gang,

I am getting repeating messages in my syslog as follows:

inetd[8567]: ident/tcp: Connection from localhost (127.0.0.1)

If I execute "inetd -l" I can turn logging on. If I execute it again, it turns it off and the messages stop. Keep in mind that I have to execute it twice to first turn on logging and then turn it off to make the messages stop.

However, are there security implications by turning off logging and how can I directly fix this problem that I have?

Thanks for the help, as always!!!
7 REPLIES 7
Lennart Wiklund
Occasional Visitor

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog


Check in file /etc/rc.config.d/netdaemons
for export INETD_ARGS=

This file is read during startup from /sbin/init.d/inetd

Darrel Louis
Honored Contributor

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

Hi,

As already mentioned, you can enale logging via the netconf file.

More important do you need the ident services, if not remove it from your inetd.conf file.
Ident is mostly required in a MC/SG environment.


Darrel
TheJuiceman
Super Advisor

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

This is happening on our systems that are in a ServiceGuard cluster. Any thoughts short of just running inetd -l to turn off all logging totally? I'm sure there must be some configuration/security setting that's not right. Thanks.
TheJuiceman
Super Advisor

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

Our netdaemons file has this entry...
export INETD_ARGS="-s"
Thanks.
TheJuiceman
Super Advisor

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

I am still having this problem. This sequence of messages repeats in the syslog every 10 seconds...

Oct 18 23:47:05 host inetd[21846]: hacl-cfg/tcp: Connection from 127.0.0.1 a
t Wed Oct 18 23:47:05 2006
Oct 18 23:47:05 host inetd[21847]: ident/tcp: Connection from 127.0.0.1 at W
ed Oct 18 23:47:05 2006
Oct 18 23:47:05 host inetd[21849]: hacl-cfg/tcp: Connection from 127.0.0.1 a
t Wed Oct 18 23:47:05 2006
Oct 18 23:47:05 host inetd[21850]: ident/tcp: Connection from 127.0.0.1 at W
ed Oct 18 23:47:05 2006
Oct 18 23:47:05 host inetd[21852]: hacl-cfg/tcp: Connection from 127.0.0.1 a
t Wed Oct 18 23:47:05 2006
Oct 18 23:47:05 host inetd[21853]: ident/tcp: Connection from 127.0.0.1 at W
ed Oct 18 23:47:05 2006

What is causing this error and how can I correct it? We just upgraded this server from 11.11 to 11.23 and we are still getting these messages. Thanks for your help.
someonexh
New Member

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

Did anyone have a fix for this? I have this same problem and it is filling up OpenView with messages also.

Thanks.
Wouter Jagers
Honored Contributor

Re: "inetd: ident/tcp: connection from localhost (127.0.0.1)" entries in syslog

From http://www.informit.com/articles/article.asp?p=349748&seqNum=7&rl=1 :

[...]
The entries you see for hacl-cfg come from the cluster configuration daemon (cmclconfd) that gathers information about LAN cards and volume groups. It also distributes the cluster binary file. During the startup of the cluster, all nodes are communicating with each other to ensure that the cluster is formed correctly and also to elect a cluster coordinator. If cmcld needs to gather information, it will do so by making a request to a cmclconfd process├в actually to a network socket being managed by inetd. inetd is listening for requests on port 5302, and it is inetd that will actually spawn the cmclconfd daemon.
[...]

Seems related to cluster startup, but I wouldn't know why you keep getting them. I'd say have a read on that webpage.

My MC/SG training is still pending, so this is all I can do for now.. it just so happened that I'm trying to get documented on these things at the moment :)

Cheers
an engineer's aim in a discussion is not to persuade, but to clarify.