Help Center/ Application Operations Management/ FAQs/ Collection Management/ What Should I Do If ICAgent Fails to Install on a New Host Cloned from the Host Where ICAgent Is Installed?
Updated on 2026-09-18 GMT+08:00
View PDF
Share

What Should I Do If ICAgent Fails to Install on a New Host Cloned from the Host Where ICAgent Is Installed?

Symptom

A new host (host B) is generated by cloning an existing one (host A), and host A is checked whether it has ICAgent installed. If ICAgent has been installed on this host, ICAgent fails to be installed on host B.

Possible Causes

ICAgent has been installed on host A. AgentID of host B is the same as that of host A. As a result, the installation fails.

Solution

  1. On host B, run the following commands to delete AgentID: 

    rm -f /tmp/caf-agent-id
rm -f /tmp/apm/caf/caf-agent-id
rm -f /var/share/oss/manager/ICProbeAgent/internal/AGENT_CONFIG/caf-agent-id

  2. Run the following commands to restart ICAgent: xxx indicates the ICAgent process ID. 

    ps -ef | grep icagent |grep -v icwatchdog | grep -v grep
kill -9 xxx

Parent topic: Collection Management