Troubleshooting an OPCUA Collector that Fails to Start

Important: You do not have the latest version of Historian! You are missing out on the newest capabilities and enhanced security. For information on all the latest features, see the Historian product page. For more information on upgrades, contact your GE Digital sales agent or e-mail GE Digital Sales Support. For the most up-to-date documentation, go here.

Possible Causes

Following are some possible causes and solutions to troubleshoot an OPCUA Collector that fails to start:

An OPCUA Collector fails to start, if:

  • Historian is trying to run the OPCUA Collector before the OPCUA Server fully starts.
  • Libraries shipped with the collector are missing.
  • There is not enough free space for the collector to create its buffer files on startup.

Review the OPCUA Collector log file to isolate the cause of the issue.

Possible Solutions

If the OPCUA Collector fails to connect to OPCUA Server:

  • Check that the General1 property is set to point to the correct OPCUA Server.
  • Check that the OPCUA Server is up before starting the collector.
  • Check the Secure Connectivity property. If it is set to true, make sure that the client certificate is in the trusted list of the server.

If the OPCUA Collector fails to start with a message about missing libraries:

  • Check that the LD_LIBRARY_PATH is pointing to the libraries shipped with the Collector.
If the OPCUA Collector fails to start, with no message about missing libraries:
  • Clean the HistorianServers.reg file of all entries except the default entries which are present in the default .reg file.
  • Delete all the .log, .shw, .msq, .hdr, and .cfg files from previous runs of the Collector.