Agens is in "Discover" status - how to delete it?

Dilbert · Post by **Dilbert** » 28 Dec 2007 9:47

philmalmaison wrote:or a node group in wich your nodeid is record ?
regards
Philmalmaison

No, I already checked that.

I tried solutions posted before, restarted Active Environment and AJF, but nothing helps...
CONTROL-M/Server deleted the entry with wrong Agent, but when I start EM/Configuration Manager, it says there is a duplicated components, and tried to discover that agent again..

After that, when I open Agent Menu in CONTROL-M/Server, that Agent appear - twice!

I'm going slightly mad about it...

philmalmaison · Post by **philmalmaison** » 02 Jan 2008 10:29

stop/start control-m server

Dilbert · Post by **Dilbert** » 03 Jan 2008 2:29

philmalmaison wrote:stop/start control-m server

Already done.
Many times... CTM Server always found the "duplicate components".

philmalmaison · Post by **philmalmaison** » 03 Jan 2008 2:46

don't you have some jobs in old net record on that agent ?
regards
Philmalmaison

philmalmaison · Post by **philmalmaison** » 03 Jan 2008 3:04

did you try to only change controlm status in AGSTAT ?
do you have a file named with your agnt host like the following ?
NODEID <agent>
AGSTAT R # should be R for discover V for available
FIRST_SET 20080102210000
LAST_UPD 20080103145716
AGENTTYPE U
IS_DEFAULT N
HOSTNAME
DOMAIN

if you have it try to change from R to V then by controlm menu put it in unavailable, then steel by ctm_menu, delete the entry, and if you don't want to wait for synchro, stop / start gateway

regards
Philmalmaison

ranger67 · Post by **ranger67** » 04 Jan 2008 4:38

I've been using 6.3.01 for a while now and have come to the conclusion that the new "discovery" process leaves much to be desired.

Regardless, some information that I've found useful in this situation.

1. Watch for duplicate NODEID entries in separate AGSTAT file entries, the duplicate component message you are receiving tends to indicate this situation.
2. Updating the AGSTAT files manually can be problematic, but are the best way to correct things. CM will display updates to these files within 5 minutes without restart of the CM.
3. When the discovery can't fully resolve an agent's configuration it assumes that the agent is a "remote" agent. As such when you manipulate the agent type from "R" to "N" in the AGSTAT file, you MUST remember to delete the corresponding file in the AGSTAT_RJX directory. If you do not, you may experience serious problems with both CTM and with the CM.

I've had other issues but this covers the gist of the problems.

philmalmaison · Post by **philmalmaison** » 04 Jan 2008 4:41

nothing new ...
regards
Philmalmaison

Dilbert · Post by **Dilbert** » 07 Jan 2008 12:09

philmalmaison wrote:did you try to only change controlm status in AGSTAT ?
do you have a file named with your agnt host like the following ?
NODEID <agent>
AGSTAT R # should be R for discover V for available
FIRST_SET 20080102210000
LAST_UPD 20080103145716
AGENTTYPE U
IS_DEFAULT N
HOSTNAME
DOMAIN

if you have it try to change from R to V then by controlm menu put it in unavailable, then steel by ctm_menu, delete the entry, and if you don't want to wait for synchro, stop / start gateway

I already checked that, but without stopping/starting gateway.
I will try that today, and I'll post the result.

Thanks for the tips!

regards,

Dilbert · Post by **Dilbert** » 09 Jan 2008 1:04

Nothing posted here helps.

I followed all instructions posted here, placing "N" in AGSTAT file for that agent (AGSTAT_RJX folder is empty), the disable Agents, delete agent file in AGSTAT folder... but when CM starting CTM Server, it appear again.
Nothing helps.

UPDATE: When refreshing components in Configuration Manager, window appear:

Duplicate component was identified

Duplicate key: Type='CTM_Agent', Name='DS1-Red_Hat', Host='cmem6301', NodeId='cmem6301'

This duplicated component will not be displayed.

And below that:
Error EM74022 CCM

This error code not descripted in CONTROL-M/Enterprise Manager Messages Manual. The last descripted error code is 74021.

ranger67 · Post by **ranger67** » 09 Jan 2008 1:38

Dilbert, have you tried grepping the AGSTAT files for 'cmem6301'? The error sure does look like you have multiple file entries within the AGSTAT directory which contain the same NODEID information.

Dilbert · Post by **Dilbert** » 09 Jan 2008 2:05

ranger67 wrote:Dilbert, have you tried grepping the AGSTAT files for 'cmem6301'? The error sure does look like you have multiple file entries within the AGSTAT directory which contain the same NODEID information.

At this moment, only 2 files are in AGSTAT directory. Local agent and this "ghost" agent. A can delete this file for "ghost" agent, disabled and deleted this agent through the ctm_menu (on Linux machine, where Control-M Server installed) but when CM (Configuration Manager) on Windows Machine is running, this file appear again on the Linux AGSTAT folder.

ranger67 · Post by **ranger67** » 10 Jan 2008 9:12

Please post the contents of both files.

Dilbert · Post by **Dilbert** » 11 Jan 2008 11:51

ranger67 wrote:Please post the contents of both files.

Agent #1
NODEID bmccontrolm2 #(this is local agent)
AGSTAT U
FIRST_SET 20080111114824
LAST_UPD 20080111114824
AGENTTYPE N
IS_DEFAULT N

Agent #2
NODEID cmem6301 #(this agent is problematic, it shouldn't exist!)
AGSTAT R
FIRST_SET 20080109132738
LAST_UPD 20080109150838
AGENTTYPE # this field is empty
IS_DEFAULT N

vassi168 · Post by **vassi168** » 18 Jan 2008 7:49

We have the same problem,
and every time i must stop the ctm Server than delete the agent from AGSTAT and restart the ctm server.
And the agent is gone.
Our server is 6.2.01 on Unix

Dilbert · Post by **Dilbert** » 21 Jan 2008 2:37

vassi168 wrote:We have the same problem,
and every time i must stop the ctm Server than delete the agent from AGSTAT and restart the ctm server.
And the agent is gone.
Our server is 6.2.01 on Unix

Tnx, but not works for me.

Server is 6.3.01, Unix version...