gLite > gLite 3.2 > glite-LFC_mysql > Update to glite-LFC_mysql 3.2.1-0  



gLite 3.2

glite-LFC_mysql - Update to version 3.2.1-0

Date 27.07.2009
Priority Normal


glite-BDII, glite-DPM_mysql, glite-LFC_mysql glite-TORQUE_client, glite-UI, glite-WN
New version of yaim core
  • The creation of users specifying a home directory wasn't working. This is fixed now.
  • GLOBUS_TCP_PORT_RANGE is not defined for the WN and it's properly defined for the TAR UI.
  • MYPROXY_TCP_PORT_RANGE is not defined any more.
  • YAIM checks whether fetch-crl is installed and fails otherwise.
  • groups.d structure is now available for all the node types.
glite-LFC_mysql, glite-UI, glite-WN
Introduction of the LFC mysql

This update introduces the glite-LFC_mysql node type for SL5 x86_64

Please also have a look at the list of known issues.

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

Fixed bugs

Number Description
 #40208 [ YAIM ] LCG_GFAL_INFOSYS variable is defined in two places
 #44820 [ yaim-core ] The lcg-cp parallel data transfer failed on UI_TAR installed gLite-UI 3.1 nodes
 #45418 [ yaim-core ] Check exists if -r option is used
 #46194 [ yaim-core ] YAIM config_crl should check for /usr/sbin/fetch-crl
 #48309 Use a VDT version which includes fix for globus gsi threading bug (globus bug #6510)
 #48452 [ yaim-core ] WN should not define GLOBUS_TCP_PORT_RANGE
 #48932 [ yaim-core] output is not helpful when a conf target is wrongly stated
 #48991 [ yaim-core ] needed to change config_edgusers
 #49017 [ yaim-core ] configuration changes for new trustmanager and util-java
 #49575 [ yaim-core ] MYPROXY_TCP_PORT_RANGE can be deleted
 #50735 [ yaim-core ] queue_GROUP_ENABLE fails for "/vo" FQAN

Updated rpms

Name Version Full RPM name Description
LFC-client 1.7.2-5sec.sl5 LFC-client-1.7.2-5sec.sl5.x86_64.rpm Client side libraries for the LFC
LFC-interfaces2 1.7.2-5sec.sl5 LFC-interfaces2-1.7.2-5sec.sl5.x86_64.rpm LCG File Catalog Interfaces
LFC-interfaces 1.7.2-5sec.sl5 LFC-interfaces-1.7.2-5sec.sl5.x86_64.rpm LCG File Catalog Interfaces
LFC-server-mysql 1.7.2-5sec.sl5 LFC-server-mysql-1.7.2-5sec.sl5.x86_64.rpm LFC Server for a MySQL database backend
bdii 5.0.0-22 bdii-5.0.0-22.noarch.rpm bdii
edg-mkgridmap 3.0.0-1 edg-mkgridmap-3.0.0-1.noarch.rpm A tool to build the grid-mapfile
fetch-crl 2.7.0-2 fetch-crl-2.7.0-2.noarch.rpm Tool for periodic retrieval of Certificate Revocation Lists fetch-crl
glite-LFC_mysql 3.2.1-0 glite-LFC_mysql-3.2.1-0.x86_64.rpm gLite metapackage (glite-LFC_mysql)
glite-info-generic 2.0.2-3 glite-info-generic-2.0.2-3.noarch.rpm glite-info-generic
glite-info-provider-release 1.0.0-5 glite-info-provider-release-1.0.0-5.noarch.rpm glite-info-provider-release
glite-info-templates 1.0.0-8 glite-info-templates-1.0.0-8.noarch.rpm glite-info-templates
glite-security-voms-api-cpp 1.8.12-1.sl5 glite-security-voms-api-cpp-1.8.12-1.sl5.x86_64.rpm v.
glite-security-voms-api 1.8.12-1.sl5 glite-security-voms-api-1.8.12-1.sl5.x86_64.rpm v.
glite-version 3.2.0-0.sl5 glite-version-3.2.0-0.sl5.x86_64.rpm glite-version
glite-yaim-core 4.0.8-7 glite-yaim-core-4.0.8-7.noarch.rpm YAIM core package
glite-yaim-lfc 4.0.3-1 glite-yaim-lfc-4.0.3-1.noarch.rpm glite-yaim-lfc module configures 3.0 LFC.
glue-schema 1.3.0-5 glue-schema-1.3.0-5.noarch.rpm glue-schema
gpt 3.2autotools2004_NMI_9.0_x86_64_rhap_5-1 gpt-3.2autotools2004_NMI_9.0_x86_64_rhap_5-1.x86_64.rpm The Grid Packaging Toolkit (GPT) gpt
lcg-dm-common 1.7.2-5sec.sl5 lcg-dm-common-1.7.2-5sec.sl5.x86_64.rpm LCG Data Management common libraries and man pages.
mysql-server 5.0.45-7.el5 mysql-server-5.0.45-7.el5.x86_64.rpm The MySQL server and related files.

The RPMs can be installed using yum:

Service reconfiguration after update

Since this is the first LFC mysql release in SL5, it needs to be configured after the installation.

Service restart after update

Since this is the first LFC mysql release in SL5, it will be started automatically after being configured. If YAIM is not used, then start it manually.

How to apply the fix

  1. Install the RPMs (see above)
  2. Run the configuration
  3. Start the service manually, if YAIM is not used