Cannot enable historian core via Docker

Ignition
, ,
1 

version: '2.4'
services:
  ignition:
    build: 
      context: ignition
      args:
          IGNITION_VERSION: 8.3.1
    ports:
      - 80:8088
      - 443:8043
      - 8060:8060
    volumes:
      - ignition-data:/usr/local/bin/ignition/data
    cap_add:
      - SYS_RAWIO
      - CAP_NET_BIND_SERVICE
      - CAP_NET_RAW
    environment:
      - ACCEPT_IGNITION_EULA=Y
      - IGNITION_EDITION=standard
      - TZ=America/Chicago
      - GATEWAY_MODULES_ENABLED=com.inductiveautomation.opcua.drivers.ablegacy,com.inductiveautomation.eam,com.inductiveautomation.opcua.drivers.logix,com.inductiveautomation.opcua,com.inductiveautomation.symbol-factory,com.inductiveautomation.opcua.drivers.tcpudp,com.inductiveautomation.vision,web-browser,com.inductiveautomation.historian,com.inductiveautomation.perspective,com.inductiveautomation.historian.sql
      - DISABLE_QUICKSTART=true
      - GATEWAY_ADMIN_USERNAME=admin
      - GATEWAY_ADMIN_PASSWORD=password
    command: >
      -m 4096
      -- gateway.resolveHostNames=true
      -Dignition.license.leased-activation-terminate-sessions-on-shutdown=true
  
  
volumes:
  ignition-data:

I am having an issue with enabling the historian core for 8.3.x in a docker environment. I have com.inductiveautomation.historian added for the gateway_modules_enabled. When I click on enable module

image
image3358×1662 375 KB

I get the following error message:

image
image534×190 8.39 KB

I downloaded the module from the inductive website, restarted the gateway, and I still get the same error. Any help would be greatly appreciated.

2

Can you show us the logs on the gateway?

1 Like
3

Ignition-dc03

image
image3389×348 66 KB

dc2ce34c_Ignition_logs_20251203-1527.idb (132 KB)

4

That looks like you are having authentication issues on the gateway, have you got an LDAP connection set up that is not working?

5

I do not have an LDAP connections that I know of. I am using the default system identity provider

6

Bad IPv6Address: [[${jndi:ldap://10.12.54.58:54491/nessus}]]
This is the bit that I'm getting that detail from. Somewhere your system has a bad hostname/path configured.

Bad Authority: [5eaed2c.jville.com/..] I am also interested in this entry too, does this resemble part of a config you have set up?

7

One aspect with use of GATEWAY_MODULES_ENABLED env var with Ignition 8.3 is that you're basically enforcing the set of enabled modules--enabling or disabling a given module from the UI is blocked. Enable/disable of modules is now retained in the data/modules.json configuration file, so use of this env var is no longer needed to enforce loading of modules (which in 8.1 was based on mere presence of the module file on the filesystem). If you want to be able to control which modules are enabled/disabled, you can omit specifying GATEWAY_MODULES_ENABLED. Since the config is now persisted in your data volume, container lifecycle events will no longer have disabled modules come "back to life" like would happen in 8.1 without GATEWAY_MODULES_ENABLED.

Starting a "stock" inductiveautomation/ignition:8.3.1 container with your GATEWAY_MODULES_ENABLED does result in Historian Core and Historian SQL modules being enabled:

SCR-20251204-lesf
SCR-20251204-lesf3000×1540 331 KB

1 Like
8

Thanks for the on this issue today Kevin. There were persistent environmental variables that were over riding what was being stated in the docker compose file.

1 Like