AutoSys Workload Automation

we are unable to stop Waae_agent so we have killed the process by taking pid of agent and uninstalled the whole autosys server and re-installed after doing it we have got two default agents with the name of server_name.main and another one was server_name.out, now how could we stop the server_name.main.

Hi,

Each agent comes with an init script in the agent install directory.  You can use that to start/stop/restart the agent.

You can use that init script to setup start service in Linux/UNIX OS.  If this is Windows OS, the services console will have a specific entry for each agent and that works well.

Thank you,

Nitin Pande

CA Technologies

Thank you Pande for giving fast response.

Current issue was i'm not able to stop an agent using command unisrvcntr stop all and also i have tried using script called ./cybAgent  -s  to stop it but no luck, so i have killed the process by taking the PID of WAAE_AGENT. After it I have totally uninstalled Autosys server and Re-installed. 

my expected output :

bash-4.3# autorep -M ALL

Machine Name Max Load Current Load Factor O/S Status

tigera1a.out.a1 --- --- 1.00 Sys Agent Online

Actual coming output:

bash-4.3# autorep -M ALL

Machine Name Max Load Current Load Factor O/S Status

tigera1a.main.a1 ---  --- 1.00    Sys Agent   Online

tigera1a.out.a1 --- --- 1.00  Sys Agent Online

could you suggest me how to uniform that two machines into single machine?

Hi,

When you installed the agent, did you give it a new name?

On AE side, was this agent added again?

I can't see how AE will have two entries unless it got added somewhere.

Thanks,

Nitin Pande

CA Technologies

Hi Pande,

I have installed Waae_agent with the same agent name, not with new name.

and how could we add new agent at AE side? would you explain me? 

regards,

G.Ramakiran Reddy

Hi Ramakiran,

It is possible for multiple machine definitions to reference a single System Agent within AutoSys. An example of such is below.

/* ----------------- machine1 ----------------- */

insert_machine: machine1
...
port: 7520
node_name: agent_host_name
agent_name: WA_AGENT
...

/* ----------------- machine2 ----------------- */

insert_machine: machine2
...
port: 7520
node_name: agent_host_name
agent_name: WA_AGENT
...

The node_name is the name/IP of the server upon which the agent is installed. If there are multiple agents on the same machine then they will be using different ports.

When you first installed the AutoSys server I suspect that that the first agent was defined. When you uninstalled AutoSys and started afresh, did you also drop the AutoSys database tables? If not, then its possible that the original machine definition remained in place and that during/after the second installation the additional machine was added.

I suggest that you check the definition of both machines to verify that they are referencing the same system agent. Assuming that this is the case, you can use the JIL interface to delete whichever machine you no longer need (delete_machine: ******).

hello hiejo01,

Thank you so much for your suggestion i appreciate it works for me.

I have dropped the database tables of autosys, and now the extra agent was not appearing, but when i do autorep -M ALL the machine name is coming up with tigera1a.main.a1a but i need the name of the tigera1a.out.a1a as per our requirements.

could you help out me in this?

regards,

G.Ramakiran Reddy.