Common Commands for the Component Controller

Here are some commands you may need to troubleshoot the installation failure of the component controller isap-agent.

• Restart

  sh /opt/cloud/isap-agent/action/agent_controller_linux.sh restart

  Note: This command will stop and then restart the isap-agent process. You can use command to restart isap-agent if isap-agent fails start or the process does not exist due to a node fault.

• Start

  sh /opt/cloud/isap-agent/action/agent_controller_linux.sh start

  Note: You can use this command to start isap-agen if isap-agent breaks down but the automatic startup time for disaster recovery does not arrive.

• Stop

  sh /opt/cloud/isap-agent/action/agent_controller_linux.sh stop

  You can use this command to stop isap-agent. This command will clear the scheduled automatic startup check settings to stop the isap-agent process.

• Checking processes

  ps -ef|grep isap-agent

  You can use this command to check whether isap-agent is installed on the current host.

• Checking logs

  tail -100f /opt/cloud/isap-agent/log/run.log

  You can use this command to query the latest 100 lines of logs of the isap-agent service to locate exceptions.

• Disk partitions

  sh /opt/cloud/isap-agent/action/agent_controller_linux.sh partition

  When you install the collector on a node, you can use this command to partition disks you attach to the node.