Troubleshooting
This section explains how to resolve some typical issues that you might encounter.
This list provides common issues. See the IIoT Core Release Notes for known issues and workarounds.
Subscribe to errors
Subscribe to errors to preemptively catch and handle any errors as they occur.
Errors from the message broker are sent to the error routing (binding) key hiota-errors.
Use the RabbitMQ user interface for error subscription. Include the following information to subscribe to hiota-errors:
- URL: https://<cluster_fqdn>:31671
- Login: admin
- Password: (Ask your administrator)
- Host: <IP-address>
- Port: 30671
- Error Routing (Binding) Key: hiota-errors
- Exchange Name: hiota-exchange (default)
Access gateway logs
You can obtain a log of the services running on a gateway.
You can use the gateway log to troubleshoot problems on the gateway.
Before you begin
Procedure
In the IIoT Core Services UI, select the Device tab.
Select Logs from the Actions menu next to the device description.
Select Request New Log.
Establish a time frame by selecting a time or date number, and then select the up or down arrow to adjust the number.
Select Request.
When the status shows Success, select Download Log.
Change log rotation in IIoT Gateway
To ensure that the IIoT Gateway software is able to run in a healthy and continuous way, the gateway log rotation is turned on by default.
The log rotation is configured as follows:
Property | Value |
enableDockerLogRotation | true |
dockerLogMaxFiles | 7 |
dockerLogMaxSize | 100 |
log level | Info |
Because the default maximum number of Docker log files is 7 and the maximum size of each log file is 100 MB, by default at most 700 MB disk space can be consumed by Docker logs.
You can change the default values for log rotation on the IIoT Gateway. Use SSH to connect to the gateway and edit the following file: /etc/hiota/agent/configs/configuration.yaml.