Q1: I downloaded the Floating License support files on Linux, but running lmgrd, lmutil, or lattice fails with "cannot execute: required file not found." Are the files corrupted?
A1: The files are not corrupted. This error typically indicates that a required Linux dynamic loader, specifically the LSB compatibility link, is missing on the system, rather than an issue with the FlexNet binaries themselves.
Q2: Why does this issue commonly occur on newer Linux distributions such as Ubuntu 24.04?
A2: Newer Linux distributions may not include the legacy LSB loader path by default. The FlexNet binaries expect the LSB loader path (/lib64/ld-lsb-x86-64.so.3) to be present, which causes execution failures when the expected symbolic link does not exist.
Q3: How can I confirm this is the cause before changing anything?
A3: Inspect the requested interpreter with the following command. If it requests /lib64/ld-lsb-x86-64.so.3 and that file does not exist, the missing LSB loader link is confirmed as the cause.
readelf -l ./lmgrd | grep interpreter
Q4: How can I fix this issue on Ubuntu or a similar Linux distribution?
A4: Create the required directory and symbolic link, then update the linker cache. These commands require root privileges:
sudo mkdir -p /lib64
sudo ln -sf /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
sudo ldconfig
After running these commands, lmgrd, lmutil, and lattice should run and report their version correctly. On the RHEL family, the link target is /lib64/ld-linux-x86-64.so.2 instead.
Q5: Which Linux distributions are officially supported for the Floating License utilities?
A5: FlexNet Publisher utilities are officially validated on selected versions of RHEL, SUSE, and Ubuntu. Other distributions, such as Rocky Linux, are not officially supported. Because they are binary compatible with RHEL, they often work with additional manual configuration, but support on these platforms is best effort.
Q6: Does this fix apply to Rocky Linux 8 as well?
A6: Rocky Linux 8 is not officially validated, but because it is RHEL compatible, the same workaround may apply. Results can vary depending on system configuration, and additional dependencies may be required.