gLite > gLite 3.1 > glite-FTS_oracle > Update to glite-FTS_oracle 3.1.9-0  
 
 

 

 

gLite 3.1

glite-FTS_oracle - Update to version 3.1.9-0


Date 27.03.2009
Priority Normal

Description

- Upgrade of BDII. The main change is that the starting cache size used for the Berkeley Database in the BDII has been reduced from 1 GB to 50 MB. This should significantly reduce the memory footprint and still provide the necessary performance.

- DB_CONFIG now has "set_lk_max_locks 10000" (10k) to fix GGUS ticket 43230 ("gLite 3.1u34: lcg-cp failing on a BDII error in a MPI job").

- New version of VDT that introduces GridFTP2 support.

- FTS job submission sometimes ends up with an invalid delegated proxy certificate in the FTS service, thus transfers will fail. This update fixes the FTS web service's delegation code that the delegated proxy certificates should not be corrupted. The fix is transparent for the clients and there is no configuration change on the server side. One only needs to restart the FTS web service (Tomcat) after upgrading the glite-data-transfer-fts package.

- lcg-vomscerts-5.4.0 adds next cert for lcg-voms.cern.ch and removes old certs of cclcgvomsli01.in2p3.fr and vo.racf.bnl.govi.

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
 #33641 [delegation] corrupted proxies after delegation

Updated rpms

Name Version Full RPM name Description
bdii 4.0.1-4 bdii-4.0.1-4.noarch.rpm bdii
glite-FTS_oracle 3.1.9-0 glite-FTS_oracle-3.1.9-0.x86_64.rpm gLite metapackage (glite-FTS_oracle)
glite-data-transfer-fts 3.4.5-1 glite-data-transfer-fts-3.4.5-1.noarch.rpm gLite Data File Transfer Service (FTS)
lcg-vomscerts 5.4.0-1 lcg-vomscerts-5.4.0-1.noarch.rpm lcg-vomscerts
vdt_globus_essentials VDT1.6.1x86_64_rhas_4-9 vdt_globus_essentials-VDT1.6.1x86_64_rhas_4-9.x86_64.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)