CA Agent do not automatic restart after reboot of server

[Daniel Giron]

​HI: we are facing an issue that some of our CA Agents install in windows Azure server do not automatically come up after server has been patch or reboot. we need to log in to server and restart the agent.
any one has any ideas?

Daniel Giron

[Jonathan Calloway]

Daniel,

If this is a Windows server, then you should set the agent service to automatically start when the OS starts.  If it is a Linux server, then use "systemctl" with "enable" flag to start eh daemon when the server starts (I cannot remember right off the name of the agent daemon in Linux).

<JC>​

[Daniel Giron]

HI Jonathan:

Thanks for your reply. This is the problem the agent is already set up as automatic in the services but still when the server gets reboot the agent does not automatic comes back up causing the operations support to have to call the admin support to start the agent.

 

Daniel Giron

Infrastructure Technical Analyst

Manulife

 

E    [e-mail]

T    (514) 206-7232

 

[CARLOS JUPIA]

Hi Daniel,

 

Startup (Windows): Generally started as a windows service –Default is SYSTEM account

-Agent can be started on command line using

cybAgent –debug

 

And see the logs mainly transmitter.log  file:

 

 

 

 

Carlos Jessé D. Jupiá

Services Consultant - CA Services

HCL Technologies Ltd.

Rua Olimpíadas, 205 – 1st Floor – Vila Olímpia – São Paulo/SP - Brazil

Mob: [phone]

www.hcltech.com

www.hcl.in

 

[CARLOS JUPIA]

Daniel

Another tip is :

On Windows:

You can Use AgentRansack tool  to find 'exception|error' * string in log files..

 

And in Linux use egrep

 

–[root@xpto log]# egrep -i 'exception|error' *

 

–For system or general type problems, check runner_os_component.log and defaultlog_agent.log–For communication related problems check the transmitter and receiver logs.

–Existence of a java exception stack in the logs means there is a problem:

cybermation.library.communications.CybConversationConnectException: Connection refusedcybermation.library.communications.CybConversation.<init>(CybConversation.java:130)cybermation.commplugins.tcpip.handler.

CybTargetHandlerChannel.constructConversation(CybTargetHandlerChannel.java:660)cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.sayHelloOrGoodbye(CybTargetHandlerChannel.java:564)

cybermation.commplugins.tcpip.CybTransmitter.sayHelloOrGoodbye(CybTransmitter.java:84)at cybermation.commplugins.tcpip.CybTransmitter.run(CybTransmitter.java:133)

 

Carlos Jessé D. Jupiá

Services Consultant - CA Services

HCL Technologies Ltd.

Rua Olimpíadas, 205 – 1st Floor – Vila Olímpia – São Paulo/SP - Brazil

Mob: [phone]

www.hcltech.com

www.hcl.in

 

[Rick Romanowski]

On Windows you can also use the native command FINDSTR.

Change to the <agent dir>/log

To search for all log files that contain "error" OR "exception":
FINDSTR  /i "error exception" *.*​

------------------------------
Senior Systems Analyst
UPS
------------------------------

[Michael Woods]

Hi,

I would also check the windows event logs for any errors as well as in the agent install directory, there is the nohup.stdxxx files.
Check those for any errors after the reboot.  It will get overwritten when restarted.

Mike