Page updated: 21/03/2007
About the website

                        Valid XHTML 1.0!

gLite 3.0

glite-CE - Update to version 2.4.23-0

Date 11.12.06
Priority Normal


Introduced configuration for blah (/opt/glite/etc/blah.config) and blah cna generate logs for accounting.

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

Fixed bugs

Number Description
 #17064 location of log file parser in
 #17622 hard coded IP adress for server running the log file parser
 #17631 BLClient attempts to read arguments even if there are none
 #17858 Modification of glite-CE necessary because of the fix of the bug#17622
 #17942 RGMABufferFullException not handled in APEL
 #18663 Apel Data Privacy
 #18974 blah changed to use /opt/glite/etc/blah.config
 #20252 Publisher RPM overwrites its config file
 #20253 Apel publisher should support DGAS HLR
 #20898 APEL only queries port 2135 of site GIIS to get CPU information
 #20943 APEL data syncronisation and validity
 #20989 BLAH creates accounting log file with incorrect lrmsID info

Updated rpms

Name Version Full RPM name Description
glite-apel-condor 2.0.3-1 glite-apel-condor-2.0.3-1.noarch.rpm CONDOR log parser plugin
glite-apel-core 2.0.5-1 glite-apel-core-2.0.5-1.noarch.rpm Core components of the Apel accounting application
glite-apel-lsf 2.0.4-1 glite-apel-lsf-2.0.4-1.noarch.rpm LSF log parser plugin
glite-apel-pbs 2.0.3-1 glite-apel-pbs-2.0.3-1.noarch.rpm PBS log parser plugin
glite-apel-publisher 2.0.6-1 glite-apel-publisher-2.0.6-1.noarch.rpm Apel account record publisher
glite-apel-sge 2.0.3-1 glite-apel-sge-2.0.3-1.noarch.rpm CONDOR log parser plugin
glite-CE 2.4.23-0 glite-CE-2.4.23-0.noarch.rpm gLite Computing Element node configuration files
glite-ce-blahp 1.5.16-1 glite-ce-blahp-1.5.16-1.i386.rpm CE Blahp

The RPMs can be updated using apt via

Service reconfiguration after update

You need to reconfigure the service after the update.

Service restart after update

You need to restart the service after the update.

How to apply the fix

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