Q. How can I troubleshoot RTDA licensing?
A. See the following discussion:
During normal operation, the RLM licensing used by RTDA has two daemon processes that run on the primary license host, the one whose hostid is in the HOST line of the license file. These daemons are 'rlm' the top level daemon that manages individual vendor daemons, and 'rtdad' the RTDA vendor daemon.
0. Verify that the value of the RLM_LICENSE environment variable is correct. This should be of the form port@host, where 'port' is 7070 unless you have changed it, and 'host' is the hostname of the license server.
We recommend that you use the port@host form and not the path to the license file, so that NFS is not needed.
1. Check the status of the licenses by
% rlmstat -avail
This command is handy because it shows a compact summary of the licenses, and how many are checked out without the full details.
2. If you are starting RTDA licensing for the first time or have just installed a new license file, verify that the hostid in the HOST line matches the one of the machine where you are trying to run the license server. For Sun, HP, and IBM machines, we use the built-in hostid of the machine. On Linux, Windows, and MacOSX, we use the Ethernet MAC address of the primary network interface card. You can use the RTDA 'vovhostid' command to find the hostid to use. Do not use the hostid returned by the built-in Linux 'hostid' command.
3. Check that the hostname on the HOST line is the same as that returned by the 'hostname' command, or is set to 'localhost' to use the loopback interface.
4. Check that the path to the 'rtdad' daemon is correct for the version and platform (CPU/OS) of your license host. Some licenses are shipped with the string @VOVDIR@ in the path to indicate that you must change it.
5. Verify that the license features you need have not expired.
6. Use the ps() command to be certain that both component processes of the license server are running. A handy command is:
% ps auxww | egrep '(rlm|rtdad)'
If you see only one of the two processes running, stop the running one with the OS kill() command and restart the license server as described below.
7. Start the license server as the role account owning the RTDA software, by changing to the directory containing the license file, and using the command
% rlm -nows -c license.rlm -dlog reprise.log &
The '-nows' option turns off the built-in webserver, and the -dlog option specifies the name of the logfile, which is very useful for license troubleshooting.
8. Read the license server's logfile. This is helpful after first starting it, or when trouble is encountered, because often the logfile will contain helpful information.