Troubleshoot the registry center

Deployment

1. Delete the data for MetaServer from the /home/admin/raftData/ path, and then republish MetaServer, DataServer, and SessionServer sequentially.

2. After publishing SessionServer, the IP address of the pod node changes. Check that the ACVIP configuration is correct.

Usage

1. Check if the server is connected to the registry center.

   On the affected machine, run the netstat -anlp | grep 9600 command.

2. A connection to the registry center could not be established. Verify the ACVIP configuration.

   Run the cd /home/admin/conf/acvip-java-client-cache/domains/ command. Then, find the *-DSR_CLOUD.json and *-DSR_HTTP_CLOUD.json files and check their configuration to verify that information was pulled from the registry center.

3. If the server failed to pull information from the registry center, check the ACVIP configuration.

   Run the cd /home/admin/logs/acvip-java-client command and check the api-stat.log file for errors.

4. After connecting to the registry center, check the pulled information.

   On the subscriber side, run the following command:

   grep "DsrSubscribeCallback"  /home/admin/logs/rpc/rpc-registry.log

   A message similar to the one shown in the following figure indicates a successful subscription.

   On the confreg side, run the grep <interface_name> /home/admin/logs/rpc/rpc-registry.log -A 5 command.

5. If a service fails after a restart and the registry center reports no errors, check whether SessionServer has disabled push.

   Run the following command:

   curl http://localhost:9603/digest/pushSwitch