gLite > gLite 3.2 > glite-APEL > Update to glite-APEL 3.2.5-0.sl5  



gLite 3.2

glite-APEL - Update to version 3.2.5-0.sl5

Date 05.10.2010
Priority Normal



New version of glite-APEL

What's new

  • The Limit variable in the publisher configuration file is not compulsory. The default value (300000) will be used if Limit is not set or is not a valid number.
  • The APEL publisher won't optimise the database tables when it runs.

Installation and Configuration

  • The package fetch-crl is now part of the yum repository for the glite-APEL metapackage.
  • No dependency to java is specified in the metapackage. Please install jdk or openjdk previous to the metapackage.
  • For Sun JDK installations, YAIM changes the link to keytool to point to the jdk 1.6 version.
This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #65428 APEL Publisher Fails if <LIMIT> is Missing from Config
 #65721 apel publisher optimises tables each time it is launched
 #68636 fetch-crl not included in the yum repository
 #70546 log4j-1.2.13 pulls old java 1.4 version which breaks keytool
 #70751 Logging in AMQ APEL publisher still referring to RGMA table

Updated rpms

Name Version Full RPM name Description
fetch-crl 2.7.0-2 fetch-crl-2.7.0-2.noarch.rpm Tool for periodic retrieval of Certificate Revocation Lists
glite-APEL 3.2.5-0.sl5 glite-APEL-3.2.5-0.sl5.x86_64.rpm glite-APEL for version 3_2_5_0
glite-apel-core 2.0.13-8 glite-apel-core-2.0.13-8.noarch.rpm Core components of the Apel accounting application
glite-apel-publisher 2.0.13-6 glite-apel-publisher-2.0.13-6.noarch.rpm Apel account record publisher
glite-apel-yaim 1.0.2-1 glite-apel-yaim-1.0.2-1.noarch.rpm glite-apel-yaim_R_1_0_2_1
glite-version 3.2.3-1 glite-version-3.2.3-1.noarch.rpm Shows version information for the installed gLite node types
glite-yaim-core 4.0.13-2 glite-yaim-core-4.0.13-2.noarch.rpm YAIM core package

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

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)