Diagnostic Practices

The purpose of this page is to assist with the initial troubleshooting and set up basic diagnostics in case you encounter problems with licenses. These are tips and step-by-step guides, which our support colleagues usually recommend as a potential solution, or ask for as additional information on tickets.

If neither of these steps, our Troubleshooting or FAQ pages can not help you, you can still contact our support team at support@hightec-rt.com.

Check RLM_LICENSE

As a typical first step, please check if the value of the environment variable RLM_LICENSE on the client computer where the toolchain is used is set to:

  • the license server’s <port_number>@<host_name> (in case of Floating License)

  • the exact path of the directory of the license file (in case of Node-Locked license)

If you need additional help with this, please check the "How to check the value of RLM_LICENSE environment variable?" section of our FAQ.

Check PATH

Please check if the value of the environment variable PATH contains the path of the installation folder of the toolchain executables and also the path of the license manager-related DLLs and executables (by default, C:\HighTec\licensemanager).

How to check that you can access your license server?

To verify license server accessibility…​

On Windows, open PowerShell as Administrator and run:

Test-NetConnection -ComputerName <server-name> -Port <port-number>

On Linux, open a terminal and run:

nc -zv -w 5 <server-name> <port-number>

Where:

  • "server-name": is the name of host machine where the license server is run

  • "port-number": is the used port of the server, it is 5053 by default

For more examples, please visit Reprise communication troubleshooting page.

Setting up Diagnostics - Client Side

For diagnostic purpose there are a number of environment variables related to RLM, which you can set manually on the client side.

Windows cmd:

set RLM_DIAGNOSTICS=<debug-log-file-path>
set RLM_EXTENDED_ERROR_MESSAGES=1

Linux bash:

export RLM_DIAGNOSTICS=<debug-log-file-path>
export RLM_EXTENDED_ERROR_MESSAGES=1

NOTE: Although it seems logical to set RLM_DEBUG=<product-name> (like RLM_DEBUG=tricore-gcc) too, setting this one can cause compilation to hang. If you encounter an error like this during compilation, check the value of this variable and try to delete it.

After starting the compilation, a log file is generated in the configured path. This log file is quite useful for investigating the issue.

If you want to know more about the environment variables used by RLM, you can find relevant information in the Reference Material of RLM.

The support team kindly requests that you provide both the client- and server-side log files when contacting them.

Setting up Diagnostics - Server Side

To obtain the server-side diagnostic log, restart the rlm.exe with the -dlog <logfile> option to enable logging. For more information, see RLM Documentation - License Server Startup Options.

The support team kindly requests that you provide both the client- and server-side log files when contacting them.

Sample Compilation

In case you are experiencing trouble with the license checks while compiling, you can run a test by creating a dummy main.c file elsewhere and try to compile it via your terminal. This way, it is easier to conclude where the error is coming from.

main.c:

int main(void) {
    return 0;
}

Open a new command prompt (don’t use one that was already open) and try to compile the previously created main.c by invoking your toolchain (tricore-gcc in this example):

> cd <your_main.c_location>
> "<your_toolchain_location>\bin\tricore-gcc.exe" -c main.c