Edge Troubleshooting

Linux provides many built in tools to evaluate the Edge functionality. This article identifies select tools and workarounds.

About Edge Configurator (web control panel)

As of platform release 20.07, Edge Configurator is a web app for the IoT Edge administrator to inspect system health, resource usage, and configure network options, as well as carry out other maintenance operations. The Edge Configurator continually receives improvements and new features. In a future platform release, it may offer a graphical workflow for initial configuration of the Edge.

By following the software acquisition and installation instructions above, the Edge Configurator will start automatically via the system service abb-edge-configurator.service and serve HTTPS traffic on port 443 by default. To use an alternative HTTPS port, change /etc/abb-edge-configurator following this example:​

HTTPS_PORT=8443

Next, restart the system service: systemctl restart abb-edge-configurator.service​.

Potential Malfunction in Docker

Occasionally, Docker software may malfunction and prevent the Edge Proxy (an essential component) from starting after a system reboot. When the malfunction occurs, the equipment user will not receive any failure indication. This malfunction affects only a small number of users.

The earliest noted malfunction occurred in November 2018. The culprit traces to an issue discovered in the Docker daemon itself, resulting in the following bug report to Docker developers: https://github.com/moby/moby/issues/38318

As of 2019-06-20, Docker developers have not made any progress toward a permanent resolution. If your Edge deployment suffers from this issue, a temporary remedy is available via the pre-installed system service abb-iot-edge-replay-netconf.service. The service resets the Docker daemon upon system reboot, which clears the malfunction.

To permanently enable the workaround, proceed with Edge installation via abb-iot-edge-setup, and afterwards run systemctl enable abb-iot-edge-replay-netconf.service to permanently enable the workaround. After enabling the workaround, Docker will not encounter the malfunction again, however, the Edge will have to use Internet connectivity to bring business line modules online after reboot (whereas business line modules come online even with the absence of Internet connectivity without the workaround).

Other Diagnosis Tips

• To inspect the status of the device ID certificate acquisition and renewal, run journalctl -u dpcm*.
• To inspect the launch sequence of Edge containers, run journalctl -u abb-iot-edge. To inspect the individual container output, first identify the container's ID from the output of docker ps -a, then use either docker logs -f ##### or journalctl CONTAINER_ID=##### to retrieve the output.​