Page updated: 21/03/2007
About the website

                        Valid XHTML 1.0!

 
gLite 3.0

glite-FTS_mysql - Update to version 3.0.8-0

Date 19.12.06
Priority High

Description


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

glite-data-common v1.3.2

o Adding method for clientDN resolution;
o Removed locking to avoid races->deadlocks in tomcat while used with dbcp.
o Canon(ical)ised the stripper
o Added CertParse utility servlet
o Added some tools (e.g. Precondition used in new Transfer service
o Fixed Bug #8714: should be able to specify log4j file in config

glite-data-transfer-fts v3.2.0-16

o Proper getTransferJobSummary subcalls.
o rebuild for new common (fixing bug #21296)
o check only major and minor schema version, not the whole thing.
o Add indices to improve performances
o Change information provider to use direct DB access.
 

Fixed bugs

Number Description
 #16534 TORQUE_server node in YAIM
 #16855 config_mkgridmap in a glitece+torque_server create gridmapfile via edg-mkgridmap
 #19120 config_mkgridmap creates edg-mkgridmap cron job on gliteCE
 #21057 FTS: sometimes transfer-url-copy doesn't call PutDone after a transfer failure
 #21058 FTS: transfer-url-copy reports 'No such active transfer' for successfully completed transfers
 #21209 There is a possible vulnerability with VO boxes
 #21296 FTS: web-service locks up several times a week under high load

Updated rpms

Name Version Full RPM name Description
glite-BDII 3.0.2-2 glite-BDII-3.0.2-2.noarch.rpm gLite BDII node
glite-data-common 1.3.2-1 glite-data-common-1.3.2-1.noarch.rpm common files for gLite Data Management web-services
glite-data-common 1.3.2-1 glite-data-common-1.3.2-1.noarch.rpm common files for gLite Data Management web-services
glite-data-transfer-fts 3.2.0-16 glite-data-transfer-fts-3.2.0-16.noarch.rpm gLite File Transfer Service (FTS)
glite-FTS_mysql 3.0.8-0 glite-FTS_mysql-3.0.8-0.noarch.rpm gLite FTS MySQL node
glite-yaim 3.0.0-34 glite-yaim-3.0.0-34.noarch.rpm glite-yaim

The RPMs can be updated using apt via

Service reconfiguration after update

Since the schema is changed, it is required to re-run YAIM to configure it. And at the end of running YAIM, it may ask to upgrade the schema by running certain commands.

Service restart after update

Yes.

How to apply the fix

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