Possible Causes

• The network is faulty.

  The agent or the cloud protection center is abnormal. For example, the NIC is faulty, the IP address changes, or the bandwidth is low.

• The agent process is abnormal.
• The agent status has not been updated. After the agent is installed, it takes about 2 minutes for the console to update its status.

Solution

1. Fix network problems (if any).

   Ensure that the outbound configurations of the security group of your server allow access to port 10180 in the 100.125.0.0/16 network segment.

   After the network recovers,

   • If the agent status is Online, no further action is required.
   • If the agent status is Not installed or Offline, go to 2.

2. Log in to the server and restart the agent. The agent status Not installed or Offline indicates that the agent process is probably abnormal.
   • Linux

     Run the following command in the CLI as user root to restart the agent:

     service hostguard restart

     If the following information is displayed, the restart is successful:

     root@HSS-Ubuntu32:~#service hostguard restart
     Stopping Hostguard...
     Hostguard stopped
     Hostguard restarting...
     Hostguard is running

   After the process is restarted, wait for about 2 minutes.

   • If the agent status is Online, no further action is required.
   • If the agent status is still Not installed or Offline, uninstall the agent and install it again.