gLite > gLite 3.1 > glite-MON > Update to glite-MON 3.1.3-0  
 
 

 

 

gLite 3.1

glite-MON - Update to version 3.1.3-0


Date 13.05.08
Priority Normal

Description


APEL is now working with external log4j and BouncyCastle. In gLite 3.1, log4j and BouncyCastle are not bundled with APEL anymore. Instead, the log4j and BouncyCastle provided by JPackage are used. APEL code needed to change the dependencies and the scripts to use JPackage.

The new version of the glite-security-trustmanager package fixes the problem of log4j and BouncyCastle jars not being installed in the tomcat server/lib directory.



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
 #29510 APEL loads log4j under old path
 #32661 Little bug on /opt/glite/etc/glite-security-trustmanager/configure.sh
 #33180 APEL in CE gLite3.1 is not publishing

Updated rpms

Name Version Full RPM name Description
glite-MON 3.1.3-0 glite-MON-3.1.3-0.i386.rpm gLite metapackage (glite-MON)
glite-apel-core 2.0.9-8 glite-apel-core-2.0.9-8.noarch.rpm Core components of the Apel accounting application
glite-apel-publisher 2.0.9-4 glite-apel-publisher-2.0.9-4.noarch.rpm Apel account record publisher
glite-security-trustmanager 1.8.16-1 glite-security-trustmanager-1.8.16-1.noarch.rpm org.glite.security.trustmanager v. 1.8.16-2

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)