cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AMZN_EIP blank on Linux

AMZN_EIP blank on Linux

Summary

AMZN_EIP blank on Linux

Question

On a RHEL 6.5 64bit system, the AMZN_EIP is blank. When using lmadmin 11.12.1 and vendor daemon that were built on the same version, the license manager is no longer working.

15:13:27 (LUMERICL) Wrong hostid on SERVER line for license file:
15:13:27 (LUMERICL) licenses/LUMERICL/LicenseFile.lic
15:13:27 (LUMERICL) SERVER line says AMZN_EIP=54.76.163.82, hostid is AMZN_EIP=
15:13:27 (LUMERICL) Invalid hostid on SERVER line
15:13:27 (LUMERICL) Disabling 1 license from feature eme_engine(0305 5387 0769 6447 )
15:13:27 (LUMERICL) Disabling 1 license from feature fde_engine(0187 8EE1 1148 1138 )
15:13:27 (LUMERICL) Disabling 1 license from feature FDTD_Solutions_design(027D CBD0 C79F F963 )
15:13:27 (LUMERICL) Disabling 1 license from feature FDTD_Solutions_engine(030E 8B25 031F 83BA )
15:13:27 (LUMERICL) Disabling 1 license from feature Lumerical_DEVICE_design(03EB F132 8F40 9D79 )
15:13:27 (LUMERICL) Disabling 1 license from feature Lumerical_DEVICE_engine(03E9 6D91 C78B 54F5 )
15:13:27 (LUMERICL) Disabling 1 license from feature Lumerical_INTERCONNECT_design(0064 E490 BD61 4C17 )
15:13:27 (LUMERICL) Disabling 1 license from feature Lumerical_INTERCONNECT_engine(0008 830F 2055 CD7D )
15:13:27 (LUMERICL) Disabling 1 license from feature MODE_Solutions_design(0046 CE5A 9444 A9C8 )
15:13:27 (LUMERICL) Disabling 1 license from feature varfdtd_engine(038D 2457 7A28 1139 )

Answer

The Amazon instance in question gave the following error in the log:
20:37:29 (demo) The HOSTID on the SERVER line needs the server to run in Amazon Cloud environment.
20:37:29 (demo) EXITING DUE TO SIGNAL 60 Exit reason 28
20:37:29 (lmgrd) demo exited with status 60 (HOSTID does not match the license server environment (Cloud|Virtual|Physical))
20:37:29 (lmgrd) No feature will be served.

This error told us the Amazon cloud detection code detected the user wasn't running on Amazon Cloud environment. This could happened when the IPv4 address mapped with the hostname isn't corrected.

By default, the IPv4 address of the Amazon instance should match with the default private IP address assigned by Amazon (the hostname of the instance usually gives the hint of default private IP. For example, the default IP is 10.0.0.244 and the hostname is ip-10-0-0-244.eu-west-1.compute.internal).

In the case of this Amazon instance, the assigned private IP address is 10.0.0.244. However, the IP address configured inside the /etc/hosts was 10.0.0.158. After the IP address was changed from 10.0.0.158 to 10.0.0.244 in /etc/hosts, the server was able to start with AMZN_EIP.
Labels (2)
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Nov 13, 2018 10:24 PM
Updated by: