gLite > gLite 3.1 > lcg-CE > Update to lcg-CE 3.1.17-0  
 
 

 

 

gLite 3.1

lcg-CE - Update to version 3.1.17-0


Date 06.08.2008
Priority Normal

Description



  • support gSOAP 2.7.10 (provide matching gsoap-plugin library flavour)
  • fix bug #32059 aka security vulnerability bug #31911
  • miscelaneous memleaks fixed
lcg-extra-jobmanagers-1.1.15 has various improvements:
  • Record submit-helper download errors in logfiles on the WN named like this: /tmp/submit-helper-YYYYmmdd-HHMMSS-$USER-$$.
  • Set $FINAL_DONE_LOAD_RANGE to 1000 on advice of David Smith: when the load is high, finished jobs should still be cleaned up, otherwise they will keep piling up while the load remains high, which then may prevent the load from decreasing (seen at CERN).
  • Fix for bug #35580: do not assume the cwd is ${GLOBUS_LOCATION}/setup/globus.
  • Helper.pm: Increased cancel sleep time on advice from Andrey Kiryanov.
  • lcgpbs.in: Defined variable to avoid perl warning (fix by Andrey Kiryanov).


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
 #32059 There is a possible vulnerability with the glite WMS
 #35580 lcg-extra-jobmanagers contains a buggy PBS setup script, that fails configuring a jobmanager

Updated rpms

Name Version Full RPM name Description
glite-security-gsoap-plugin 1.5.3-1.slc4 glite-security-gsoap-plugin-1.5.3-1.slc4.i386.rpm org.glite.security.gsoap-plugin
glite-security-voms-api-c 1.8.3-4.slc4 glite-security-voms-api-c-1.8.3-4.slc4.i386.rpm org.glite.security.voms-api-c v. 1.8.3_4
lcg-CE 3.1.17-0 lcg-CE-3.1.17-0.i386.rpm gLite metapackage (lcg-CE)
lcg-extra-jobmanagers 1.1.15-1 lcg-extra-jobmanagers-1.1.15-1.noarch.rpm Jobmanagers for PBS and LSF that do not rely on a shared fs between CE WNs.
vdt_globus_data_server VDT1.6.1x86_rhas_4-7 vdt_globus_data_server-VDT1.6.1x86_rhas_4-7.i386.rpm Virtual Data Toolkit

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Service must be restarted.

How to apply the fix

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