Re: IC 5033 with Suse 9
The problem is that you had already started the cdslmd daemon multiple times. And the cdslmd.lock had been locked by a previous cdslmd daemon. The solution is to find out those lmgrd and those accompanied cdslmd daemon processes. Then kill all of them. Try to find out cdslmd.lock file and delete it also. It is usually at the /var directory.
So the steps are as this:
1. su root <cr> -- in an opened terminal windows.
2. ps -A | grep lmgrd <cr> -- take note of the lmgrd processes ID.
3. ps -A | grep cdslmd <cr> -- take note of the accompanied cdslmd processes ID.
4. kill lmgrd_processesID <cr> or kill -9 lmgrd_processesID <cr> -- to kill those processes. So do the cdslmd_processesID.
5. find / -name cdslmd.lock -print <cr> -- to find out the lock file. Then delet it.
6. lmgrd -c your_cadence_license_file -log your_log <cr> -- to restart the license server. Remember you only need to run this once and only once. This server will serve any users logged on to use cadence licensed eda tools.
Good Luck.
Added after 31 minutes:
iyad_tubs said:
I don't have any lmgrd or cdslmd servers running.???
the local-instalation directory is not mounted from the server, must it? what files should I have on the server.
1. If you only want the mentioned Server served as a license server, then you only need to install the lmgrd, lmutil,... etc togethered with the cdslmd and its license file on the server. That's all enough to start the license server. But at your license-Client side, you have to setup the license client environment variable to let the eda tool get license from. The license client setup is by putting this line in your .bashrc or .cshrc "export LM_LICENSE_FILE=port@LicenseServer" or "setenv LM_LICENSE_FILE port@LicenseServer" respectively.
2. If you want the mentioned Server also served as a file server for your client-Box, then the story is totally different. You have to install license server on the file server, then start it. You also have to install the eda tools on the file server and mount it back on your client-Box if you want to start the eda tool on your local client-Box. Even this way, you also have to setup the client environment variable as described in <1> in your client-Box.
But I think your choice is <1>, if my guess not wrong.
Bless you.