MATLAB Installation Guide for Unix

Resolving Other MATLAB Startup Problems

The following lists some other MATLAB start up problems with possible solutions.

Changes to License File Unread by License Manager

If you change the License File, you must restart the license manager using $MATLAB/etc/lmstart.

The lmstart script calls the lmdown script to shut down the license manager daemon. Sometimes the lmdown script does not succeed at its task. An effective way to shut down the license manager daemons is to use the UNIX ps command to check for running processes and terminate them manually using the UNIX kill command. See Checking the License Manager Daemons for more information.

MATLAB Can't Find LM_LICENSE_FILE

If MATLAB is installed on a file server in /usr/local/matlab6p5, the install script defines $MATLAB as /usr/local/matlab6p5 in the file .matlab6rc.sh. If MATLAB is automounted on other workstations in directories other than
/usr/local/matlab6p5, MATLAB will fail at startup because it cannot find LM_LICENSE_FILE. The LM_LICENSE_FILE is determined by $MATLAB.

Edit $MATLAB/bin/.matlab6rc.sh and comment out the line that defines the variable MATLAB. If this line is not found in.matlab6rc.sh, $MATLAB is determined automatically when MATLAB is started.

License Key Unusable on Crashed Node

When the node on which MATLAB is running crashes, the license key should be released after about 2 hours. If the key is never released, use $MATLAB/etc/lmremove to release it manually. This script allows you to remove a single user's license for a specified feature and return the license to the pool of available licenses without having to restart the license manager.

Checking the Network Connection

Overriding the Default Choice of BLAS Library