Alertcollector not started automatically

Document ID : KB000015831
Last Modified Date : 14/02/2018
Show Technical Document Details

Alertcollector is installed on a machine.

After the reboot of the machine, alertcollector is not started automatically


Command caf status cfprocessmanager returns status stopped for "Alert Collector"



The solution is to start Alert Collector manually with this command :

alertcollector start



But why it is not started manually




At startup, hmagent.exe starts automatically alertcollector.exe 

In TRC_CF_HMAGENT*.log in trace DETAIL following lines should appear :


150917-07:31:06.1295068L|004824|0000128c|hmagent   |hmagent         |HMAgent.cpp         |000781|DETAIL | HMAgent::StartMonitoring(). Starting Alert Collector

150917-07:31:06.1307415L|004824|0000128c|hmagent   |hmagent         |HMAgent.cpp         |000794|DETAIL | HMAgent::StartMonitoring(). Alert Collector started successfully



Remark :

Trace DETAIL for HMAGENT could be set with this command :

cftrace -c set -l DETAIL -f CF -pp hmagent -s 30000



If service "CA DSM r14 Health Monitoring Agent Service" has been set for "Manual" or Disabled startup type, process hmagent.exe and alertcollector are not automatically started.




The solution is to set the startup type of "CA DSM r14 Health Monitoring Agent Service" service to Automatic.

But if it is not possible to do this, execute this command to indicate that process alertcollector should be started automatically when caf is started :


ccnfcmda -cmd setParameterValue -ps itrm/common/caf/processes/alertcollector -pn startwithcaf -v 1



After the reboot of machine, process Alertcollector.exe is automatically started and running.