Agens is in "Discover" status - how to delete it?
Agens is in "Discover" status - how to delete it?
Hello all!
In my test environment I have the 2 Agents controlled by old CONTROL-M/Server. I changed hostname of the CONTROL-M/EM machine and CONTROL-M/Server machine, changed the Agent logical name, but one of the agent remains with old name, and it is always in "Discovering.." status. I can't delete it, or stop discovering it...
Anybody know how to delete that Agent from environment?
In my test environment I have the 2 Agents controlled by old CONTROL-M/Server. I changed hostname of the CONTROL-M/EM machine and CONTROL-M/Server machine, changed the Agent logical name, but one of the agent remains with old name, and it is always in "Discovering.." status. I can't delete it, or stop discovering it...
Anybody know how to delete that Agent from environment?
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
Hello, guys!
It is impossible to delete Agent.
I don't know how, but it seems that the Agent entry is somehow duplicated in the database.
When I'm using option 4 from Agent Status Menu, it says there is a two Agent with same name in status "Disable".
After deleting Agent entry, it appear again, twice!
I'm going slightly mad about it... maybe I should write to BMC support...
It is impossible to delete Agent.
I don't know how, but it seems that the Agent entry is somehow duplicated in the database.
When I'm using option 4 from Agent Status Menu, it says there is a two Agent with same name in status "Disable".
After deleting Agent entry, it appear again, twice!
I'm going slightly mad about it... maybe I should write to BMC support...
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
I removed machine with problematic agent from environment.
After that, CONTROL-M/Server always trying to discover that Agent, and, of course, without success.
I deleted the entry from CONTROL-M/Server database as you and fyot suggested before, but CONTROL-M/EM Configuration Manager always show that Agent and trying to discover... after that, that agent appear again in Server database entry...
It will be good idea to implemet mechanism into CONTROL-M/Server to prevent automatic discovering of agent...
After that, CONTROL-M/Server always trying to discover that Agent, and, of course, without success.
I deleted the entry from CONTROL-M/Server database as you and fyot suggested before, but CONTROL-M/EM Configuration Manager always show that Agent and trying to discover... after that, that agent appear again in Server database entry...
It will be good idea to implemet mechanism into CONTROL-M/Server to prevent automatic discovering of agent...
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France