Unable to start Autosys Agent

[Sandeep Veetil]

We have Autosys 11.3.6 running on our Linux server and the systems team had to reboot the server to apply some PeopleSoft patch. After the server was rebooted, I am unable to start the agent.

 

When I try to start the agent, it gives me the below error:

 

bash-3.2$ unisrvcntr start ALL

WAAE Agent (WA_AGENT) Agent is already running with pid  0

                                                           [  OK  ]

Executed waae_agent-WA_AGENT start...............................OK

 

I checked but we are unable to find any process with PID 0. The agent on the other servers where the reboot was initiated is working fine. It is only one of this server having a problem.

Has anyone faced this kinda issue before?

[lisadunaway]

Yes we have seen this issue a few times.

 

You can remove the status file that is found in the SystemAgent directory and then it will usually start up fine (at least it does for us).

 

Thanks,

 

Lisa Dunaway

[Sandeep Veetil]

I did that before, but it didn’t help.

 

Regards,

Sandeep K V

Autosys Administrator

[Legacy User]

Je suis absent(e) du bureau jusqu'au 29/05/2015

 

 

 

 

Remarque : ceci est une réponse automatique à votre message  "Re: [CA

Workload Automation] - Unable to start Autosys Agent" envoyé le 28/05/2015

23:02:29.

 

C'est la seule notification que vous recevrez pendant l'absence de cette

personne.

 

 

This message and any attachments (the "message") is

intended solely for the intended addressees and is confidential.

If you receive this message in error,or are not the intended recipient(s),

please delete it and any copies from your systems and immediately notify

the sender. Any unauthorized view, use that does not comply with its purpose,

dissemination or disclosure, either whole or partial, is prohibited. Since the internet

cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS

(and its subsidiaries) shall not be liable for the message if modified, changed or falsified.

Do not print this message unless it is necessary,consider the environment.

[Legacy User]

Je suis absent(e) du bureau jusqu'au 29/05/2015

 

 

 

 

Remarque : ceci est une réponse automatique à votre message  "[CA Workload

Automation] - Unable to start Autosys Agent" envoyé le 28/05/2015 22:45:32.

 

 

C'est la seule notification que vous recevrez pendant l'absence de cette

personne.

 

 

This message and any attachments (the "message") is

intended solely for the intended addressees and is confidential.

If you receive this message in error,or are not the intended recipient(s),

please delete it and any copies from your systems and immediately notify

the sender. Any unauthorized view, use that does not comply with its purpose,

dissemination or disclosure, either whole or partial, is prohibited. Since the internet

cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS

(and its subsidiaries) shall not be liable for the message if modified, changed or falsified.

Do not print this message unless it is necessary,consider the environment.

[Steve Carrobis]

check the plugin logs .. there must be something else that is breaking.

dont use the univctr wrapper ot wrapper to wrapper.

got to /etc/init.d

look for the waa_agent startup and try it form there.. you may want to check the code to see where its finding it.

do a ps.. you may have an errant process..

[Nitin Pande]

Hi,

Please check the ps.log in log directory.  If the agent is not able to connect to PeopleSoft instance, then it will not start.

This is to make sure you have provided correct user/pass.  It allows checks to make sure that all the PS settings are correct and working.

 

Thank you,

Nitin

[Steve Carrobis]

In autosys. I rather the owner: field handle ID and password. the agents themselves should noty be PS server specific.

it should behave like the DB and FTP plugin.

[Nitin Pande]

Hi Steve,

The agent works with several other managers as well.  Other managers have to option to use defaults in the agentparm.txt.  The job definition in other schedulers have options to omit users and passwords and then agent can fill in the blanks.  This is why it is necessary to have working user and password in the agentparm.txt.

Again, it also allows the agent to make sure it can reach and connect the intended PS instance.

 

Thank you,

Nitin

[Steve Carrobis]

Understood but this was an autosys questioon. if the agent allows for non default. Then its easy to know that when the job runs and fails.

and not check the logs for the agent. because in autosys many times it is very difficult for users to get access to the agent machine and the logs.

hence why the job itself saying it has an issue logging, in.

the working id and password shouldnt need to be in agent file for autosys. if this is how other managers works thats fine, but for autosys. it is important that the detail i bring up isnt lost.

 

Hope this explains my point.

 

Thank you

[Nitin Pande]

Hi Steve,

Thanks for your reply.  The same agent install can work with different schedulers like CA-7, AutoSys, DE and ESP.  As I mentioned, the agent has to accommodate different managers including AutoSys.  We have several users who use the same agent to run the job submitted by different managers.  This is why this user and password is needed in agentparm.txt for now. 

Also, please note that the user credentials are always encrypted, if that is/was a concern.

 

Sincerely,

Nitin

[Steve Carrobis]

The concern is that the agent is set to only one id and password. and that if that password changes. it needs to go out to all the agents individually instead of centrally within the autosys db.

This makes password changes dangerous in an environment as it could lock user out .. until all the agents are updated .. where applicable.

Autosys Engineers understand this and expect the behavior i discussed... and why in a different thread i appealed that the agents need to behave as Autosys needs them to behave.

we can always discuss in a sprint call etc.

But this is a very important point.// Autosys is centralized to the DB NOT decentralized.. like DE and maestro and TWS and sysadmiral..

 

Thank you

[Nitin Pande]

Hi Steve,

Thanks again.  Yes I understand the concern here.  Please feel free to discuss this during our sprint review.

I would also like to ask user "sveetil" if the initial question has been answered.  If so then please mark it as solved.

 

Sincerely,

Nitin Pande

CA Technologies

[Sandeep Veetil]

Thanks for the response guys. The issue has been fixed.

 

Solution was: Delete the .lock file from the SystemAgent directory and also the waae_agent file from the /var/lock/subsys directory. Tried to start the autosys agents and it worked fine.

 

Thanks again everyone.

[Steve Carrobis]

usually you will see that error when starting up. etc. or in the logs.

cannot delete .lck file etc..

one of the reasons why i dont useth the univ wrapper sometimes you dont see the errors.

Glad it was resolved.