Elastic Compute Service:Check Cloud Assistant Status and Troubleshoot Abnormal Statuses

Console

1. Go to ECS console - Cloud Assistant.

2. In the upper-left corner of the page, select a region and resource group.

3. On the ECS Instance tab, view the Cloud Assistant status.

   • Normal: Cloud Assistant is running as expected.

     In the instance list on the Cloud Assistant page, ensure the Cloud Assistant Status for the target instance is Normal.

   • Not installed: The Cloud Assistant Agent is not installed on the instance. You can install the Cloud Assistant Agent by using the following methods.

     • Click Install to automatically install the Cloud Assistant Agent.

       When you install the Cloud Assistant Agent with one click, you must restart the instance for it to take effect.

     • Manually install the Cloud Assistant Agent. For more information, see Install Cloud Assistant Agent.

       In the instance list of the Cloud Assistant console, if the Cloud Assistant Status column for the target instance shows Not Installed, click the corresponding Install button to complete the installation.

   • Abnormal: This status indicates a problem with several possible causes. For troubleshooting steps, see Troubleshoot abnormal statuses.

     On the ECS Instances tab of the Cloud Assistant console, the Cloud Assistant Status column shows the running status of Cloud Assistant on each instance. A yellow icon indicates an abnormal status.

API

Call the DescribeCloudAssistantStatus operation. If "CloudAssistantStatus": "true" is returned, Cloud Assistant is running correctly. If "false" is returned, the status is abnormal. See Troubleshoot abnormal statuses.

Linux instance

1. Connect to the Linux instance.

   For more information, see Connect to a Linux instance by using Workbench.

2. Run the following commands to check whether the Cloud Assistant installation directory exists.

   • CoreOS

     cd /opt/local/share/
     ls

   • Other operating systems (such as Alibaba Cloud Linux, Ubuntu, Debian, Red Hat, SUSE Linux Enterprise Server, and OpenSUSE)

     cd /usr/local/share/
     ls

   • If the aliyun-assist directory exists, go to Step 3.

   • If the aliyun-assist directory does not exist, the Cloud Assistant Agent is not installed. You must reinstall the Cloud Assistant Agent.

3. Check the status of the Cloud Assistant service.

   First, determine the init system of the ECS instance. The command to check the service status depends on the init system.

   ls -l /sbin/init

   • If the output points to systemd (for example, /lib/systemd/systemd), the init system is systemd.

   • If the output points to upstart (for example, /sbin/upstart), the init system is Upstart.

   • If the output points to init (for example, /sbin/init), the init system is sysvinit.

   Systemd

   Run the following command to check the Cloud Assistant status:

   systemctl status aliyun.service

   • If the status is inactive (dead), the Cloud Assistant service is stopped. Run systemctl start aliyun.service to start the Cloud Assistant service.

     If an error occurs or the service fails to start, uninstall and then reinstall the Cloud Assistant Agent. For more information, see Stop and uninstall the Cloud Assistant Agent and Install Cloud Assistant Agent.

     [   @iZuf68j5ei93s       share]# systemctl status aliyun.service
     ● aliyun.service - Aliyun Assist
        Loaded: loaded (/etc/systemd/system/aliyun.service; enabled; vendor preset: enabled)
        Active: inactive (dead) since Mon 2023-09-11 17:18:33 CST; 47s ago
       Process: 1951 ExecStart=/usr/local/share/aliyun-assist/2.2.3.515/aliyun-service (code=exited, status=0/SUCCESS)
      Main PID: 1951 (code=exited, status=0/SUCCESS)
         Tasks: 2 (limit: 22694)
        Memory: 1.3G
        CGroup: /system.slice/aliyun.service
                ├─5608 gpg-agent --homedir /var/cache/dnf/remi-modular-6408ecca79e22107/pubring --use-standard-socket --daemon
                └─5648 gpg-agent --homedir /var/cache/dnf/remi-safe-ff04689114f71b24/pubring --use-standard-socket --daemon

   • If the status is active (running), the Cloud Assistant service is running as expected. Go to Step 4.

     [root@iZuf68j5ei93s8       ~ share]# systemctl status aliyun.service
     ● aliyun.service - Aliyun Assist
        Loaded: loaded (/etc/systemd/system/aliyun.service; enabled; vendor preset: enabled)
        Active: active (running) since Mon 2023-09-11 17:25:07 CST; 2s ago
      Main PID: 72998 (aliyun-service)
         Tasks: 10 (limit: 22694)
        Memory: 1.3G
        CGroup: /system.slice/aliyun.service
                ├─ 5608 gpg-agent --homedir /var/cache/dnf/remi-modular-6408ecca79e22107/pubring --use-standard-socket --daemon
                ├─ 5648 gpg-agent --homedir /var/cache/dnf/remi-safe-ff04689114f71b24/pubring --use-standard-socket --daemon
                └─72998 /usr/local/share/aliyun-assist/2.2.3.515/aliyun-service

   Upstart

   Run the following command to check the Cloud Assistant status:

   /sbin/initctl status aliyun-service

   • If the status is stop/waiting, the Cloud Assistant service is stopped. Run /sbin/initctl start aliyun-service to start the Cloud Assistant service.

     If an error occurs or the service fails to start, uninstall and then reinstall the Cloud Assistant Agent. For more information, see Stop and uninstall the Cloud Assistant Agent and Install Cloud Assistant Agent.

     /sbin/initctl status aliyun-service
     aliyun-service stop/waiting

   • If the status is start/running, the Cloud Assistant service is running as expected. Go to Step 4.

     /sbin/initctl status aliyun-service
     aliyun-service start/running, process 1129

   Sysvinit

   Run the following command to check the Cloud Assistant status:

   /etc/init.d/aliyun-service status

   • If the status is Stopped, the Cloud Assistant service is stopped. Run /etc/init.d/aliyun-service start to start the Cloud Assistant service.

     If an error occurs or the service fails to start, uninstall and then reinstall the Cloud Assistant Agent. For more information, see Stop and uninstall the Cloud Assistant Agent and Install Cloud Assistant Agent.

     [root@i7bp1hfzscxxx ~]# /etc/init.d/aliyun-service status
     Stopped

   • If the status is Running, the Cloud Assistant service is running as expected. Go to Step 4.

     [root@i7bplhtzscxxxxxx ~]# /etc/init.d/aliyun-service status
     Running

4. Check the status of the Cloud Assistant Agent on the console.

   • If the status of the Cloud Assistant Agent is Normal, the issue is resolved.

   • If the Cloud Assistant Agent status is still Abnormal, check the Cloud Assistant logs to investigate further.

     • CoreOS:

       cd /opt/local/share/aliyun-assist/<version>/log  
       tail -100f aliyun_assist_main.log

     • Other operating systems (such as Alibaba Cloud Linux, Ubuntu, Debian, Red Hat, SUSE Linux Enterprise Server, and OpenSUSE):

       cd /usr/local/share/aliyun-assist/<version>/log  
       tail -100f aliyun_assist_main.log

Windows instance

1. Connect to the Windows instance.

   For more information, see Connect to a Windows instance by using Workbench.

2. Check whether the Cloud Assistant installation directory C:\ProgramData\aliyun\assist exists.

   • If the assist directory exists, go to Step 3.

   • If the assist directory does not exist, the Cloud Assistant Agent is not installed. You must reinstall the Cloud Assistant Agent. For more information, see Install Cloud Assistant Agent.

3. Check the status of the Cloud Assistant service.

   1. Click the Start menu and go to Windows Administrative Tools > Computer Management.

   2. In the navigation pane, choose Computer Management (Local) > Services and Applications > Services.

   3. Find Aliyun Assist Service and check its Status.

      • If the Status column shows Normal, the Aliyun Assist Service is running as expected.

      • If the Status column is empty, the Aliyun Assist Service is stopped. Click Start to start the Aliyun Assist Service.

        If an error occurs or the service fails to start, uninstall and then reinstall the Cloud Assistant Agent. For more information, see Stop and uninstall the Cloud Assistant Agent and Install Cloud Assistant Agent.

4. Check the status of the Cloud Assistant Agent on the console.

   • If the status of the Cloud Assistant Agent is Normal, the issue is resolved.

   • If the status is still Abnormal, review the Cloud Assistant logs to investigate further.

     The default log path for Cloud Assistant is C:\ProgramData\aliyun\assist\<version>\log, where <version> is the version of the Cloud Assistant Agent.

     In this directory, focus on aliyun_assist_main.log and its date-rotated backup files (for example, aliyun_assist_main.log.20230912) to diagnose the problem.