Testing FTS Upgrade from 2.1 to 2.2.3
The starting point was the first FTS release for gLite 3.1, which I assumed being FTS 2.1
Steps performed on a clean vNode SL4 machine, vtb-generic-57.cern.ch:
# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/jpackage.repo -P /etc/yum.repos.d
# yum -y install jpackage-utils
=============================================================================
Package Arch Version Repository Size
=============================================================================
Updating:
jpackage-utils noarch 5.0.0-2.jpp5 jpackage5-generic 72 k
# wget http://glite.web.cern.ch/glite/packages/R3.1/deployment/glite-FTS_oracle/3.1.1-0/glite-FTS_oracle-3.1.1-0.rpm.list.txt
# wget -i glite-FTS_oracle-3.1.1-0.rpm.list.txt
_The Jpackage 1.7 files have been removed_
# yum -y --enablerepo=CERN-only install oracle-instantclient-basic oracle-instantclient-sqlplus
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
oracle-instantclient-basic i386 10.2.0.3-3.slc4 CERN-only 33 M
oracle-instantclient-sqlplus i386 10.2.0.3-3.slc4 CERN-only 726 k
# yum -y --enablerepo=CERN-only install java-1.5.0-sun java-1.5.0-sun-devel
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
java-1.5.0-sun i586 1.5.0.15-1.slc4 CERN-only 31 M
java-1.5.0-sun-devel i586 1.5.0.15-1.slc4 CERN-only 5.1 M
# ls
CGSI_gSOAP_2.7-1.2.1-2.slc4.i386.rpm glite-service-discovery-file-c-2.1.2-2.slc4.i386.rpm
ant-1.7.1-7.jpp5.noarch.rpm glite-version-3.1.0-1.slc4.i386.rpm
bdii-3.9.1-5.noarch.rpm glite-yaim-core-4.0.4-2.noarch.rpm
bea-stax-1.2.0-0.rc1.3.jpp5.noarch.rpm glite-yaim-fts-4.0.12-1.noarch.rpm
bea-stax-api-1.2.0-0.rc1.3.jpp5.noarch.rpm glue-schema-1.3.0-3.noarch.rpm
edg-mkgridmap-3.0.0-1.noarch.rpm gridsite-shared-1.1.18.1-1.i386.rpm
fetch-crl-2.6.3-1.noarch.rpm icu4j-3.8.1-5.jpp5.noarch.rpm
glite-FTS_oracle-3.1.1-0.rpm.list.txt isorelax-0.1-0.20041111.6.jpp5.noarch.rpm
glite-data-delegation-api-c-2.0.0-4.slc4.i386.rpm jakarta-commons-dbcp-tomcat5-1.2.2-2.jpp5.noarch.rpm
glite-data-delegation-cli-2.0.0-4.slc4.i386.rpm jakarta-commons-digester-1.8-1jpp.noarch.rpm
glite-data-transfer-api-c-3.4.0-1.slc4.i386.rpm jakarta-commons-logging-1.1-8.jpp5.noarch.rpm
glite-data-transfer-cli-3.4.3-2.slc4.i386.rpm jakarta-commons-pool-tomcat5-1.3-11.jpp5.noarch.rpm
glite-data-transfer-fts-3.4.2-3.noarch.rpm jdom-1.0-5.jpp5.noarch.rpm
glite-data-util-c-1.2.3-1.slc4.i386.rpm lcg-vomscerts-5.0.0-1.noarch.rpm
glite-info-generic-2.0.2-3.noarch.rpm msv-1.2-0.20050722.6.jpp5.noarch.rpm
glite-info-templates-1.0.0-8.noarch.rpm msv-xsdlib-1.2-0.20050722.6.jpp5.noarch.rpm
glite-security-delegation-interface-2.0.0-1.noarch.rpm newlist.txt
glite-security-trustmanager-1.8.16-1.noarch.rpm relaxngDatatype-1.0-3.jpp5.noarch.rpm
glite-security-util-java-1.4.0-1.noarch.rpm saxon-6.5.5-1.jpp5.noarch.rpm
glite-security-voms-api-c-1.8.3-4.slc4.i386.rpm user_certificates
glite-service-discovery-api-c-2.2.2-2.slc4.i386.rpm vdt_globus_essentials-VDT1.6.1x86_rhas_4-6.i386.rpm
glite-service-discovery-bdii-c-2.2.2-2.slc4.i386.rpm xpp2-2.1.10-6.jpp5.noarch.rpm
glite-service-discovery-cli-2.2.1-2.slc4.i386.rpm xpp3-1.1.3.8-1.jpp5.noarch.rpm
# yum --enablerepo=dag localinstall *.rpm
Installed: CGSI_gSOAP_2.7.i386 0:1.2.1-2.slc4 ant.noarch 0:1.7.1-7.jpp5 bdii.noarch 0:3.9.1-5 bea-stax.noarch 0:1.2.0-0.rc1.3.jpp5 bea-stax-api.noarch 0:1.2.0-0.rc1.3.jpp5 edg-mkgridmap.noarch 0:3.0.0-1 fetch-crl.noarch 0:2.6.3-1 glite-data-delegation-api-c.i386 0:2.0.0-4.slc4 glite-data-delegation-cli.i386 0:2.0.0-4.slc4 glite-data-transfer-api-c.i386 0:3.4.0-1.slc4 glite-data-transfer-cli.i386 0:3.4.3-2.slc4 glite-data-transfer-fts.noarch 0:3.4.2-3 glite-data-util-c.i386 0:1.2.3-1.slc4 glite-info-generic.noarch 0:2.0.2-3 glite-info-templates.noarch 0:1.0.0-8 glite-security-delegation-interface.noarch 0:2.0.0-1 glite-security-trustmanager.noarch 0:1.8.16-1 glite-security-util-java.noarch 0:1.4.0-1 glite-security-voms-api-c.i386 0:1.8.3-4.slc4 glite-service-discovery-api-c.i386 0:2.2.2-2.slc4 glite-service-discovery-bdii-c.i386 0:2.2.2-2.slc4 glite-service-discovery-cli.i386 0:2.2.1-2.slc4 glite-service-discovery-file-c.i386 0:2.1.2-2.slc4 glite-version.i386 0:3.1.0-1.slc4 glite-yaim-core.noarch 0:4.0.4-2 glite-yaim-fts.noarch 0:4.0.12-1 glue-schema.noarch 0:1.3.0-3 gridsite-shared.i386 0:1.1.18.1-1 icu4j.noarch 0:3.8.1-5.jpp5 isorelax.noarch 0:0.1-0.20041111.6.jpp5 jakarta-commons-dbcp-tomcat5.noarch 0:1.2.2-2.jpp5 jakarta-commons-digester.noarch 0:1.8-1jpp jakarta-commons-logging.noarch 0:1.1-8.jpp5 jakarta-commons-pool-tomcat5.noarch 0:1.3-11.jpp5 jdom.noarch 0:1.0-5.jpp5 lcg-vomscerts.noarch 0:5.0.0-1 msv.noarch 0:1.2-0.20050722.6.jpp5 msv-xsdlib.noarch 0:1.2-0.20050722.6.jpp5 relaxngDatatype.noarch 0:1.0-3.jpp5 saxon.noarch 0:6.5.5-1.jpp5 vdt_globus_essentials.i386 0:VDT1.6.1x86_rhas_4-6 xpp2.noarch 0:2.1.10-6.jpp5 xpp3.noarch 0:1.1.3.8-1.jpp5
Dependency Installed: bcel.noarch 0:5.1-16.jpp5 bouncycastle.noarch 0:1.43-1.jpp5 classpathx-mail.noarch 0:1.1.2-1.jpp5 dom4j.noarch 0:1.6.1-10.jpp5 ecj.noarch 1:3.3.1.1-3.jpp5 geronimo-j2ee-1.4-apis.noarch 0:1.2-13.jpp5 geronimo-jaf-1.0.2-api.noarch 0:1.2-13.jpp5 geronimo-javamail-1.4-api.noarch 0:1.2-13.jpp5 geronimo-jms-1.1-api.noarch 0:1.2-13.jpp5 geronimo-specs-poms.noarch 0:1.2-13.jpp5 geronimo-stax-1.0-api.noarch 0:1.2-13.jpp5 glassfish-jaf.noarch 0:1.1.0-5.jpp5 glassfish-jaxb.noarch 0:2.1.4-7.jpp5 jakarta-commons-beanutils.noarch 0:1.7.0-10.jpp5 jakarta-commons-collections.noarch 0:3.1-9.jpp5 jakarta-commons-collections-tomcat5.noarch 0:3.1-9.jpp5 jakarta-commons-daemon.noarch 1:1.0.1-7.jpp5 jakarta-commons-el.noarch 0:1.0-12.jpp5 jakarta-commons-launcher.noarch 0:1.1-4.jpp5 jakarta-commons-modeler.noarch 0:2.0-5.jpp5 jaxen.noarch 0:1.1-3.jpp5 jdk.i586 2000:1.6.0_17-fcs log4j.noarch 0:1.2.14-15.jpp5 mx4j.noarch 0:3.0.1-9.jpp5 openldap-servers.i386 0:2.2.13-12.el4 perl-DateManip.noarch 0:5.42a-3 perl-IO-Socket-SSL.noarch 0:1.31-1.el4.rf perl-Net-SSLeay.i386 0:1.35-2.el4.rf perl-TermReadKey.i386 0:2.30-3.el4.rf perl-XML-DOM.noarch 0:1.44-2.el4.rf perl-XML-RegExp.noarch 0:0.03-1.2.el4.rf regexp.noarch 0:1.5-1.jpp5 tomcat5.noarch 0:5.5.27-7.jpp5 tomcat5-common-lib.noarch 0:5.5.27-7.jpp5 tomcat5-jasper.noarch 0:5.5.27-7.jpp5 tomcat5-jsp-2.0-api.noarch 0:5.5.27-7.jpp5 tomcat5-server-lib.noarch 0:5.5.27-7.jpp5 tomcat5-servlet-2.4-api.noarch 0:5.5.27-7.jpp5 ws-jaxme.noarch 0:0.5.1-10.jpp5 xalan-j2.noarch 0:2.7.0-10.jpp5 xerces-j2.noarch 0:2.7.1-12.jpp5 xml-commons.noarch 0:1.3.04-5.jpp5 xml-commons-jaxp-1.2-apis.noarch 0:1.3.04-5.jpp5 xml-commons-jaxp-1.3-apis.noarch 0:1.3.04-5.jpp5 xml-commons-resolver11.noarch 0:1.3.04-5.jpp5 xom.noarch 0:1.2.1-1.jpp5
Complete!
# mkdir /etc/yaim/
# cd /etc/yaim/
# wget https://pucciani.web.cern.ch/pucciani/yaimfiles/yaimfiles.tar.gz
# tar -xvzf yaimfiles.tar.gz
groups.conf
site-info.def
users.conf
vo.d/
vo.d/org.glite.voms-test
wn-list.conf
# sed -i 's/bash/sh/' /etc/rc.d/init.d/tomcat5
site-info.def modified to include:
###############################
# FTS configuration variables #
###############################
FTS_HOST="vtb-generic-57.cern.ch"
FTS_HOST_ALIAS=${FTS_HOST}
FTS_SERVER_URL="https://${FTS_HOST}:8443/glite-data-transfer-fts"
FTA_GLOBAL_DB_CONNECTSTRING="(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))"
FTS_DBURL="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))"
FTS_DB_TYPE=ORACLE
FTS_DB_USER=lcg_voms_test_5
FTS_DB_PASSWORD=**************
TOMCAT_USER=tomcat
ORACLE_LOCATION="/usr/lib/oracle/10.2.0.3"
JAVA_LOCATION="/usr/lib/jvm/jre-1.5.0"
The database was cleaned using
/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-drop.sql
and he first Yaim run gave:
# /opt/glite/yaim/bin/yaim -c -s ./site-info.def -n FTS2
[...]
INFO: FTS database type Oracle selected
INFO: Setting FTS_DB_SQLPLUS_CONNECTSTRING to the value
INFO: set for FTA agents from FTA_GLOBAL_DB_CONNECTSTRING
INFO: Service administrator mapfile /opt/glite/etc/glite-data-transfer-manager-mapfile already exists. Not updating.
INFO: Copying Oracle JDBC jar file to tomcat common lib directory...
INFO: Testing DB account and FTS schema...
ABORT: Database schema does not appear to be loaded. Assuming yaim is currently configured with the username of the schema owner account, please load it using the command:
ABORT: sqlplus "LCG_FTS_SA3TESTS3/***********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-schema.sql
ABORT: If this command only completes partially then there is a problem with your schema, please drop the schema contents by hand and retry (ask your DBA)
sqlplus "LCG_FTS_SA3TESTS3/********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-schema.sql
Second run of Yaim gave:
INFO: Testing DB account and FTS schema...
INFO: ...schema OK.
INFO: Testing delegation schema...
ABORT: Delegation schema does not appear to be loaded. Assuming yaim is currently configured with the username of the schema owner account, please load it using the command:
ABORT: sqlplus "lcg_voms_test_5/********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-security-delegation-interface/schema/oracle/oracle-schema.sql
ABORT:
The delegetation schema was created by running
/opt/glite/etc/glite-security-delegation-interface/schema/oracle/oracle-schema.sql
The third run of Yaim gave:
INFO: Testing DB account and FTS schema...
INFO: ...schema OK.
INFO: Testing delegation schema...
INFO: ...schema OK.
INFO: Making context file /etc/tomcat5/Catalina/localhost/glite-data-transfer-fts.xml...
INFO: Replacing JAVA_HOME in the file /etc/tomcat5/tomcat5.conf...
INFO: Replacing LD_LIBRARY_PATH and CATALINA_OPTS (if they exist) in the file /etc/tomcat5/tomcat5.conf...
INFO: Installing log rotation for FTS (N.B. it's not a standard logrotate script)...
INFO: Creating basic /opt/glite/etc/services.xml file...
INFO: Doing chkconfig for tomcat5...
INFO: Restarting Tomcat:
Stopping tomcat5: [FAILED]
Starting tomcat5: [ OK ]
INFO: Configuration Complete.
At this point the version of the schema was 3.2.0
# sqlplus "lcg_voms_test_5/************@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-get-version.sql
SQL*Plus: Release 10.2.0.3.0 - Production on Wed Feb 24 16:47:52 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
3.2.0
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
From this point the upgrade to the latest version was done by:
# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/glite-FTS_oracle.repo -P /etc/yum.repos.d/
# yum upgrade
[...]
Installed: ca_policy_igtf-classic.noarch 0:1.34-1 glite-data-transfer-cli.i386 0:3.7.2-1.slc4 kernel.i686 0:2.6.9-89.0.20.EL kernel-module-openafs-2.6.9-89.0.20.EL.i686 0:1.4.7-68.2.SL4 kernel-module-openafs-2.6.9-89.0.20.ELxenU.i686 0:1.4.7-68.2.SL4 kernel-xenU.i686 0:2.6.9-89.0.20.EL lcg-CA.noarch 0:1.34-1
Dependency Installed: ca_AAACertificateServices.noarch 0:1.34-1 ca_CESNET-CA-3.noarch 0:1.34-1 ca_CESNET-CA-Root.noarch 0:1.34-1 ca_TERENAeSciencePersonalCA.noarch 0:1.34-1 ca_UTNAAAClient.noarch 0:1.34-1
Updated: CGSI_gSOAP_2.7.i386 0:1.3.3-1.slc4 bdii.noarch 0:4.0.1-4 ca_AEGIS.noarch 0:1.34-1 ca_AIST.noarch 0:1.34-1 ca_APAC.noarch 0:1.34-1 ca_ASGCCA-2007.noarch 0:1.34-1 ca_ArmeSFo.noarch 0:1.34-1 ca_AustrianGrid.noarch 0:1.34-1 ca_BEGrid2008.noarch 0:1.34-1 ca_BG-ACAD-CA.noarch 0:1.34-1 ca_BYGCA.noarch 0:1.34-1 ca_BalticGrid.noarch 0:1.34-1 ca_BrGrid.noarch 0:1.34-1 ca_CALG.noarch 0:1.34-1 ca_CERN-Root.noarch 0:1.34-1 ca_CERN-TCA.noarch 0:1.34-1 ca_CESNET.noarch 0:1.34-1 ca_CNIC.noarch 0:1.34-1 ca_CNRS2.noarch 0:1.34-1 ca_CNRS2-Grid-FR.noarch 0:1.34-1 ca_CNRS2-Projets.noarch 0:1.34-1 ca_CyGrid.noarch 0:1.34-1 ca_DFN-GridGermany-Root.noarch 0:1.34-1 ca_DFN-SLCS.noarch 0:1.34-1 ca_DOEGrids.noarch 0:1.34-1 ca_ESnet.noarch 0:1.34-1 ca_FNAL-SLCS.noarch 0:1.34-1 ca_GermanGrid.noarch 0:1.34-1 ca_Grid-Ireland.noarch 0:1.34-1 ca_GridCanada.noarch 0:1.34-1 ca_HKU.noarch 0:1.34-1 ca_HellasGrid-CA-2006.noarch 0:1.34-1 ca_HellasGrid-Root.noarch 0:1.34-1 ca_IGCA.noarch 0:1.34-1 ca_IHEP.noarch 0:1.34-1 ca_INFN-CA-2006.noarch 0:1.34-1 ca_IRAN-GRID.noarch 0:1.34-1 ca_IUCC.noarch 0:1.34-1 ca_KEK.noarch 0:1.34-1 ca_KISTI-2007.noarch 0:1.34-1 ca_LACGridCA.noarch 0:1.34-1 ca_LIPCA.noarch 0:1.34-1 ca_MARGI.noarch 0:1.34-1 ca_MD-Grid.noarch 0:1.34-1 ca_MREN-CA.noarch 0:1.34-1 ca_MaGrid.noarch 0:1.34-1 ca_NAREGI.noarch 0:1.34-1 ca_NCHC.noarch 0:1.34-1 ca_NCSA-mics.noarch 0:1.34-1 ca_NCSA-slcs.noarch 0:1.34-1 ca_NECTEC.noarch 0:1.34-1 ca_NERSC-SLCS.noarch 0:1.34-1 ca_NGO-Netrust.noarch 0:1.34-1 ca_NIIF.noarch 0:1.34-1 ca_NIKHEF.noarch 0:1.34-1 ca_NorduGrid.noarch 0:1.34-1 ca_PK-Grid-2007.noarch 0:1.34-1 ca_PRAGMA-UCSD.noarch 0:1.34-1 ca_PolishGrid.noarch 0:1.34-1 ca_QuoVadis-Root-CA1.noarch 0:1.34-1 ca_RDIG.noarch 0:1.34-1 ca_REUNA-ca.noarch 0:1.34-1 ca_RomanianGRID.noarch 0:1.34-1 ca_SDG.noarch 0:1.34-1 ca_SEE-GRID.noarch 0:1.34-1 ca_SRCE.noarch 0:1.34-1 ca_SWITCH-QuoVadis-Grid-ICA.noarch 0:1.34-1 ca_SWITCHgrid-Root.noarch 0:1.34-1 ca_SWITCHslcs.noarch 0:1.34-1 ca_SiGNET-CA.noarch 0:1.34-1 ca_SlovakGrid.noarch 0:1.34-1 ca_TACC-Classic.noarch 0:1.34-1 ca_TACC-MICS.noarch 0:1.34-1 ca_TACC-Root.noarch 0:1.34-1 ca_TRGrid.noarch 0:1.34-1 ca_UGRID.noarch 0:1.34-1 ca_UKeScienceCA-2007.noarch 0:1.34-1 ca_UKeScienceRoot-2007.noarch 0:1.34-1 ca_ULAGrid-CA-2008.noarch 0:1.34-1 ca_UNAMgrid-ca.noarch 0:1.34-1 ca_UNLPGrid.noarch 0:1.34-1 ca_ncsa-gridshib-ca.noarch 0:1.34-1 ca_pkIRISGrid.noarch 0:1.34-1 ca_policy_igtf-mics.noarch 0:1.34-1 ca_policy_igtf-slcs.noarch 0:1.34-1 fetch-crl.noarch 0:2.7.0-1 glite-data-delegation-api-c.i386 0:2.0.0-7.slc4 glite-data-delegation-cli.i386 0:2.0.0-5.slc4 glite-data-transfer-fts.noarch 0:3.7.0-3 glite-info-templates.noarch 0:1.0.0-11 glite-security-trustmanager.noarch 0:1.8.16-3 glite-security-voms-api-c.i386 0:1.8.12-1.slc4 glite-yaim-core.noarch 0:4.0.11-2 glite-yaim-fts.noarch 0:4.1.5-1 glue-schema.noarch 0:1.3.0-5 lcg-vomscerts.noarch 0:5.8.0-1 vdt_globus_essentials.i386 0:VDT1.6.1x86_rhas_4-9
Replaced: ca_CNRS.noarch 0:1.32-1 ca_CNRS-Grid-FR.noarch 0:1.32-1 ca_CNRS-Projets.noarch 0:1.32-1 ca_FNAL_KCA.noarch 0:1.32-1 glite-data-transfer-api-c.i386 0:3.4.0-1.slc4
Complete!
Re-running Yaim:
# /opt/glite/yaim/bin/yaim -c -s ./site-info.def -n FTS2
[...]
INFO: FTS database type Oracle selected
INFO: Setting FTS_DB_SQLPLUS_CONNECTSTRING to the value
INFO: set for FTA agents from FTA_GLOBAL_DB_CONNECTSTRING
INFO: Service administrator mapfile /opt/glite/etc/glite-data-transfer-manager-mapfile already exists. Not updating.
INFO: Copying Oracle JDBC jar file to tomcat common lib directory...
INFO: Testing DB account and FTS schema...
INFO: The expected schema version is 3.4.1
ABORT: Database schema is using the old 3.2.0 version.
ABORT: Please upgrade to 3.4.1 using the following command(s)
ABORT: (assuming yaim is configured to use the schema owner account):
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "LCG_FTS_SA3TESTS3/**********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-upgrade_3.2.0-3.3.0.sql
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "LCG_FTS_SA3TESTS3/********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-upgrade_3.3.0-3.4.0.sql
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "LCG_FTS_SA3TESTS3/********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-upgrade_3.4.0-3.4.1.sql
ABORT: NOTE: This operation is irreversible!
ERROR: One of the functions returned with error without specifying it's nature !
The schema was updated by running the commands
# /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "LCG_FTS_SA3TESTS3/*********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-upgrade_3.2.0-3.3.0.sql
[..]
Updating schema version...
SUCCESS: Patch applied. New version is 3.3.0
PL/SQL procedure successfully completed.
/usr/lib/oracle/10.2.0.3/client/bin/sqlplus "LCG_FTS_SA3TESTS3/*********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-upgrade_3.3.0-3.4.0.sql
[...]
INFO: Column [t_fts_plugin_schema.schemaversion] added
Updating schema version...
SUCCESS: Patch applied. New version is 3.4.0
PL/SQL procedure successfully completed.
/usr/lib/oracle/10.2.0.3/client/bin/sqlplus "LCG_FTS_SA3TESTS3/*********@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/oracle-upgrade_3.4.0-3.4.1.sql
[...]
Applying Patch...
Upgrading T_SCHEMA_VERS...
Upgrading schema 3.4.0 to 3.4.1 ...
Updating schema version...
SUCCESS: Patch applied. New version is 3.4.1
PL/SQL procedure successfully completed.
Running Yaim again:
[...]
INFO: Testing DB account and FTS schema...
INFO: The expected schema version is 3.4.1
INFO: ...schema OK.
INFO: Testing delegation schema...
INFO: ...schema OK.
INFO: Testing the history package...
ABORT: FTS history package does not appear to be loaded. Assuming yaim is currently configured with the username of the schema owner account, please load it using the command:
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "lcg_voms_test_5/******@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_history_pack.sql
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "lcg_voms_test_5/******@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_history_body_pack.sql
ERROR: One of the functions returned with error without specifying it's nature !
/opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_history_pack.sql and /opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_history_body_pack.sql where successfully applied.
Running Yaim again:
[...]
INFO: Testing DB account and FTS schema...
INFO: The expected schema version is 3.4.1
INFO: ...schema OK.
INFO: Testing delegation schema...
INFO: ...schema OK.
INFO: Testing the history package...
INFO: ...schema OK.
INFO: Testing the purge package...
ABORT: FTS purge package does not appear to be loaded. Assuming yaim is currently configured with the username of the schema owner account, please load it using the command:
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "lcg_voms_test_5/*****@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_purge_pack.sql
ABORT: /usr/lib/oracle/10.2.0.3/client/bin/sqlplus "lcg_voms_test_5/*****@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=int11r2-v.cern.ch)(PORT=10121))(ADDRESS=(PROTOCOL=TCP)(HOST=int11r1-v.cern.ch)(PORT=10121))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=lcg_fts_int11r.cern.ch)))" @/opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_purge_body_pack.sql
ERROR: One of the functions returned with error without specifying it's nature !
/opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_purge_pack.sql and /opt/glite/etc/glite-data-transfer-fts/schema/oracle/fts_purge_body_pack.sql where successfully applied.
Final run of Yaim:
[...]
INFO: Testing DB account and FTS schema...
INFO: The expected schema version is 3.4.1
INFO: ...schema OK.
INFO: Testing delegation schema...
INFO: ...schema OK.
INFO: Testing the history package...
INFO: ...schema OK.
INFO: Testing the purge package...
INFO: ...schema OK.
INFO: Making context file /etc/tomcat5/Catalina/localhost/glite-data-transfer-fts.xml...
INFO: Replacing JAVA_HOME in the file /etc/tomcat5/tomcat5.conf...
INFO: Replacing CATALINA_OPTS (if it exists) in the file /etc/tomcat5/tomcat5.conf...
INFO: Adding LD_LIBRARY_PATH for the native JDBC driver in the file /etc/tomcat5/tomcat5.conf...
INFO: Installing log rotation for FTS (N.B. it's not a standard logrotate script)...
INFO: /opt/glite/etc/services.xml already exists. Will not update!
INFO: Please ensure you have added a delegation service block (see /tmp/glite-fts-add-delegation.services.xml)
INFO: Doing chkconfig for tomcat5...
INFO: Restarting Tomcat:
Stopping tomcat5: [ OK ]
Starting tomcat5: [ OK ]
DEBUG: Skipping function: config_bdii_only_setenv because it is not defined
INFO: Executing function: config_bdii_only
Stopping BDII [ OK ]
Starting BDII [ OK ]
INFO: Configuration Complete. [ OK ]
INFO: YAIM terminated succesfully.
At this point, installing FTS from production gives the same error reported in
ticket=55828
.
# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/glite-FTA_oracle.repo -P /etc/yum.repos.d/
# yum install glite-FTA_oracle
# /opt/glite/yaim/bin/yaim -c -s ./site-info.def -n FTA2
[...]
INFO: Executing function: config_FTA2_agents
DEBUG: Setting up the environment
DEBUG: Setting environment variable GLITE_LOCATION, to value "/opt/glite".
DEBUG: Unset environment variable GLITE_LOCATION.
DEBUG: Setting default configuration files for known agents' types
DEBUG: Checking the DB type
INFO: FTA database type Oracle selected
INFO: Site definiton file contains definitions for FTA agent server ONE on host vtb-generic-57.cern.ch
INFO: Running basic sanity check on site definition file...
DEBUG: FTA_MACHINES = ONE
DEBUG: san_mach = ONE; sanmachsub=FTA_AGENTS_ONE
DEBUG: san_agent = DTEAM; atsub=FTA_DTEAM
DEBUG: Agent "DTEAM" has the following variables: FTA_DTEAM
DEBUG: san_agent_type = FTA_TYPEDEFAULT_VOAGENT
DEBUG: used_agents_types=FTA_TYPEDEFAULT_VOAGENT
DEBUG: san_agent = VOMSTEST; atsub=FTA_VOMSTEST
DEBUG: Agent "VOMSTEST" has the following variables: FTA_VOMSTEST FTA_VOMSTEST_AGENT_NAME
DEBUG: san_agent_type = FTA_TYPEDEFAULT_VOAGENT
DEBUG: used_agents_types=FTA_TYPEDEFAULT_VOAGENT
DEBUG: san_agent = CERN-CERN; atsub=FTA_CERN_CERN
DEBUG: Agent "CERN-CERN" has the following variables: FTA_CERN_CERN
DEBUG: san_agent_type = FTA_TYPEDEFAULT_SRMCOPY
DEBUG: used_agents_types=FTA_TYPEDEFAULT_VOAGENT FTA_TYPEDEFAULT_SRMCOPY
DEBUG: san_agent = CERN-DESY; atsub=FTA_CERN_DESY
DEBUG: Agent "CERN-DESY" has the following variables: FTA_CERN_DESY
DEBUG: san_agent_type = FTA_TYPEDEFAULT_URLCOPY
DEBUG: used_agents_types=FTA_TYPEDEFAULT_VOAGENT FTA_TYPEDEFAULT_SRMCOPY FTA_TYPEDEFAULT_URLCOPY
DEBUG: Type "FTA_TYPEDEFAULT_VOAGENT" has vars: FTA_TYPEDEFAULT_VOAGENT_ACTIONS_RETRYMODULE FTA_TYPEDEFAULT_VOAGENT_ACTIONS_RETRYPARAMS FTA_TYPEDEFAULT_VOAGENT_PYTHON_PYTHONPATH
DEBUG: Type "FTA_TYPEDEFAULT_SRMCOPY" has vars: FTA_TYPEDEFAULT_SRMCOPY_ACTIONS_SURLNORMALIZATION
DEBUG: Type "FTA_TYPEDEFAULT_URLCOPY" has vars:
INFO: ... file looks OK.
INFO: Copying hostcert to /etc/grid-security/glite-data-transfer-agents-cert.pem for :root......
INFO: Copying hostkey to /etc/grid-security/glite-data-transfer-agents-key.pem for :root...
INFO: This hostname is: vtb-generic-57.cern.ch
INFO: This machine is going to be configured as server: ONE
INFO: The following agents will be configured on this server:
INFO: DTEAM of type VOAGENT
INFO: VOMSTEST of type VOAGENT
INFO: CERN-CERN of type SRMCOPY
INFO: CERN-DESY of type URLCOPY
INFO: Making temporary config directory as /tmp/tmp.Nwymw14631
INFO: Writing input file for the global defaults to temporary file: /tmp/tmp.Nwymw14631/global.config.properties
INFO: Configuring agent DTEAM of type VOAGENT...
INFO: Agent DTEAM uses template file: /opt/glite/share/config/glite-data-transfer-agents/glite-transfer-vo-agent-python-oracle.config.xml
INFO: This is the default template file for this agent type.
INFO: New agent type VOAGENT used. Creating the default generator config files for it.
INFO: Writing generator input file for agent type VOAGENT to temporary file: /tmp/tmp.Nwymw14631/agenttype.VOAGENT.config.properties
INFO: Agent type VOAGENT overrides some defaults with the following variables:
FTA_TYPEDEFAULT_VOAGENT_ACTIONS_RETRYMODULE FTA_TYPEDEFAULT_VOAGENT_ACTIONS_RETRYPARAMS FTA_TYPEDEFAULT_VOAGENT_PYTHON_PYTHONPATH
INFO: Generating instance configuration...
INFO: No instance variables changed for this agent. Defaults will be used.
ERROR: Config generator failed with errors. See message above.
ERROR: Error during the execution of function: config_FTA2_agents
^[[80G[^[[1;31mFAILED^[[0;39m]^M ERROR: Error during the configuration.Exiting.
ERROR: One of the functions returned with error without specifying it's nature !
Adding some more logging messages and re-running the yaim function:
# /opt/glite/yaim/bin/yaim -r -s ./site-info.def -f config_FTA2_agents
[..]
ERROR: The following command returned 127
ERROR: /opt/glite/bin/glite_data_config_generator -f /opt/glite/share/config/glite-data-transfer-agents/glite-transfer-vo-agent-python-oracle.config.xml -p /tmp/tmp.rlGkA21087/global.config.properties -p /tmp/tmp.rlGkA21087/agenttype.VOAGENT.config.properties -p /tmp/tmp.rlGkA21087/agentinstance.DTEAM.config.properties -o /tmp/tmp.rlGkA21087/glite-transfer-vo-agent-DTEAM.properties.xml -l /tmp/tmp.rlGkA21087/glite-transfer-vo-agent-DTEAM.log-properties
ERROR: Error during the execution of function: config_FTA2_agents
[root@vtb-generic-57 yaim]# /opt/glite/bin/glite_data_config_generator
/opt/glite/bin/glite_data_config_generator: error while loading shared libraries: liblog4cpp.so.4: cannot open shared object file: No such file or directory
The problem was a not updated version of log4cpp:
[root@vtb-generic-57 yaim]# rpm -ql log4cpp-0.3.4b-2.slc4 | grep liblog4cpp.so
/opt/log4cpp/lib/liblog4cpp.so
/opt/log4cpp/lib/liblog4cpp.so.3
/opt/log4cpp/lib/liblog4cpp.so.3.1.3
After installing a newer version of log4cpp enabling the dag repository config_FTA2_agents run ok.
# yum --enablerepo=dag install log4cpp
[...]
=============================================================================
Package Arch Version Repository Size
=============================================================================
Updating:
log4cpp i386 1.0-1.el4.rf dag 2.4 M
[root@vtb-generic-57 yaim]# /opt/glite/bin/glite_data_config_generator
<glite-data-config-generator> Version 2.5.0
Usage:
[...]
# /opt/glite/yaim/bin/yaim -r -s ./site-info.def -f config_FTA2_agents
[...]
INFO: Scanning existing configuration...
INFO: There are 0 existing agents.
INFO:
New agents that are being defined on this server:
INFO: DTEAM
INFO: VOMSTEST
INFO: CERN-CERN
INFO: CERN-DESY
INFO:
Copied configuration successfully to directory:
/opt/glite/etc/glite-data-transfer-agents.d/
INFO: Wrote daemon sysconfig script to /etc/sysconfig/glite-data-transfer-agents...
INFO: Linked SysV script from /opt/glite/etc/init.d/glite-data-transfer-agents to /etc/init.d/transfer-agents...
INFO: Ckconfig'd transfer-agents on ...
INFO: Writing logrotate script to /etc/logrotate.d/glite-data-transfer-agents ...
DEBUG: Closing VO paramters.
INFO: YAIM terminated succesfully.
--
GianniPucciani - 24-Feb-2010