How to locate VDS issues
The problem of locating VDS can be divided into the following steps. Take the image download problem as an example. The log is as follows:
1. First, we must clarify what type of problem is, how it is generated, and how likely it is to appear.
(Understanding that the problem is a picture download problem, some pictures may not be displayed properly, and the chance of occurrence is occasional.)
2、No corresponding abnormal prints were found, only successful prints were found, as shown below, and all successful prints were all smaller than 4M in size, so from the VDS print, there was no download failure on the VDS side. After VDS downloads the original image, it will serialize the operation and encode the image in BASE64. Because BASE64 is a general-purpose function, as long as the basic functions are correct, there will be no other problems, so it can be ruled out that the BASE64 encoding problem is caused.
3、If the second step still fails to solve the problem, the network captures the location problem (it is obvious that step 2 still fails to rule out whether the VDS failed to respond to the request sent by the vvcsdk. Therefore, the capture can be very good. Explain the problem. Reproduce the problem, and capture a complete package in the process of recurring, request the download code to be 1025, the number of occurrences is 16 times, so as long as the number of responses on our side is 16 times, it can be excluded as For the VDS problem, it can be seen from the packet capture log that the number of requests and responses is consistent, so the exclusion is a VDS issue.
