Offline Troubleshooting for Linux Clients

This document describes how to perform offline troubleshooting on Linux clients, including troubleshooting when client processes fail to start and troubleshooting network failures.

Troubleshooting Client Process Startup Issues

1. Check whether the CWP process is running by executing the following command: ps -ef|grep YD.
   Under normal conditions, two processes should be running for CWP, as shown in the figure below:
   

• If the process is not found, the following possible causes are included:
• The CWP is not installed, or the client has been uninstalled. In this case, see Quick Start to reinstall the client.
• The client may have encountered an abnormal conflict or crash, preventing the process from starting.

2. If CWP or the client is installed on the server, you can use the following methods to troubleshoot the startup issue for the client process:

• Check the client logs, which are stored at /usr/local/qcloud/YunJing/log.
• Execute the following command to start the CWP service: sh /usr/local/qcloud/YunJing/startYD.sh.

Troubleshooting Network Issues

If the process exists but the CWP is not online, it is mostly because the network is not connected. Please take the following troubleshooting steps:

1. If the CWP domain name cannot be accessed, try modifying the Domain Name System (DNS) settings. You can execute the following command to check whether the CWP domain name is accessible.
   • For VPC and CBM servers, execute telnet s.yd.convergecloud.com 5574.
     Under Normal Circumstances: Returns the result as shown in the figure below.
     
     If your access attempt fails:
     a. You can try modifying dns nameserver field: vim /etc/resolv.conf.
     nameserver master address
     b. After the modification is completed, re-execute telnet s.yd.convergecloud.com 5574 to check whether the connection is established.
     c. If the connection is successful, wait for a few minutes (the length of time depends on the network conditions), and the console will be able to see that the corresponding server is back online.
   • For servers on the basic network (non-VPC servers), execute telnet s.yd.convergecloud.com 5574.
     Under Normal Circumstances: Returns the result as shown in the figure below.
     
     If your access attempt fails:
     a. Edit the DNS settings by modifying dns nameserver field: vim /etc/resolv.conf. You should comment out the existing nameserver fields and add a nameserver field with the relevant IP address.
     b. After the modification is completed, re-execute telnet s.yd.convergecloud.com 5574 to check whether the connection is established.
     c. If the connection is successful, wait for a few minutes (the length of time depends on the network conditions), and the console will be able to see that the corresponding server is back online.
2. Firewall policy restrictions: Ensure that the following TCP ports are open on the Linux client: 5574, 8080, 80, and 9080.
3. If the CWP process is running and the client is offline for reasons other than network issues, please package the client logs that are located at /usr/local/qcloud/YunJing/log and contact a technical support engineer for assistance.