Agent status discovering

Diablau · Post by **Diablau** » 11 Dec 2009 7:33

Hi!/Bonjour!

In Control-M Configuration Manager, I have an agent stuck on the discovering status. This is the Control-M Server Agent. I don't need this agent and I would like it to be on the disable status. The problem is that (even with the command line menu), when I try to change the status, it says that when an agent is Discovering, it is prohobited to chage its status. Is there something I can do to change it?
Thaks a lot!

Lau

gglau · Post by **gglau** » 11 Dec 2009 7:59

use ctmping at server to add agent

ctmping -NODEID <agent> -NODETYPE REGULAR -DISCOVER y

Diablau · Post by **Diablau** » 11 Dec 2009 8:10

Thanks, but it doesn't work, it says: The node type for Node ID tictrlm is unknown. Please wait for the node discovery to complete.

gglau · Post by **gglau** » 14 Dec 2009 8:06

Which version are you using?

Prior to 6.4 FP1, in AGSTAT folder, open any file in folder AGSTAT, and make change all occurences of hostname to the one in question. Change the character after AGSTAT to D. Save the edited file as a new file, using the hostname in question as filename (without extension).

For 6.4 FP1 and higher, perform the above in CTM server DB table CMR_NODES instead.

Diablau · Post by **Diablau** » 14 Dec 2009 8:24

Really nice gglau! Thanks a lot! It has worked great!

Diablau · Post by **Diablau** » 14 Dec 2009 8:47

oups! I've spoken too fast, after a little while, it changes automatically to "discovering" again

gglau · Post by **gglau** » 14 Dec 2009 9:04

NS may have remembered the the agent status. You probably need to stop CTM to manipulate the agent status manually.

Or, start the agent, ping it from CTM to make it available, disable it, and then shut it down.

Diablau · Post by **Diablau** » 15 Dec 2009 4:35

You was right gglau. I've stopped Ctrl-M services, made my changes, restart the services and eveything's stable now.
Thanks again!
Lau

philmalmaison · Post by **philmalmaison** » 15 Dec 2009 5:07

be sure that no jobs using the concerned nodeid, because if there are AJF they should automaticly put the wrong agent in discover mode

regards
philmalmaison