Readme file for IBM® Spectrum LSF 10.1 Fix 602067
Abstract
P105159. This fix enhances the lsfd service to 1. prevent user jobs from being killed if LSF_DAEMON_WRAP is enabled when it stops lsfd service, and 2. Restricts to use PIDfiles to get the lim, res, and sbatchd daemon process IDs.
Description
Readme documentation for IBM Spectrum LSF 10.1 Fix 602067 including installation-related instructions, prerequisites and co-requisites, and list of fixes.
This fix addresses the following issue:
1. If the LSF_DAEMON_WRAP parameter is enabled in the lsf.conf configuration file, user jobs are killed when the lsfd service is stopped.
2. Using the ps -ef command to get LSF daemons to processes IDs and kill them is not safe. LSF should only use PIDFiles to get the lim, res, and sbatchd daemon process IDs.
Readme file for: IBM® Spectrum LSF
Product or component release: 10.1
Update name: Fix 602067
Fix ID: LSF-10.1-build602067
Publication date: 23 June 2024
Contents
1. List of fixes
2. Download location
3. Product or components affected
4. System requirements
5. Installation and configuration
6. List of files
7. Product notifications
8. Copyright and trademark information
1. List of fixes
P105159
2. Download locations
Download Fix 602067 from the following location: https://www.ibm.com/support/fixcentral
3. Product or components affected
Affected product or components include:
lim
lsload
lshosts
sbatchd
res
install/hostsetup
install/instlib/startup.svr4
4. System requirements
linux2.6-glibc2.3-x86_64
linux3.10-glibc2.17-x86_64
linux3.10-glibc2.17-ppc64le
linux3.12-glibc2.17-armv8
5. Installation and configuration
Before you install
LSF_TOP is the full path to the top-level installation directory of LSF.
1. Before you apply this fix, ensure that you installed LSF 10.1 Fix Pack 12 or later. You can download LSF 10.1 Fix Pack 12 from https://www.ibm.com/support/fixcentral. Search for build600488. Contact IBM LSF Support if you have any questions or problems with installing Fix Pack 12.
2.
Starting in LSF 10.1
Fix Pack 13, the default values of the following three GPU parameters are
changed to:
LSF_GPU_AUTOCONFIG=Y
LSB_GPU_NEW_SYNTAX=extend
LSF_GPU_RESOURCE_IGNORE=Y
If you have Fix Pack 13
installed, and these GPU parameters are not configured in the lsf.conf
configuration file, LSF will take the default values. The parameters already
configured in the lsf.conf file will not be affected.
If you want to keep the former
GPU behavior, and if any of the three parameters are missing in the lsf.conf
configuration file, you must explicitly configure the following default
settings that are defined in Fix Pack 12 or earlier:
LSF_GPU_AUTOCONFIG=N
LSB_GPU_NEW_SYNTAX=N
LSF_GPU_RESOURCE_IGNORE=N
Installation steps
1. Log on to each LSF server hosts as the root user and set your environment:
-For csh or tcsh: % source
LSF_TOP/conf/cshrc.lsf
-For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
2. Stop LSF on each LSF server host. Stop
your previous version of lsfd.service if it was deployed, by running systemctl stop lsfd. Or run lsf_daemons stop, if lsfd.service is not deployed. Make sure no LSF daemons are running.
3. Disable the previous lsfd.service if it was deployed, by running systemctl disable lsfd lsfd-lim lsfd-res lsfd-sbd.
4. Log on to the LSF management host as the root user and set your environment:
-For csh or tcsh: % source
LSF_TOP/conf/cshrc.lsf
-For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
5. Go to the install directory: cd $LSF_ENVDIR/../10.1/install/
6. Copy the fix file to the install directory: $LSF_ENVDIR/../10.1/install/
7.
Run patchinstall: ./patchinstall
<fix>.
8.
Back up the <LSF_SERVERDIR>/lsf_daemons file.
9.
Copy the
LSF_TOP/10.1/install/instlib/startup.svr4
script to
<LSF_SERVERDIR>/lsf_daemons.
10. Modify the <LSF_SERVERDIR>/lsf_daemons file, by changing the LSF_CONF=@LSF_CONF@ line to LSF_CONF=<LSF_TOP>/conf/lsf.conf.
After you install
1. Log on to each LSF server hosts as the root user and set your environment:
-For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf
-For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
2. If you want to deploy lsfd.service, follow steps 4 to 6 to deploy the new lsfd.service and start it.
3.
If you don’t want to
deploy lsfd.service, directly start LSF on each host
and skip steps 4 to 6.
4. Refresh the new lsfd.service file by running:
hostsetup –-top=<LSF_TOP>
--boot=y
Note: If this is a dynamic host, add the –-dynamic option.
5. Load the new lsfd.service by running systemctl daemon-reload.
6. Start the new lsfd.service by running systemctl start lsfd.
Uninstallation
1. Log on to each LSF server host as the root user and set your environment:
-For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf
-For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
2. Stop the lsfd.service by running systemctl stop lsfd.
3. Disable the lsfd.service by running systemctl disable lsfd
4. Log on to the LSF management host as the root user and set your environment:
-For csh or tcsh: % source
LSF_TOP/conf/cshrc.lsf
-For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
5. Go to the install directory: cd $LSF_ENVDIR/../10.1/install/
6. Run ./patchinstall -r <fix>
7. Restore your backup <LSF_SERVERDIR>/lsf_daemons file.
8. If you
want to recover your old lsfd.service, follow steps 10 to 11 to recover the
old lsfd.service and start it.
9.
If you have no old lsfd.service, directly start LSF on each host and skip steps
10 to 11.
10. Log on to each LSF server hosts as
the root user and
recover your old lsfd.service on each server hosts by running hostsetup –-top=<LSF_TOP> --boot=y.
Note: If this is a dynamic host,
add the –-dynamic
option.
11. Start the old lsfd.service by running systemctl start lsfd.
6. List of files
The following components in all Linux and UNIX packages:
lim
lsload
lshosts
sbatchd
res
install/hostsetup
install/instlib/startup.svr4
7. Product Notifications
To receive information about product solution and fix updates automatically, subscribe to product notifications on the My notifications page (www.ibm.com/support/mynotifications) on the IBM Support website (support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes.
8. Copyright and Trademark Information
©Copyright IBM Corporation 2024
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM®, the IBM logo, and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.