I have encountered an error on AIX box, related to start up of hma. When the box is re-started, there is a script that runs to start hawk agent and the agent then should bring up hma automatically.
What is observed is that, when the box is restarted, agent comes up correctly but the hma does not. After I kill the agent and run the same script again, it starts both agent and hma correctly, i.e. agent starts hma automatically.
Script does nothing more than running the hawkagent_domain command.
The versions of Hawk and TRA being used are listed below,
Hawk – 4.5.1
TRA – 5.2.0.
Any suggestions greatly appreciated.
1. Comment by Serge
11/Mar/2010 at 11:54 am
Just to make a supposition, is an agent comes up first time and second time under the same user? If user the same (root?), it perhaps something related to system variables: rv/lib must be in LIBPATH and LD_LIBRARY_PATH, JRE_ROOT also must be, that can be defined in users profile but not defined when system comes up. You can check system variables when you start the agent second time, then try to define these variables in your script. Also you can add to the end of line, which called the script in /etc/inittab, like hawkagent_domain >/tmp/agent_start.log 2>&1 to enable output to the startup log file for subsequent analysis.
2. Comment by abhishek bhatia
11/Mar/2010 at 6:42 pm
Yes, I am starting the process as tibco user at both instances. From inittab I call the startup script.
Startup script switches to tibco user before starting the hawk agent. So, in case of server restart or starting agent manually, the user stays the same.
The variables containing lib path and jre are set correctly.
It is a good idea to log the output of the hawkagent_domain command to a startup log file because I was putting that to dev/null. But, I had a question here, doesn’t it automatically log any errors or startup problems to HAWK.log under /tra/domain//logs and /hawk/log folders??
I will try logging the output in either case. It can reveal something.
3. Comment by Serge
11/Mar/2010 at 7:05 pm
You can also enable higher tracing to Hawk, set -tsm_tracelevel -1 in your\tibco\tra\domain\\hawkagent.cfg and restart your Hawk Agent. The logs will be under \tibco\tra\domain\\logs\tsm.log by default, you can define it using -tsm_traceLogFile parameter.