Table of Content

Figure 1: FlexNet administration page

Figure 2: Vendor Daemon Configuration page

Figure 3: State of the license daemon

...

If the installation directory does not exist, create it:

$> mkdir /opt/NanoXplore

To install the NanoXplore License Manager Daemon, unpack NXLMD-2.2-linux.tar.gz file into the installation directory using the following command:

$> tar xzvf NXLMD-2.2-linux.tar.gz -C /opt/NanoXplore

Linux distribution adaptation

The NanoXplore License Manager Daemon supports several Linux distributions. You have to point to the correct one in updating the symbolic links in the directory

$> ln -sfn x86_64_RHEL_7/lmgrd lmgrd

...

$> ln -sfn x86_64_RHEL_7/lmhostid lmhostid

...

$> ln -sfn x86_64_RHEL_7/lmstat lmstat

...

$> ln -sfn x86_64_RHEL_7/lmutil lmutil

...

$> ln -sfn x86_64_RHEL_7/NXLMD NXLMD

...

$> ln -sfn x86_64_RHEL_7/lmadmin lmadmin

Linking libraries

The NanoXplore License Manager Daemon needs the library ld-lsb-x86-64.so.3 which might not be installed on Linux distribs. The following command must be done:

$> ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

Retrieve information for licensing

...

the name of the host where the License Manager Daemon is installed, use the following command:

$> hostname

the License Manager Host ID provided by the binary located in /opt/NanoXplore/NXLMD/2.2/bin, use the following command:

$> /opt/NanoXplore/NXLMD/2.2/bin/lmhostid

License file

Once you get the license file it has to be copied in the installation directory:

$> cp license.lic /opt/NanoXplore/NXLMD/2.2/license.lic

Install in a non-default directory

You can install NXLMD in a non-default directory ${MY_INSTALLATION_DIRECTORY} using the following command:

$> tar xzvf NXLMD-2.2-linux.tar.gz -C ${MY_INSTALLATION_DIRECTORY}

You also have to change the path in the license file:

• ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/license.lic

$> DAEMON NXLMD ${MY_BIN_DIRECTORY}/NXLMD

with ${MY_BIN_DIRECTORY} = ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/bin/.

...

Simply copy the lmadmin.service file to /etc/systemd/system directory:

$> cp /opt/NanoXplore/NXLMD/2.2/etc/lmadmin.service /etc/systemd/system/

Please make sure that the user and group specified in lmadmin.service file exists.

Please make sure that the user has writing rights in /opt/NanoXplore/NXLMD.

...

Note

If you choose to use the default user specified in the lmadmin.service file, you will have to execute the following commands:

$> useradd lmadmin

...

$> chown -R lmadmin:lmadmin /opt/NanoXplore

Manual execution

To manage the NanoXplore License Manager Daemon manually, you can use the following commands:

• start

$> systemctl start lmadmin

• stop

$> systemctl stop lmadmin

• restart

$> systemctl restart lmadmin

Automatic execution

Use systemctl to add the new service:

$> systemctl enable lmadmin

Then start the NanoXplore License Manager Daemon with the following command:

$> systemctl start lmadmin

To print status information about the NanoXplore License Manager Daemon, use the command:

$> systemctl status lmadmin

Execution log files are available in /opt/NanoXplore/NXLMD/ directory.

...

To stop the NanoXplore License Manager Daemon, use the command:

$> systemctl stop lmadmin

Windows

Manual execution

Launch a Windows PowerShell and go to the installation directory of NXLMD:

$> cd C:\NanoXplore\NXLMD\2.2\bin\lmadmin

To launch the lmadmin service, use the following command:

$> .\lmadmin.exe

Automatic execution

Launch a Windows PowerShell as administrator and go to the installation directory of NXLMD:

$> cd C:\NanoXplore\NXLMD\2.2\bin\lmadmin

To add the lmadmin service to Windows run the following command:

$> .\lmadmin.exe –installService lmadmin

Configuration of lmadmin

Once lmadmin service is launched, you have to configure it.

...

You can check the execution log file in the following directory if you use the service nxlmd:

$> /var/log/NXLMD.log

If you use the service lmadmin, you can check the execution log file in the following directory:

$> /opt/NanoXplore/NXLMD/2.2/bin/lmadmin/logs/NXLMD.log

Windows

You can check the execution log files in:

$> C:\NanoXplore\NXLMD\2.2\bin\lmadmin\logs

lmadmin (Linux)

If you have the following message in the /opt/NanoXplore/NXLMD/2.2/bin/lmadmin/logs/web.log:

[alert] getpwuid: couldn't determine user name from uid 4294967295

You probably have launched lmadmin as root.

...

If you have the following message in the execution log file (for example):

Wrong hostid on SERVER line for license file:

...

              ${MY_LICENSE_FILE}

...

SERVER lines says 08002780463d, hostid is (Can't get hostid of type 2 [])

...

Invalid hostid on SERVER line

with ${MY_LICENSE_FILE} = ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/license.lic

...

If you want to check the hostid found by NXLMD without running the server, you can use the following command:

$> ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/bin/lmhostid

You have to get a full hostid with ${HOSTID} not empty:

The FlexNet host ID of this machine is "${HOSTID}"

lmstat (Linux)

You can check that NanoXplore License Manager Daemon runs correctly using the following command:

$> ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/bin/lmstat -a

GLIBC problem (Linux)

If you have the following error message:

...

You have to change the links in directory ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/bin to your OS version. For example:

lmgrd -> x86_64_UBUNTU_18/lmgrd

...

lmhostid -> x86_64_UBUNTU_18/lmhostid

...

lmstat -> x86_64_UBUNTU_18/lmstat

...

lmutil -> x86_64_UBUNTU_18/lmutil

...

NXLMD -> x86_64_UBUNTU_18/NXLMD

hostname problem (Linux)

You can check that you have your hostname written in the file /etc/hosts.

...

You can manually specify the NXLMD port in license file. For example, to set the port 27010:

$> DAEMON NXLMD ${MY_BIN_DIRECTORY}/NXLMD PORT=27010

with ${MY_BIN_DIRECTORY} = ${MY_INSTALLATION_DIRECTORY}/NXLMD/2.2/bin/

...

If you have the following message when launching ‘journalctl –xe’ command:

$> lmadmin.service: Failed at step EXEC spawning /opt/NanoXplore/NXLMD/2.2/bin/lmadmin/lmadmin: No such file or directory

The ld-lsb-x86-64.so.3 file is probably missing. Run the following command to check it:

$> ls -l /lib64/ld-lsb-x86-64*

If there is no result, run the following command:

$> sudo ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3