hma did not respond to first heartbeat request. Presumed dead.
Article ID: KB0072881
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | 5.x , 6.x |
Description
User may see below warning messages in hawk.log file.
<------
2020 Oct 25 16:00:10:704 GMT -10:00 HawkAgent.hlp9210 Warn [Application] HWKXXX-000004 Announced AMI application COM.TIBCO.hawk.hma.Process did not respond to first heartbeat request. Presumed dead.
2020 Oct 25 16:00:15:704 GMT -10:00 HawkAgent.hlp9210 Warn [Application] HWKXXX-000004 Announced AMI application COM.TIBCO.hawk.hma.FileStat did not respond to first heartbeat request. Presumed dead.
2020 Oct 25 16:00:30:706 GMT -10:00 HawkAgent.hlp9210 Warn [Application] HWKXXX-000004 Announced AMI application COM.TIBCO.hawk.hma.FileSystem did not respond to first heartbeat request. Presumed dead.
2020 Oct 25 16:00:35:709 GMT -10:00 HawkAgent.hlp9210 Warn [Application] HWKXXX-000004 Announced AMI application COM.TIBCO.hawk.hma.System did not respond to first heartbeat request. Presumed dead.
020 Oct 25 16:00:45:726 GMT -10:00 HawkAgent.hlp9210 Warn [Application] HWKXXX-000004 Announced AMI application COM.TIBCO.hawk.hma.Network did not respond to first heartbeat request. Presumed dead.
------->
This warn message indicates that the hma did not response to the first heartbeat request right after hawk get the announce message from hma and request that. This could be the hma or machine is heavy loaded and did not response in time.
This could be due to following reasons :-
1.) hma is heavily loaded
2.) machine is heavy loaded
3.) Network glitch
4.) RV communication
5.) Hawk is busy in processing other request
Environment
Resolution
1. Please run ps -ef|grep hma to see if you can see the hma running.
2. Check machine to see if it has High CPU or Memory consumption.
3. Manually start HMA first, when it starts completely, then start hawkagent.
Issue/Introduction
Feedback
