After receiving the product license file(s) from Avenza Activation, extract the license file and place it in the same folder as the RLM binary files. Installing and configuring RLM will require access to the command prompt. If you have multiple license files for multiple products, place all of the license files in the same folder where the RLM binaries are stored.
After receiving the license file(s) from Avenza Activation department, extract the license file and place it in the same folder as the other binary files. Setting up RLM will require access to the terminal window.
Using Terminal
1.Extract Avenza_FloatingLicense_RLMv12.zip to a convenient location on your hard drive. This will be the folder from which the program will run.
2.Open the Terminal Window (go to Applications / Utilities, then select Terminal).
3.Navigate to the directory where all the binaries and the license file are stored.
4.Type ./rlm
For example, this line indicates that your server is running properly for MAPublisher and other Avenza products. Depending on how many product licenses you have, this line may be different.
Make sure that avenza, rlm, and all of the license files are placed in the same directory.
Ensure that the license file has the .lic extension (e.g. MAPublisher.lic).
Troubleshooting RLM Server Setup
When setting up RLM, its behaviour may be observed from the log file if RLM is running. The following is a brief list of troubleshooting tips regarding error or warning messages that may appear in the server log.
|
Issue |
Possible Solution |
|
|
Warning: No license file for this host (Server name); The host name in the license file(s) may be incorrect. |
A possible cause of this issue is that the license file does not have the appropriate extension (.lic). Please ensure that the license file has the correct extension (.lic) at the end of the file name. |
|
|
RLM Version: What is the appropriate version of RLM for MAPublisher 10.x? |
The appropriate version of RLM for MAPublisher 10.x is RLM version 12.x. The version number can be indicated in one of the server log lines, e.g. “01/06 12:17 (rlm) RLM License Server Version 9.3BL2” |
|
|
Error: (rlm) Port 5053 in use, waiting... |
This log line appears when port 5053 is used by other applications. RLM version 12.x uses port 5053 (TCP/IP) by default. In order to solve this problem, a port number can be specified in the license file. Enter the port number at the end of the HOST line in the license file. As this port number is not included in the encryption code, any encryption process from the Avenza Activation Department will not be required. However, please ensure that the license file has the file extension .lic after saving the file. The example below shows that port number 5055 is specified.
Another cause of this issue is that RLM is already running. Check whether or not the RLM is running in the Activity Monitor (/Applications/Utility/Activity Monitor). When RLM is running, rlm and avenza will be listed.
|
|
|
Error: (rlm) Cannot bind Web Server port 5054, existing... |
A web browser is required to access the RLM administrator page. This log line appears when port 5054 is used by another application. RLM version 12.x uses port 5054 for the web server port by default.
In order to solve this problem, a port number can be specified with a command prompt line when running RLM (as a service). The argument word to be used to specify the web port number is -ws <port number>; the examples below show the web server port number specified as 5555.
When running RLM
|
|
|
Error: (avenza) problem with executable - unable to start . . . (rlm) avenza executable path: avenza |
This error message appears when the binary file “avenza” does not have appropriate permission to execute when running “RLM”. In order to solve this, the file must be assigned an appropriate privilege to the avenza binary file as suggested below.
When running RLM
This line above can be interpreted as adding a permission of executable to all the users on the "avenza" binary file. Run rlm (./rlm) after the privileges of the avenza binary file is modified. |
|
|
Error: (avenza) cannot set server lock - exiting (rlm) avenza - lockfile problems |
This error only affects Mac/Linux. This error message appears when the lock file named .rlmlockavenza is interfering with RLM. The solution to this problem is to delete the lock file with a command in the Terminal window.
Before the lock file is deleted, both rlm and avenza must be stopped. Otherwise, it is not going to allow to delete the lock file. This process can be stopped from the Activity monitor (/Applications/Utility/Activity Monitor) or command line.
1. Open the Activity Monitor (/Applications/Utility/Activity Monitor). 2. Find the name rlm, then click Quit process. When prompted, select Force quit. 3. Repeat the same step for the process name avenza. 4. Open the terminal window and navigate to the location of the.rlmlockavenza file by typing: cd /private/var/temp/ 5. The .rlmlockavenza file is a hidden file. In order to view the file in the directory, type ls -la. 6. Remove the .rlmlockavenza file by typing: rm .rlmlockavenza 7. Navigate to the directory where all the RLM binaries and the license file are stored. 8. Run rlm. |
Comments
0 comments
Please sign in to leave a comment.