FAQs

Why does the license not become available after I suspend the job that is using it?

  1. You submit a job to a license project that requires a specific license.

  2. You submit a second higher priority job that requires this license. No licenses are free.

  3. You suspend the first job to release the license it is using.

  4. The second job starts but fails because it cannot obtain the required license.

Solution: Suspend the job with bkill -s TSTP. This sends a SIGTSTP signal to the job, suspends the job, and releases the license that the job was using.

Why does lsf not recognize the names of features I configured in lsf.licensescheduler?

  1. You installed LSF License Scheduler.

  2. You configured new license features in the License Scheduler configuration file, lsf.licensescheduler.

  3. You reconfigured the License Scheduler daemon (bld) with bladmin reconfig all.

  4. You submit a job that requires the new feature you configured. For example:

    bsub -R "rusage[feature_name=1]" ...

  5. LSF does not recognize the feature name and you receive the following error:

    Bad resource requirement syntax. Job not submitted.

Solution: Run badmin reconfig to reconfigure mbatchd if you have added new features to lsf.licensescheduler. You must reconfigure mbatchd after you install License Scheduler and configure your license features. You must also reconfigure mbatchd each time you add a new license feature. LSF treats license tokens as LSF resources, and mbatchd must be reconfigured to recognize the resources if they change.

Note:

If you increase the number of tokens for a license feature, you do not need to reconfigure mbatchd. You only reconfigure mbatchd if you add a new license feature.

Why does blhosts -s display license tokens after you shut down the LSF License Scheduler daemon (bld)?

The License Scheduler daemon (bld) keeps a local backup database of all the license tokens in LSB_SHAREDIR/cluster_name/log_dir/lsb.tokens. This backup file provides redundancy for License Scheduler when it runs in a WAN configuration.

mbatchd can still read this file after you shut down bld.

If you do not want mbatchd to recognize the license token names, you can remove the backup file and reconfigure mbatchd by running badmin reconfig.

Why does my job submission fail when the license feature name includes numbers?

Normally, license token names should be the same as the FLEXnet feature names, as they represent the same license. However, LSF does not support names that start with a number, or names containing a dash or hyphen character (-), which may be used in the FLEXnet feature name.

Solution: Set both NAME and FLEX_NAME in the Features section of lsf.licensescheduler. FLEX_NAME is the actual FLEXnet feature name, and NAME is an arbitrary license token name you choose that does not start with a number or contain a dash.

Example:

Begin Feature 
FLEX_NAME=201-AppZ 
NAME=AppZ201 
DISTRIBUTION=LanServer1(Lp1 1 Lp2 1) 
End Feature

I see the following error in the bld.log: server_name file: globInit(): cannot initialize the listening TCP - 2 channel Address already in use.

  1. You edit the LSF_CONFDIR/lsf.conf file to include a list of hosts for the LSF_LIC_SCHED_HOSTS parameter.

  2. You run lsadmin reconfig to reconfigure the LIM.

  3. You use ps -efl | grep bld to make sure that bld is running on the candidate hosts, but find that bld is not running on the server_name host.

  4. You view the bld.log.server_name file and see the following error message:

    globInit(): cannot initialize the listening TCP -2 channel Address already in use

Explanation: Normally, the LSF LIM daemon starts the License Scheduler daemon (bld) automatically on startup. If you already started bld manually, the LSF LIM daemon still tries to start bld, but the port used by bld is already open.

Solution: Run bladmin shutdown to shut down License Scheduler. The LSF LIM starts bld automatically. Run badmin reconfig to reconfigure mbatchd.

Why does the job pending reason show the wrong license feature?

  1. You have two License Scheduler resources: feat2 and feat3, both with value 10.

  2. Submit a job with rusage[feat2=11:feat3=1]"

  3. bjobs pending reason shows (feat3) not satisfied when it should be (feat2) not satisfied.

Reason: When scheduling a job that requests license resources, mbatchd sends a request to bld to reserve the requested licenses for the job. This will take some time. During this time, the requested license resources are not available and mbschd sets the pending reason.

Solution: Wait a few moments for mbatchd to get the license resource and passed it to mbschd, and run bjobs again to see the correct pending reason.

I see the following error when running LSF License Scheduler commands: Network I/O error with the License Scheduler server

  1. You are running LSF License Scheduler on a Windows client.

  2. You run an LSF License Scheduler command and see the following error message:

    Network I/O error with the License Scheduler Server.

  3. You see the following message in the mbatchd log file:

    callglb(): cc -1Failed in an LSF library call: Failed in sending/receiving a message: error 0: The operation completed successfully

Reason: The master host does not recognise your Windows client when you try to issue LSF License Scheduler commands to bld because you did not specify your Windows client host name and IP address in the /etc/hosts file on the master host.

Solution: Add your Windows client host name and IP address to the /etc/hosts file on the master host.