FAQ about client disconnections

Problem description

You may encounter the following problems:

• No machine IP address is displayed on the client.

• The error message "No available target zone was found" is reported when a task is triggered.

• The client is displayed as offline.

Troubleshooting procedure

1. Check whether the application configuration is valid in the task configurations.

   • Check whether the specified instance ID is consistent with that displayed on web pages. If not, change the instance ID.

     Use Google Chrome to run the developer tool. When you perform an operation on a web page, the request contains an instance ID, which is the one corresponding to the account that you use.

   • Check whether the AccessKey pair is valid.

   • Check whether the value of com.antcloud.antvip.endpoint is valid and corresponds to the environment that you want to use.

   • Check whether the value of spring.application.name is consistent with the application name specified in the task configurations.

2. Check whether the application process is running as expected.

   • If your application is a SOFABoot or Sprint Boot application, run the curl http://127.0.0.1:8080/actuator/readiness command to check whether the configured application port is valid. If not, the business process is abnormal.

   • Check whether the ~/conf/acvip-java-client-cache/domains/xxx-ANTSCHEDULER_CLOUD.json file can be obtained.

     • If the configuration file cannot be obtained, check whether an error is recorded in ~/logs/acvip-java-client/inner-error.log.

     • If the configuration file is obtained, check whether it contains information including an IP address.

3. Log on to one of the machines specified in the task configurations to check the connection.

   Run the following command to check whether a connection to Task Scheduler (TS) is established:

   netstat -ant | grep 9001

   • If no connection exists, repeat Steps 1 and 2.

   • If a connection exists, contact R&D engineers for help.