Alibaba Cloud DevOps:Common issues and solutions for host deployment

Troubleshoot Flow Runner

Check the Runner status first when host deployment fails, or self-hosted instance fails to apply for environment.

• Use the tool to get prompts for troubleshooting.

  1. Download the troubleshooting tool (supports Linux only).

     wget "https://rdc-public-software.oss-cn-hangzhou.aliyuncs.com/runner/runnerStatusCheck" -O runnerStatusCheck

  2. Configure permissions.

     chmod u+x runnerStatusCheck

  3. Run the tool.

     ./runnerStatusCheck

  4. Follow the prompts provided by the tool for further processing, as illustrated below.

• Troubleshooting without tool.

  1. Check the Linux system version.

     Use the command lsb_release -a to get the version. Runner currently supports the following Linux distribution versions:

     1. CentOS 6 and later

     2. Ubuntu 16.04 and later

     3. Alibaba Cloud Linux 2 and 3

  2. Check the Runner service status and logs.

  3. Use the command ls -al /etc/systemd/system | grep runner to identify the Runner service name, which is typically formatted as runner-{version}-{tenant}.service, as shown below.

  4. Check the Runner service status with the command systemctl status runner-{version}-{tenant}.service. If the status is active (running), the service is functioning properly, as shown below.

  5. You can view the Runner execution logs with the command journalctl -u runner-{version}-{tenant}.service -a --no-pager --since '5 minutes ago' -f.

Common issues with offline host groups

• During building or deploying, logs are not reported or the host goes offline

  1. Use the command df -hl to get the status of the disk. Clean it up if it is out of space.

  2. Restart the Runner service if it is not active (running).

     1. Get the service name, usually named after runner-{version}-{tenant}.service

        systemctl | grep "runner-v" | awk '{print $1}'

     2. Restart the Runner service with the name obtained from the last step.

        systemctl restart $SERVICE_NAME

  3. Ensure the network connectivity.

     1. Query the Runner service status with systemctl status runner-{version}-{tenant}.service and note the service process parameter --configPath=***, as illustrated below.

     2. Check the URL in the configPath using cat {***}/config.yml | grep url.

        

     3. Check if the URL is accessible using the following command.

        # replace the url in the command below
        curl '{url}/api/v2/runner/storage/latest?os=linux&arch=amd64'