DISCOVERING controlm agents
DISCOVERING controlm agents
We have a control M server which is connected to almost 6 agents in which 3 of them are linux and rest 3 are windows server ... linux agents are running fine and jobs are exeuting fine, but 2 of windows agents are always in discovering mode, after deleting the agent entries again i found the same agent was in discoverinig mode due to this we are facing slow response, any suggestions on this as we cannot disable or remove the jobs which are executing on these agent machines but we dont want these agents in discovering status.
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
Hi,
find why your agent is in discover status
this is probably just some port number collision.
look that Server To Agent port and Agent to Server port are correctly set on both controlm server and controlm agent part
Note : i don't think it could make your datacenter to be slower that before that discover.
Regards,
Philmalmaison
find why your agent is in discover status
this is probably just some port number collision.
look that Server To Agent port and Agent to Server port are correctly set on both controlm server and controlm agent part
Note : i don't think it could make your datacenter to be slower that before that discover.
Regards,
Philmalmaison
AGENT IN DISCOVERING MODE
It is probably the case that the agent is not configured correctly. Here are some likely scenarios:
1. The agent is behind a firewall.
2. The Control-M/Server is not on the list of authorised servers in the agent configuration.
3. The agent is not running.
4. The server-to-agent and agent-to-server ports do not match (between Control-M/Server and Control-M/Agent).
There are clearly processes attempting to run on these agent, and Control-M is trying to automatically discover them (this is a feature of the product that you cannot turn off). I would think that the jobs would not be able to run on these agents if the agent cannot be discovered? Are they in blue status (waiting resource) or are they running?
Cheers.
1. The agent is behind a firewall.
2. The Control-M/Server is not on the list of authorised servers in the agent configuration.
3. The agent is not running.
4. The server-to-agent and agent-to-server ports do not match (between Control-M/Server and Control-M/Agent).
There are clearly processes attempting to run on these agent, and Control-M is trying to automatically discover them (this is a feature of the product that you cannot turn off). I would think that the jobs would not be able to run on these agents if the agent cannot be discovered? Are they in blue status (waiting resource) or are they running?
Cheers.
AGENT IN DISCOVERING MODE
Hi,
If the jobs are blue, then they are not running. Why do you not want to hold or stop them from running? They can't run anyway!
If the jobs are blue, then they are not running. Why do you not want to hold or stop them from running? They can't run anyway!