Push interruption diagnosis helps you quickly check the record of LVB push interruptions and their reasons.
After the LVB push is interrupted, select Event Center > Stream Interruption Records on the left sidebar to enter the push interruption diagnosis page.
Here:
AppName
in the push address.StreamName
in the push address.The error codes and corresponding reasons are listed in the table below:
Error Code | Reason | |
---|---|---|
0 | Unknown error. | |
1 | The push client actively stopped the push. | |
2 | The push client actively stopped the push. | |
3 | The push client actively stopped the push. | |
4 | The push client actively stopped the push. | |
5 | Internal error in the LVB system. | |
6 | Exception with the RTMP protocol content. | |
7 | The size of a single RTMP frame exceeds the maximum value allowed by the configuration. | |
8 | The system actively disconnected the push as there was no data for a prolonged time. | |
9 | Internal error in the LVB system. | |
10 | The proxy layer received an interruption command. | |
11 | Internal error in the LVB system. | |
12 | Exception with the push linkage network. | |
13 | Exception with the push linkage network. | |
14 | Exception with the push linkage network. | |
15 | Exception with the push linkage network. | |
16 | Internal error in the LVB system. | |
17 | Exception with the push linkage network. | |
18 | 100 | Internal error in the LVB system. |
101 | Internal error in the LVB system. | |
102 | Internal error in the LVB system. | |
103 | Internal error in the LVB system. | |
104 | Internal error in the LVB system. | |
200 | Failed to get the customer information corresponding to the push link. | |
201 | Your LVB service has been disabled. | |
202 | You LVB service has been temporarily disabled due to arrears of your account. Please top up promptly. | |
203 | Your LVB service has been forcibly disabled. | |
300 | Push with an IP address is not allowed. | |
301 | Unable to identify the push domain name. | |
302 | The push domain name is invalid. | |
303 | The push domain name is disabled. | |
304 | The push application name is disabled. | |
305 | The pushed stream name is in forbidden status. | |
306 | The access mode is channel mode, but the corresponding push channel has not been created yet. | |
307 | The access mode is channel mode, but the current push channel has been disabled. | |
308 | The pushed stream name contains invalid characters. | |
309 | The push application name contains invalid characters. | |
400 | The push client IP is in the blocklist. | |
401 | The push client IP is not in the allowlist. | |
500 | The push does not carry the expiration time parameter. | |
501 | The parameter value of the expiration time has expired. | |
502 | The push does not carry the authentication parameter. | |
503 | Authentication parameter verification failed. | |
600 | The current number of pushes exceeds the maximum value allowed by the configuration. | |
601 | The number of pushes corresponding to the current stream name exceeds the maximum value allowed by the configuration. | |
19 | Third-party authentication failed. | |
20 | The system actively disconnected the push as there was no data for a prolonged time. | |
21 | 100 | A push interruption request from the client was received. |
101 | A playback forbidding request from the client was received. | |
102 | A new push link was received to replace the current push. | |
22 | Unknown reason. | |
23 | Exception with the RTMP protocol content. | |
24 | Internal error in the LVB system. | |
25 | Unknown reason. | |
26 | Unknown reason. | |
27 | Unknown reason. | |
28 | Unknown reason. | |
29 | Unknown reason. | |
30 | Unknown reason. | |
31 | Unknown reason. | |
32 | Unknown reason. | |
33 | Exception with the RTMP AMF data. | |
34 | Unknown reason. | |
35 | The push client actively stopped the push. |
LVB also provides an API for queries. For more information, see DescribeLiveStreamEventList API overview.
Was this page helpful?