HP XC System Software Release Notes for Version 3.0

5.7.1 Required Task: Restart the LSF LIM Daemon
This release note applies to systems where LSF-HPC with SLURM has been installed and
configured; skip this task if your system is installed and configured with standard LSF.
The LSF Load Information Manager (LIM) daemon must be restarted so that it can be properly
licensed for all compute node processors. At this point, LSF is only licensed for a subset of the
available compute node processors.
Follow this procedure to start the LSF LIM daemon:
1. As the root user, determine the node on which the LSF daemons are running:
# controllsf show current
2. Log in to the node on which the LSF daemons are running (unless it is the local node) and
restart the LIM:
# lsadmin limrestart
3. Confirm that LSF is fully licensed for all of the compute nodes that have been booted up
and are running:
# sinfo --long --Node --exact --partition=lsf
This command displays all of the compute nodes in the lsf partition and the number of
CPUs per node. Total the number of CPUs and make sure that the sum matches the ncpus
value in the output of the lshosts command in the next step.
4. Ensure that the total number of compute processors matches the ncpus value in the output
of the lshosts command:
# lshosts
If the lshosts command displays the number of ncpus that is less than the total number
of CPUs computed from the sinfo output, restart the LIM one more time.
5.8 OVP Might Return LSF Errors
The Operation Verification Program (OVP) might return LSF errors if it is run too soon after the
spconfig utility is run.
This can occur because the spconfig utility adjusts the default two processor per node setting
to more accurately reflect the actual number of processors on each node. Thus, if the total processor
count changes as a result of running the spconfig utility, LSF may not have updated itself by
the time the OVP runs.
The OVP has two tests that confirm that SLURM and LSF are synchronized with respect to the
total number of processors, and these tests could fail.
5.9 OVP Reports Benign Nagios Errors
The OVP may return the following Nagios errors. These errors are benign and you can ignore
them.
.
.
.
Verify nagios:
Testing configuration ...
Running basic sanity check on the Nagios configuration file.
Starting the command:
/opt/hptc/bin/nagios -v
/opt/hptc/nagios/etc/nagios_local.cfg
Here is the output from the command:
Nagios 2.0b6
5.8 OVP Might Return LSF Errors 35