General Troubleshooting Tips

Historian for Linux Starts in Demo Mode

Cause

The Historian for Linux database container must have a valid license file for all enabled features, including high tag count support. If a valid license is not provided Historian for Linux switches to demo mode (which supports only 32 tags) while starting the Docker container.

Solution

Use the HS_LICENSE_FILE_PATH environment variable in the historian-archiver-conf.json file to provide the absolute file path of the valid license file.

For example, if you mount a /data/edgedata directory with /data/ with Historian archiver Docker, you can keep the license file in the /data/edgedata/historian-license folder on the host machine. But you must set the environment variable to /data/historian-license because in a Docker-container context, the path is /data/historian-license.

Web Admin Fails to Start

Cause

The web admin is a web application hosted in a Tomcat server inside a Docker container. Sometimes the host machine has its own Tomcat server running and bound to a standard Tomcat port like 8080 or 8443, so when the web admin Docker container is started, a port conflict occurs between the Tomcat server running inside the Docker container and the Tomcat server running directly on the host machine.

Solution

Stop the Tomcat service of the host machine.

As a protective measure, in the docker-compose.yml file of web admin, port 9443 of the host machine is mapped with port 8443 of the web admin Docker container, so that the web admin Docker does not conflict with port 8443 of any other service on the host machine.

Server-to-Server Collector fails to connect to the Destination and Source Historian

Cause

The Historian archiver Docker is a TCP/IP server, listening on port 14000. The server-to-server collector is a Historian for Linux client, which connects to port 14000 of the machine on which the Historian archiver Docker is running. Usually, we do not publish port 14000 of the Historian archiver. Because of this, the Historian for Linux client Dockers (such as the server-to-server collector) which do not join the Docker network of Historian archiver, will not be able to use the port 14000.

Solution

Publish port 14000 of the Historian archiver, if you want Historian for Linux clients to be connected to Archiver from outside of Historian Archiver’s docker network.

Detailed Logs of the MQTT Collector, Server-to-Server Collector, and Historian Archiver

Cause

The Historian archiver, the MQTT collector, and the server-to-server collector logs do not go to Docker logs. Therefore, it is difficult to analyze the operations logs of these applications.

Solution

Historian archiver logs are available in the <mounted host’s data directory with docker container>/archiver/Logs folder. The MQTT collector and server-to-server collector logs are available in the mounted host’s data directory with the Docker container folder.

Connection to the OPCUA DA Server Fails

Cause

The session may have timed out when the OPCUA DA collector tried to connect to the OPCUA DA server.

Solution

Ensure that the RetryInitialConnect and AutomaticReconnect parameters are set to true in the ClientConfig.ini file.