# 10 Licensing FAQ¶

## 10.1 General questions¶

Q: How do I know what version/expiry/hostid/port I have in my license file?

The license file is a plain text file. Open it in any text editor and follow Sec. 5.2 (The License File).

Q: Can I edit the license file?

You can change the port number(s), add an OPTIONS section and edit comments. Any other edits (in particular changing the hostid) will invalidate the license file.

Q: Can I reserve some of my floating tokens to a specific IP/username/group?

To reserve a certain number license features for a particular user or IP address, you must create an additional options file and use the RESERVE option. For details see FLEXnet license administration guide. For example, to reserve one PTS token for user username make an options file res.opt with content

RESERVE 1 PTS USER username


VENDOR MOSEKLM OPTIONS=res.opt


Q: Is it possible to use MOSEK with a floating license on a machine detached from the LAN(WAN)?

Yes. It is possible to use the lmborrow functionality. See the FLEXnet license administration guide.

Q: Do you have a complete licensing guide that covers all of FLEXlm options?

Q: I know the hostid of the license server, but what about the clients?

The clients, that is machines on which MOSEK optimizations will actually be performed, can be arbitrary, as long as they can connect to the license server to check out a token. The floating license restricts only the physical machine for the token server.

Q: What does MOSEK use to verify the license?

Only the license file. There is no external communication whatsoever.

Q: When does MOSEK return the floating license token?

By default at the end of the session/process or when the MOSEK environment is deleted. This reduces the checkout overhead if one process runs multiple optimizations. However, this is completely customizable. For example, you can return the token after each optimization or upon calling a dedicated method. Your API’s manual has instructions on how to do it in the section Technical guidelines / The license system.

Q: The lmutil and lmgrd will not start on Linux: No such file or directory.

If you run a command from the licensing system and get this error:

user@hostname:~/path_to_mosek\$ ./lmutil
./lmutil: No such file or directory


then most likely you are missing the Linux Standard Base (LSB) package. LSB version at least 3 is required. On Ubuntu the latest version of LSB can be installed with the command apt-get install lsb.

Q: I get the error Vendor daemon is too old.

You are running an older license server (for example, from version 7) and tried to connect to it with a much more recent client (for example, from version 9). The lmgrd license server must be at least as new as all the clients who attempt to connect to it. Use the license server distributed with the most recent version of the clients in use. We occasionally update the FLEXlm binaries inside MOSEK and then an incompatibility with older license servers may occur.

Q: The license server will not start.

Always check the server’s log file lmgrd.log. It will explain the source of the problem. Typical issues are:

• Wrong hostid: the hostid in the license file does not correspond to actual hardware. Either you are running the license server on the wrong machine, or using a wrong file or something changed on the machine and you will need a new license file.
• Could not open port: the token server or vendor daemon could not open a port. Possibly it is already open by another process, or there are firewall issues. In either case consult Sec. 7.4 (Changing default ports and firewall and antivirus issues) for a solution.

Q: The client cannot connect to the license server or license checkout times out.

The following symptoms can indicate firewall issues:

• The client cannot connect to the license server. The error is MOSEK cannot connect to the license server or Operation now in progress.
• The client cannot connect to the license server from a remote machine, but everything works when the client runs on the same machine as the server.
• License checkout times out after about 60 seconds with message Timeout: operation now in progress.

First make sure that the license server is up an running and that the lmgrd.log file did not indicate any errors (see previous question). Assuming that, consult Sec. 7.4 (Changing default ports and firewall and antivirus issues), fix both ports described in that section (the token server port and the vendor port) to your preferred values, make sure they are open in the firewall and/or antivirus software, restart the license server and try again.

This happens typically in networks with tight security settings. Occasionally antivirus software can trigger this problem.

Q: I cannot check out a token even though there should be more available.

Most likely there are processes/users who checked out a license but never returned it. The lmgrd.log log file on the license server will contain the history of license ckeckouts and checkins which may be used to identify the culprit.

## 10.3 Local file issues¶

Q: The Optimization Toolbox for Matlab or Rmosek says license has expired although I downloaded a new one.

After you put the license file in the right place restart Matlab or R. It caches the license. If that doesn’t help MOSEK probably uses another license path than you first thought. See next question.

Q: MOSEK says there is no license file or that it expired.

If you are sure that your license file is valid and in the right place, then it is possible that your system is configured to expect the license file elsewhere than you thought. Search for the mosek.lic file on the disk and see if there is one in another location. Remove any old expired licenses found.

Go through the error or diagnostic message you received from MOSEK and look for lines such as:

License path: /home/someplace/mosek/mosek.lic


or:

License cannot be located. The default search path is ':/home/someplace/mosek/mosek.lic:'


This is the actual location where this instance of MOSEK was trying to locate the license. If it does not correspond to your expectations then go through the setup again or check that this location contains the correct file.

## 10.4 Need more help¶

Q: I tried all of the above but it doesn’t help.

Send us an email and attach as much as possible of the following data:

• description of the problem,
• the token server log file lmgrd.log or its part relevant to the issue (for floating licenses),
• the exact error message reported by the MOSEK client, or the output from mosekdiag, mosektestlic, mosek -f or other relevant diagnostic tool.