... mac address and hostname
I'm trying to do an AWS deployment of EZD without needing to maintain static infrastructure. I am running it inside of the default Centos docker image with a few modifications to install EZD 1.2.1 and related config. EZD starts and immediately complains: NODE ID IS MISMATCHED WITH LICENSE KEY
I am extremely certain that the hostname and mac address for the container correspond exactly to what was provided to the account rep.
These fields are listed as some public license info:
LICENSETYPE = STANDARD
PRODUCT = EZD
VERSION = 1.2
This is my EZD log:
ezd (version ezd1.2.F3) Initialization Start.
<END>
<<redacted>-elektron-preprod.1.ezd: Info: Wed Jun 27 03:10:02.360818 2018>
The Configuration Database is using the file /opt/thomsonreuters/SOFTWARE/globalconfig/ezd.cnf .
<END>
<<redacted>-elektron-preprod.1.ezd: Info: Wed Jun 27 03:10:02.360859 2018>
ezd main thread Using Epoll Event Notifier.
<END>
<ServerSharedMemory: Info: Wed Jun 27 03:10:02.361054 2018>
Allocated
<END>
This is the program stdout/err:
License File: /opt/thomsonreuters/SOFTWARE/globalconfig/licensefile/ezd-license.txt
License Status: NODE ID IS MISMATCHED WITH LICENSE KEY. Please contact your Thomson Reuters representatives or your administrator
ezd: Initialization Failed -Check Log-
ezd Error: Initialization failed
Is running EZD on Centos even supported? Is there a mismatch here between license version 1.2 and the patch version deployed at 1.2.1? Is there some internal syscall missing for the container and EZD is hiding the error?
I have little to no visibility on this one - pinging account rep for context but any other common use cases or pointers would be great to know about.
