FTS Known Issues.
This document contains the different problems found during the deployment and testing phase of FTS release 2.2.3 and how to solve them if possible. We also suggest the following page about some recurring difficulties:
FtsSupport2xx.
FTA configuration
log4cpp version
YAIM Values
YAIM variables reference
The FTS Configuration model and YAIM variables reference is available in the following link
FtsConfiguration.
Some variables and/or values have been deprecated, so please check them
Some channel setting are not handled via YAIM any more
- With FTS 2.1, various channel settings previously handled via YAIM and agents configuration files were moved to the database. Since the channel management command line interface were not updated accordingly, a migration script, update_channels.py, was provided and was called by YAIM each time a channel definition was updated. That script copied to the database the new parameters from the generated configuration files.
- FTS 2.2 those parameters are obsolete, and trying to set them through your YAIM configuration scripts will result in an error. The parameters should be set via the command line
Here we have the list of the parameters
TransferTimeout
HttpTimeout
SrmPutTimeout
SrmGetTimeout
SrmPutDoneTimeout
SrmGetDoneTimeout
TransferMarkersTimeout
TcpBufferSize
BlockSize
SrmStatusTimeout
SrmCopyDirection
-
- Configuration parameters:
log_level
verbose_log
Those parameters now are covered in the command line
glite-transfer-channel-set
DB Schema
History Package and Purge
Required permissions are
CREATE JOB " privilege + execute permissions on SYS.DBMS_SCHEDULER
SQL> exec fts_history.start_job
BEGIN fts_history.start_job; END;
ERROR at line 1:
ORA-27486: insufficient privileges
ORA-06512: at "SYS.DBMS_ISCHED", line 99
ORA-06512: at "SYS.DBMS_SCHEDULER", line 262
ORA-06512: at "GLITEFTS.FTS_HISTORY", line 203
ORA-06512: at line 1
New Bugs
Checksums are broken for Case 2
Checksums are not working as expected when the option -k or --compare-checksums is specified but there is no checksum provided.
Command: glite-transfer-submit --compare-checksums source-SURL destination-SURL
Command: glite-transfer-submit -K source-SURL destination-SURL
This case scenario is not frequently used by the experiments (confirmed by Atlas and CMS). So this bug should not be a reason for not upgrading to the releasenot relevant for the CMS and ATLAS. So you can use the other 2 cases while the bug is fixed and released.
Savanna bug
https://savannah.cern.ch/bugs/index.php?63518
Yaim values have priority over DB values
Check the new parameters that can be configured now from the command line
Open a bug for the YAIM overwritting the info in the DB for the tx_log (DEBUG flag), and how to fix it.
Old issues still present in FTS 2.2.3
Oracle instantclient libstdc++ dependency on SL4
The background of the problem:
https://twiki.cern.ch/twiki/bin/view/LCG/FtsKnownIssues21#Oracle_instantclient_libstdc_dep
This problem is still present in FTS 2.2.3, but it may manifest itself in a different way then the above page describes: the agent crashes after startup, at the very first database operations. Check the description about the workaround.
This problem was reported in the following GGUS ticket:
https://gus.fzk.de/ws/ticket_info.php?ticket=56384
-- Main.RosaGarciaRioja - 09-Mar-2010