gLite > gLite 3.1 > glite-MPI_utils > Update to glite-MPI_utils 3.1.11-0  



gLite 3.1

glite-MPI_utils - Update to version 3.1.11-0

Date 16.03.2010
Priority Normal


glite-AMGA_oracle, glite-AMGA_postgres, glite-BDII, glite-CONDOR_utils, glite-CREAM, glite-FTA_oracle, glite-FTM, glite-FTS_oracle, glite-HYDRA_mysql, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-LSF_utils, glite-MON, glite-MPI_utils, glite-PX, glite-SCAS, glite-SE_dcache_admin_gdbm, glite-SE_dcache_admin_postgres, glite-SE_dcache_info, glite-SE_dcache_pool, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-SGE_utils, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

The LB patch introduces a new version of glite-version.

glite-MPI_utils, glite-TORQUE_client, glite-TORQUE_server, glite-TORQUE_utils

New version of MPI_utils

This release of the glite-MPI_utils fixes a long known dependency issue with an incompatible torque library provided by the torque RPM.

There have been several updates to glite-yaim-mpi:

  • The YAIM configuration will now look in the YAIM "services" configuration directory for configuration details.
  • There have been minor changes to the YAIM MPI configuration scripts which fix some observed problems relating to variable assignment.

The default MPI installation is now OPENMPI, which is provided by the Scientific Linux distribution.

Support for MPICH1 and MPICH2 has been discontinued on SL4. MPICH2 is available for SL5.

The MPI-START scripts have been improved to detect if the user is compiling code under 64 bit or 32 bit versions of mpicc.

The supplied OPENMPI packages are compiled with support for Infiniband. If your site does not support infiniband, openmpi will output warnings. To fix this problem at your site, please see: The affected files are:
SL4: /usr/lib/openmpi/1.2.8-gcc/etc/openmpi-mca-params.conf SL5 /usr/lib64/openmpi/1.2.7-gcc/etc/openmpi-mca-params.conf

The vendor provided version of OpenMPI is not compiled with Torque support. This affects sites not using shared homes and who are not using ssh to distribute job related files between worker nodes.

In order to allow the site to compile and install their own custom MPI rpms, this metapackage removes the explicit requirement of any devel and lib packages. Further details on compiling OpenMPI with torque support can be found under:

There is a bug #62612 ( ) which hopefully will be fixed later.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #35770 Wrong parsing of the LB events which contains the string ending with '' in field DG.USERTAG.VALUE
 #41007 Missing Dependency by package mpiexec
 #48163 interlogger files may grow indefinitely
 #48875 [ yaim-mpi ] yaim doesn't configure properly MPI environment on WNs|CE
 #52555 obsolete version of i2g-mpi-start package in glite production repositories
 #52560 [ yaim-mpi ] mpirun: <user's executable>: command not found
 #54557 OpenMPI should be added to glite-MPI_utils
 #54558 mpich should be upgraded to mpich2 in glite-MPI_utils
 #55482 LB server version not published correctly

Updated rpms

Name Version Full RPM name Description
glite-MPI_utils 3.1.11-0 glite-MPI_utils-3.1.11-0.i386.rpm gLite metapackage (glite-MPI_utils)
glite-yaim-core 4.0.11-2 glite-yaim-core-4.0.11-2.noarch.rpm YAIM core package
glite-yaim-mpi 1.1.6-1.slc4 glite-yaim-mpi-1.1.6-1.slc4.noarch.rpm yaim module for MPI configuration
i2g-mpi-start 0.0.61-1 i2g-mpi-start-0.0.61-1.noarch.rpm A generic startup mechanism for different MPI installation in a cluster/grid.
mpiexec 0.83-2.el4 mpiexec-0.83-2.el4.i386.rpm MPI job launcher that uses the PBS task interface directly
torque-client 2.3.6-1cri.slc4 torque-client-2.3.6-1cri.slc4.i386.rpm client part of Torque
torque 2.3.6-1cri.slc4 torque-2.3.6-1cri.slc4.i386.rpm Tera-scale Open-source Resource and QUEue manager

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)