Logs and troubleshooting
This table provides definitions of the status and error codes that the IoT Edge Connect logs in the connection monitoring topics.
Each status and error code consist of a letter and a number. The letter tells you the category where the status code or error belongs. These are the available categories:
-
C - Configuration
-
J - JSON Web Token (JWT)
-
M - Mutual Authentication
-
A - Authentication
-
F - Broker servers
-
D - Connection drop
Connects
This table presents the definition of the status code that the system logs in the following connection monitoring topic $SYS/monitor/con/connects
.
Status code | Status description | Additional data |
---|---|---|
00 | Successful connection. | - |
Errors
This table presents the definition of the error codes that the system may log in the following connection monitoring topic $SYS/monitor/con/errors
.
Error code | Error description | Additional data | Troubleshooting |
---|---|---|---|
C1 | You haven't configured an authentication method for this namespace. | - | Check your IoT Edge Connect configuration. |
C3 | You haven't configured your namespace for the specified hostname. | - | Check your IoT Edge Connect configuration. |
J1 | No JWT present during the connection. | - | Check the following connection options of your MQTT client: |
J2 | No JWT in the MQTT CONNECT or Websocketâs header. | Specific parse error | Check the validity of the token. |
J3 | A JWT signature is invalid. | - | Check if a JWT was sent with a correct private key. |
J4 | An unsupported signing algorithm for a JWT. | Algorithm received | Check if RS256 signing algorithm was used to encrypt the JWT. |
J5 | A JWT has expired. | Expiration time | Check the JWT expiration date. It can't be set to the past date. |
J6 | The nbf claim in the JWT doesn't allow this token to be processed. | Start time | Verify your JWT's nbf claim. |
J7 | You haven't passed any client ID claim in a JWT. | - | Check if the token has an ID claim. Check if the client ID field isn't empty. |
J8 | You haven't passed any authorization group claim in a JWT. | - | Check if the token has an authorization group claim. Check if the authorization group claim isn't empty. |
M1 | Client certificate didn't pass validation. | Validation error | - |
M2 | You haven't passed any client ID claim in the client certificate. | - | Check if the certificate has an ID claim. Check if the Client ID claim isn't empty. |
M3 | You haven't passed any authorization group claim in the client certificate. | - | Check if correct authorization group was passed during the connection. Check if the correct authorization group was passed in the certificate. |
M4 | Your mutual authentication behavior failed to include authorization groups | - | Contact technical support. |
M5 | Your mutual authentication behavior failed to include client ID. | - | Contact technical support. |
A1 | Client ID in MQTT Connect settings is different from the one in the JWT set as a password for the MQTT connection. | Client ID received in MQTT Connect | Check if the correct client ID was passed during the connection. Check if the correct client ID was passed. Check the client ID in the JWT. |
A3 | The system can't validate the client ID you sent. | Specific parse error | Consult the parse error for more details. |
A4 | The system can't use the authorization groups you sent. | Specific parse error | Consult the parse error for more details. |
Drops
This table presents the definition of the status codes that the system may log in the following connection monitoring topic $SYS/monitor/con/drops
.
Status code | Status description | Additional data |
---|---|---|
D2 | Publish to an unauthorized topic. | Name of the topic |
D4 | Your connection is dropped due to the exceeded system limit. For example, the maximum number of connections for the namespace is exceeded. | - |
D5 | Client time-out. The client hasn't sent a ping request within the set keep alive period. | - |
Updated about 2 years ago