Platform LSF Administration Guide Version 6.2

Reconfiguring Your Cluster
Administering Platform LSF
90
% badmin reconfig
Checking configuration files ...
No errors found.
Do you want to reconfigure? [y/n] y
Reconfiguration initiated
The badmin reconfig command checks for configuration errors.
If no fatal errors are found, you are asked to confirm reconfiguration. If fatal errors
are found, reconfiguration is aborted.
Reconfiguring the cluster by restarting mbatchd
Run badmin mbdrestart to restart mbatchd:
% badmin mbdrestart
Checking configuration files ...
No errors found.
Do you want to restart? [y/n]
y
MBD restart initiated
The badmin mbdrestart command checks for configuration errors.
If no fatal errors are found, you are asked to confirm
mbatchd restart. If fatal errors
are found, the command exits without taking any action.
If the lsb.events file is large, or many jobs are running, restarting mbatchd can
take some time. In addition, mbatchd is not available to service requests while it is
restarted.
Viewing configuration errors
To view configuration errors, run the following commands:
◆ % lsadmin ckconfig -v
◆ % badmin ckconfig -v
This reports all errors to your terminal.
How reconfiguring the cluster affects licenses
If the license server goes down, LSF can continue to operate for a period of time until
it attempts to renew licenses.
Reconfiguring causes LSF to renew licenses. If no license server is available, LSF will not
reconfigure the system because the system would lose all its licenses and stop working.
If you have multiple license servers, reconfiguration will proceed as long as LSF can
contact at least one license server. In this case, LSF will still lose the licenses on servers
that are down, so LSF may have fewer licenses available after reconfiguration.