Show Children Hide Children FtsChangeChannelType20 FtsProcedureDatabaseQueries20 FtsProcedureDropDBLock20 FtsProcedureFtaUpgrade20 FtsProcedureFtsChannelPause20 FtsProcedureFtsUpgrade20 FtsProcedureMoveIt20 FtsProcedures20IWantTheTheCore FtsProcedureSiteNameChange FtsProcedureTomcatClean20 FtsServerServicesXml20 FtsServiceProceduresNewNode FtsServicesXmlGliteSd2Cache
Main FTS Pages
FtsRelease22
Install
Configuration
Administration
Procedures
Operations
Development
Previous FTSes
FtsRelease21
FtsRelease21
All FTS Pages
FtsWikiPages
Last Page Update
GavinMcCance
2009-07-29

FTS procedures for 2.0

This page describes specific FTS operations procedures for the SLC3 release 2.0 of FTS (FtsRelease20), and for SLC4 release 2.1 of FTS (FtsRelease21).

This page is designed only for CERN-PROD operations.

Standard operating procedures

Installation of new node

To install a new node: FtsServiceProceduresNewNode.

Changing channel type

To change the channel type (between URLCOPY and SRMCOPY) for a given channel: FtsChangeChannelType20.

Building the service.xml cache

To build the services.xml cache file for a FTS server use the glite-sd2cache tool. This is installed automatically by YAIM. The details are given here: FtsServicesXmlGliteSd2Cache. It also explains how to run the tool by hand if this is necessary.

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 can pause the relevant FTS channel: FtsProcedureFtsChannelPause20.

Software upgrade or Maintenance of FTS web-service (rolling)

This is the general template procedure to follow for a rolling software upgrade of the FTS web-service: FtsProcedureFtsUpgrade20.

Software upgrade of FTA agent daemons (rolling)

This is the general template procedure to follow for a rolling software upgrade of the FTA agent nodes: FtsProcedureFtaUpgrade20.

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: FtsProcedureMoveIt20.

Changing a site-name in the channel definition table

This is the procedure to be used when a site changes it's (GOC) site name: FtsProcedureSiteNameChange.

Advanced operating procedures

I really want those core files

In some case, such as the famous Globus abort call, the transfer processes die badly. To see the core files: FtsProcedures20IWantTheTheCore.

Useful queries to the Database

Several queries to the database that have been performed: FtsProcedureDatabaseQueries20.

Cleaning Tomcat's working directories

This is the procedure to follow after a software upgrade of the FTS webservice: FtsProcedureTomcatClean20.

Removing by hand DB locks

The procedure is described in FtsProcedureDropDBLock20.

Database History Tool

The history tool is used to move old transfer records to a history table. FtsAdminTools20.

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2009-07-29 - GavinMcCance
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback