ctmagent/tcp: bind: Address already in use

[Carme Torca]

Hi,

I have this messages in one server syslog.
Does anyone knows what are they??
They are repeating every 10 minuts!!

inetd[719]: ctmagent/tcp: bind: Address already in use
inetd [719]: ctmagent/tcp: Service enabled

Thanks very much!,
Carmen.

[Eric Antunes]

Hi Carmen,

It means that the port is busy (already in use). Check it with:

netstat -a | grep

Check the following thread - specially Armin Feller solution - that may work for you:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=51467

Best Regards,

Eric Antunes

[Kent Ostby]

Also, check the entry for ctmagent in the inetd.conf file to make sure its correct.

[Muthukumar_5]

ctmagent is trying to bind on running address there. What is there in /etc/services for that ctmagent.

And inetd.conf entry for that service there.

Check network status as,

netstat -na | grep 'service port'

Recongiure inetd as inetd -c and post the log informations too.

HTH.

[Jeff Schussele]

Hi Carmen,

Appears someone/something tried to restart the Control-M SW. It "normally" uses port 7008/tcp I believe. BUT Control-M is an on-demand utility called out of the inetd.conf, so in this case it may be that the Control-M server is trying to start/restart the same job before it's finished it's previous incarnation.
I'd check with whomever support Control-M or is responsible for it's server as it's the server that controls what happens on the clients.
You also should check that:
1) You don't have dupe entries in inetd.conf for Control-M - ctmagent
2) You don't have dupe entries in the services for it as well.

HTH,
Jeff

[Prashant Zanwar_4]

ctmagent is agent for controlM. This is a job-scheduling software. ECS-ControlM. I believe it's from BMC.

ctmagent talks to controlM server. Check for duplicate entries in /etc/services of port numbers and also if anything is wrong in /etc/inetd.conf.

you can do following also to check ctmagent.

su - ctmagent
ag_menu
a menu will pop-up..just check the status, it has several options.
you can also do a ctmping to your server to check if communication is ok. Also there is a method to see if jobs are getting kicked ot not.

Hope this helps
Prashant