HTML README for Fix Central packages

IBM Platform LSF 9.1.1 Fix Pack 7 (402751) Readme File

Abstract

LSF Version 9.1.1 Fix Pack 7. 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 24 December 2015 and 25 April 2016. For detailed descriptions of the issues and solutions in this Fix Pack, refer to the LSF 9.1.1 Fix Pack 7 Fixed Bugs List (lsf9.1.1.7_fixed_bugs.pdf can be downloaded from Fix central via fix ID lsf-9.1.1.7-spk-2016-Apr-build402751).

Description

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

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

ID

Fixed Date

Description

P101675

2016/04/12

When the LIM daemon starts up, the master elim may report the following error message in the log file:
readLoadUpdateFromSubElim: Protocol error: loadCnt cannot be read from elim.
This error message is a false alarm. The root cause is that some elims may start, but quickly exit with ELIM_ABORT_VALUE. A race condition might occur where the master elim reads the exited child elim process before receiving the SIGCHLD signal of the child. In this case the read fails and the master elim displays this error message.

P101645

2016/04/12

If the user name in the between-host user account mapping file is enclosed by double quotes, LSF cannot correctly retrieve the user name from the file. This means that jobs submitted by the user are always pending.

P101623

2016/03/08

This fix prevents sbatchd from entering into a dead loop where it creates "select failed. Bad file descriptor" error messages.

P101621

2016/02/18

If sbatchd is restarted, any jobs using pre-exec that were running on the machine before the restart are no longer killed when the jobs' wall clock times expire.

P101599

2016/02/19

After configuring both EGROUP_UPDATE_INTERVAL and FAIRSHARE in a cluster, a fairshare update may cause an mbatchd core dump.

P101580

2016/02/24

If LSF has PREEMPT_JOBTYPE=EXCLUSIVE configured in the lsb.params file, at least one LSF job queue is an exclusive queue (that is, the EXCLUSIVE parameter is enabled for at least one queue), and there are any queues that can preempt or be preempted by this exclusive queue, then:
If a job is dispatched to this exclusive queue, the job may be dispatched to hosts that have running jobs and does not have a defined maximum job count.

P101577

2016/02/02

LSF does not display esub error messages when using the ls_rexecve() or ls_rexecv() APIs to run jobs.

P101503

2016/01/12

When a job's pre-execution script fails repeatedly, the run time shown in the stream file and in the bhist output are different.

80996

2016/01/29

When NEWJOB_REFRESH=Y the runlimit displayed is multiplied by the submission host CPU Factor.

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

Readme file for: IBM® Platform LSF

Product/Component Release: 9.1.1

Update Name: Fix 402751

Fix ID: lsf-9.1.1.7-spk-2016-Apr-build402751

Publication date: 12 May 2016

Last modified date: 12 May 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

P101675, P101645, P101623, P101621, P101599, P101580, P101577, P101503, 80996(NO APAR)

2. Download Location

Download Fix 402751 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 7 include:
LSF/melim
LSF/sbatchd
LSF/bsub
LSF/mbschd
LSF/schmod_preemption.so
LSF/mesub
LSF/mbatchd
LSF/bhist

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

Files affected by the new issues added in LSF Version 9.1.1 Fix Pack 7 include:
melim
sbatchd
bsub
mbschd
schmod_preemption.so
mesub
mbatchd
bhist

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
P101675	2016/04/12	When the LIM daemon starts up, the master elim may report the following error message in the log file: readLoadUpdateFromSubElim: Protocol error: loadCnt cannot be read from elim. This error message is a false alarm. The root cause is that some elims may start, but quickly exit with ELIM_ABORT_VALUE. A race condition might occur where the master elim reads the exited child elim process before receiving the SIGCHLD signal of the child. In this case the read fails and the master elim displays this error message.
P101645	2016/04/12	If the user name in the between-host user account mapping file is enclosed by double quotes, LSF cannot correctly retrieve the user name from the file. This means that jobs submitted by the user are always pending.
P101623	2016/03/08	This fix prevents sbatchd from entering into a dead loop where it creates "select failed. Bad file descriptor" error messages.
P101621	2016/02/18	If sbatchd is restarted, any jobs using pre-exec that were running on the machine before the restart are no longer killed when the jobs' wall clock times expire.
P101599	2016/02/19	After configuring both EGROUP_UPDATE_INTERVAL and FAIRSHARE in a cluster, a fairshare update may cause an mbatchd core dump.
P101580	2016/02/24	If LSF has PREEMPT_JOBTYPE=EXCLUSIVE configured in the lsb.params file, at least one LSF job queue is an exclusive queue (that is, the EXCLUSIVE parameter is enabled for at least one queue), and there are any queues that can preempt or be preempted by this exclusive queue, then: If a job is dispatched to this exclusive queue, the job may be dispatched to hosts that have running jobs and does not have a defined maximum job count.
P101577	2016/02/02	LSF does not display esub error messages when using the ls_rexecve() or ls_rexecv() APIs to run jobs.
P101503	2016/01/12	When a job's pre-execution script fails repeatedly, the run time shown in the stream file and in the bhist output are different.
80996	2016/01/29	When NEWJOB_REFRESH=Y the runlimit displayed is multiplied by the submission host CPU Factor.