FTS procedures for 1.5
This page describes the FTS operating procedures for release 1.5 of FTS.
Problem Diagnosis
Here is what to do in case of a problem with the FTS:
FTSSmokeTestAndActions
Particular
Building the service.xml cache
To build the
services.xml
cache file for a FTS server:
FtsServerServicesXml15.
Service maintenance: pausing channels
If any part of the overall transfer service needs to be stopped for maintenance (for example, if an SRM is going down for maintenance), you should pause the relevant FTS channel:
FtsProcedure15FtsChannelPause.
Software upgrade of FTS web-service (rolling)
This is the general procedure to follow for a rolling software upgrade of the FTS web-service:
FtsProcedure15FtsUpgrade.
Software upgrade of FTA agent daemons (rolling)
This is the general procedure to follow for a rolling software upgrade of the FTA agent nodes:
FtsProcedure15FtaUpgrade.
Moving the agents to another box: FTA maintenance or manual failover
This is the manual procedure to follow if you need to take one of the agent servers down for maintenance (for software upgrade, see above).
It is also the procedure to follow for manual failover:
FtsProcedure15MoveIt.
FTS web-service failover or maintenance
This is the procedure to follow for taking an FTS web-service node down for maintenance:
FtsProcedure15FtsMaintenance.
Advanced
Useful queries to the Database
Several queries to the database that have been performed:
FtsProcedure15DatabaseQueries.
Cleaning Tomcat's working directories
This is the procedure to follow after a software upgrade of the FTS webservice:
FtsProcedureTomcatClean15.
Removing by hand DB locks
The procedure is described in
FtsProcedure15DropDBLock.
Database History Tool
The history tool is used to move old transfer records to a history table.
FtsAdminTools15.
Maintainer:
GavinMcCance