HTML README for Fix Central packages

IBM Platform LSF 9.1.1 Fix Pack 6 (381395) Readme File

Abstract

LSF Version 9.1.1 Fix Pack 6. This Fix Pack includes all fixed issues and solutions included in previous LSF Version 9.1.1 Fix Packs and addresses new issues fixed between 25 August 2015 and 24 December 2015. For detailed descriptions of the issues and solutions in this Fix Pack, refer to the LSF 9.1.1 Fix Pack 6 Fixed Bugs List (lsf9.1.1.6_fixed_bugs.pdf can be downloaded from Fix central via fix ID lsf-9.1.1.6-spk-2015-Dec-build381395).

Description

Readme documentation for IBM Platform LSF 9.1.1 Fix Pack 6 (381395) including installation-related instructions, prerequisites and co-requisites, and list of fixes.

The new issues addressed in LSF Version 9.1.1 Fix Pack 6:

ID

Fixed Date

Description

P101512

2015/12/14

Memory leaks when querying job messages in the lsb_readjobinfo_cond API and the bjobs command.

P101439

2015/12/2

After LSF_DAEMON_WRAP is enabled, the root sbatchd hangs if writing more data to the socket through esub than is defined in /proc/sys/net/core/vmem_max or /proc/sys/net/core/wmem_default on the execution host.

P101462

2015/12/2

After the PRE_EXEC or POST_EXEC process exits, the job remains running and does not exit.

P101491

2015/12/1

When the IP address of an LSF floating client changes, the "bsub -K" command hangs on the floating client while waiting for a response from mbatchd. mbatchd cannot connect to the floating client because it saved the wrong IP address. There are no error messages for this issue in the mbatchd log.

P101440

2015/11/30

When a job is finished, that job's runRusage.mem and runRusage.swap information read from the lsb_readjobinfo API are incorrectly set to the maximum value. This fix updates the lsb_readjobinfo API to set a job's runRusage.mem and runRusage.swap information to 0 when the job is finished.

P101443

2015/11/26

If the parent job is killed while in pend or suspend status after running brequeue, the child job that depended on this job cannot run due to the condition "ended()".

66209

2015/11/19

Improvements to mbatchd log messages.

P101447

2015/11/12

When mbatchd automatically deletes the oldest lsb.stream.utc or lsb.status.utc file, mbatchd may core dump. When the size of the lsb.status file reaches the value of MAX_EVENT_STREAM_SIZE (defined in lsb.params), mbatchd might incorrectly give the error message "mergeStatusFile: checkStatusFile(pathTo/stream/lsb.status) failed: No such file or directory" in the mbatchd log.

P101383

2015/9/30

mbatchd fails to send job status information to bld when the job command length exceeds 4K. This causes blstat to incorrectly report that license tokens are used by non-LSF jobs, when they actually are being used by LSF jobs.

P101329

2015/9/18

When the user does not have permission to run lsgrun, a warning message is displayed but the job exits with return code 0, indicating success.

The fixed issues and solutions included in previous LSF Version 9.1.1 Fix Packs can be found in lsf9.1.1.6_fixed_bugs.pdf.

Readme file for: IBM® Platform LSF

Product/Component Release: 9.1.1

Update Name: Fix 381395

Fix ID: lsf-9.1.1.6-spk-2015-Dec-build381395

Publication date: 18 January 2016

Last modified date: 18 January 2016

Contents:

1. List of fixes

2. Download location

3. Products 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

P101329, P101383, P101439, P101440, P101443, P101447, P101462, P101491, P101512, 66209(NO APAR)

2. Download Location

Download Fix 381395 from the following location: http://www.ibm.com/eserver/support/fixes/

3. Products or components affected

Components affected by the new issues addressed in LSF Version 9.1.1 Fix Pack 6 include:
LSF/mbatchd
LSF/liblsbstream.so
LSF/daemons.wrap
LSF/res
LSF/sbatchd
LSF/bjobs
LSF/lsgrun
LSF/lsbatch.h
LSF/lsf.h
LSF/libbat.a
LSF/libbat.so
LSF/liblsf.a
LSF/liblsf.so

4. System requirements

Linux2.6-glibc2.3-x86_64

5. Installation and configuration

5.1 Before installation

(LSF_TOP=Full path to the top-level installation directory of LSF.)

1) Log on to the LSF master host as root

2) Set your environment:

- For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf

- For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf

5.2 Installation steps

1) Go to the patch install directory: cd $LSF_ENVDIR/../9.1/install/

2) Copy the patch file to the install directory $LSF_ENVDIR/../9.1/install/

3) Run
badmin hclose all
badmin qinact all

4) Run patchinstall: ./patchinstall <patch>

5.3 After installation

1) Run
badmin hshutdown all
lsadmin resshutdown all
lsadmin limshutdown all

2) Run
lsadmin limstartup all
lsadmin resstartup all
badmin hstartup all

3) Run
badmin hopen all
badmin qact all

5.4 Uninstallation

To roll back a patch:

1) Log on to the LSF master host as root

2) Set your environment:

- For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf

- For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf

3) Run
badmin hclose all
badmin qinact all

4) Run ./patchinstall -r <patch>

5) Run
badmin hshutdown all
lsadmin resshutdown all
lsadmin limshutdown all

6) Run
lsadmin limstartup all
lsadmin resstartup all
badmin hstartup all

7) Run
badmin hopen all
badmin qact all

6. List of files in package

mbatchd
sbatchd
lim
pim
mbschd
res
nios
lsadmin
lsmake
lsmakerm
blaunch
bhist
bjobs
bkill
bpeek
bsub
bmod
mesub
esub.poe
daemons.wrap
schmod_parallel.so
schmod_reserve.so
schmod_mc.so
schmod_default.so
schmod_limit.so
lsbatch.h
lsf.h
libbat.a
libbat.so
liblsf.a
liblsf.so
lib2vemkd.so
libvem.so
liblsbstream.so
permapi.so
badmin
schmod_preemption.so
elim.hpc
lspasswd
pam
lsgrun

7. Product notifications

To receive information about product solution and patch 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

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.

ID	Fixed Date	Description
P101512	2015/12/14	Memory leaks when querying job messages in the lsb_readjobinfo_cond API and the bjobs command.
P101439	2015/12/2	After LSF_DAEMON_WRAP is enabled, the root sbatchd hangs if writing more data to the socket through esub than is defined in /proc/sys/net/core/vmem_max or /proc/sys/net/core/wmem_default on the execution host.
P101462	2015/12/2	After the PRE_EXEC or POST_EXEC process exits, the job remains running and does not exit.
P101491	2015/12/1	When the IP address of an LSF floating client changes, the "bsub -K" command hangs on the floating client while waiting for a response from mbatchd. mbatchd cannot connect to the floating client because it saved the wrong IP address. There are no error messages for this issue in the mbatchd log.
P101440	2015/11/30	When a job is finished, that job's runRusage.mem and runRusage.swap information read from the lsb_readjobinfo API are incorrectly set to the maximum value. This fix updates the lsb_readjobinfo API to set a job's runRusage.mem and runRusage.swap information to 0 when the job is finished.
P101443	2015/11/26	If the parent job is killed while in pend or suspend status after running brequeue, the child job that depended on this job cannot run due to the condition "ended()".
66209	2015/11/19	Improvements to mbatchd log messages.
P101447	2015/11/12	When mbatchd automatically deletes the oldest lsb.stream.utc or lsb.status.utc file, mbatchd may core dump. When the size of the lsb.status file reaches the value of MAX_EVENT_STREAM_SIZE (defined in lsb.params), mbatchd might incorrectly give the error message "mergeStatusFile: checkStatusFile(pathTo/stream/lsb.status) failed: No such file or directory" in the mbatchd log.
P101383	2015/9/30	mbatchd fails to send job status information to bld when the job command length exceeds 4K. This causes blstat to incorrectly report that license tokens are used by non-LSF jobs, when they actually are being used by LSF jobs.
P101329	2015/9/18	When the user does not have permission to run lsgrun, a warning message is displayed but the job exits with return code 0, indicating success.