Troubleshooting

Here are some problems you might encounter while working with licenses.

I can't locate the license file.

Files used by qlicense are stored in the home directory under .qnx/license/. The parent directory depends on your environment:

• For Linux/macOS, the default home directory is $HOME/.qnx/license/
• For Windows, it is %USERPROFILE%.qnx\license\

You can change the license file location via QNX_CONFIGURATION. When setting QNX_CONFIGURATION, be sure that it points to the parent of the license directory, $QNX_CONFIGURATION/license.

The license check failed.

When configuring a build server to use a concurrent build license, you may see a license check error. There are two common types of error messages that indicate the nature of the problem:

• license check failed – If you see this message, you may have forgotten to activate your floating license, or qcc can’t find the license (possibly because the QNX_CONFIGURATION or QNX_CONFIGURATION_EXCLUSIVE variable points to the wrong location).
• License server machine is down or not responding – This message is typically accompanied by an error code. See the FlexNet Publisher's License Administration Guide (including the section on Error Code Descriptions) to debug the issue. The guide is typically placed in home_directory/flexserver/docs/ when you install the floating license package, or refer to enduser.pdf, available through the QNX Software Center with your QNX SDP installation.

I can't connect to the license server.

When you get the Exit code 133 error, reset your machine. If that doesn't solve the issue, check the following:

• Your firewall settings

  Ensure that the license server and the firewall are configured properly. Refer to the Configuring a License Server That Uses a Firewall (Windows) or VPN Access chapter of this guide.

• Your network connectivity

  Sometimes, you have to manually configure the proxy server or provide proxy credentials.

• The license server status

  If the server status is DOWN, try refreshing.

• The QNXLM_LICENSE_FILE format

  Refer to the Environment variables related to concurrent build licenses section of the Configuring a Build Server to Use a Concurrent Build License chapter of this guide.

You can also go to the Addressing License Server Errors section in the QNX Software Center Technotes for more information on server issues.

My system has Linux Standard Base compliance issues.

In some Linux environments, you may encounter problems related to Linux Standard Base (LSB) compliance. It presents in the form of a No such file or directory error when using the LM tools lmutil and lmgrd.

If you encounter this issue, some commands provided in this guide may not work correctly. To avoid this problem, you can either add LSB support to your operating system, or create the LSB linker/loader shared library manually as a symbolic link to the Linux dynamic linker/loader shared library.

For example, for Ubuntu 12.04, 64-bit, run the following command as root (sudo):

ln -s /lib/ld-linux.so.2 /lib/ld-lsb.so.3

For Ubuntu 16.04 or 18.04, 64-bit, follow these steps running as root (sudo):

1. Create the directory /usr/tmp and make it available to all users.
2. Run the following command:

   apt-get install lsb

   Or, use the following command to create the symbolic link:

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

In some cases, running the following commands might resolve the problem:

sudo apt update
            sudo apt install lsb

The IDE or debugging tools do not work with build servers.

This is expected. Certain SDP components cannot be used on a build server, including the Integrated Development Environment (IDE) and debugging and profiling tools. As an alternative for build servers and offline scenarios, SDP 8.0 introduced the qlicense command-line utility for managing licenses without QSC. Refer to the qlicense section in the QNX Utilities Reference for details.