| |||
| Home > Frequently Asked Questions about Licensing > Problems with server configuration > Server debug log reports “(armlmd) cannot open lock file” or “cannot communicate with lmgrd” | |||
The lock file error most commonly occurs on a Unix/Linux system
if a previous instance of the armlmd license
daemon was not shut down properly. Only one copy of armlmd can
run on your license server at any given time. Attempting to start
another copy of this daemon causes an error.
When the ARM license daemon, armlmd,
is started, it creates a file called /var/tmp/lockarmlmd.
If lmgrd terminates abnormally, armlmd does
not release the lock file because it might still be running.
To solve this problem, locate any license daemon processes. You can do this using the following command on Unix/Linux:
ps -a | grep daemon_name
where is daemon_namelmgrd or armlmd.
Shut down lmgrd first.
Next terminate these processes with:
kill PID
where is
the process ID for the license daemon.PID
Delete the /var/tmp/lockarmlmd if it
still exists.
If you are using Windows, use the Windows Task Manager to
locate the lmgrd or armlmd processes.
Shut down lmgrd first. Select the process,
then click End Process.
You can now restart the license server.