Hello,
You were right. I re-run configure_node and I got:
...
Configuring config_DPM_upgrade
INFO Checking for database schema version...
INFO Database version used: 2.2.0
INFO Upgrading database schema from 2.2.0 to 3.0.0 !
INFO: Stopping DPM services.
...
Tue Apr 3 22:59:19 2007 : Starting to update the DPNS/DPM database.
Please wait...
Tue Apr 3 23:00:37 2007 : The update of the DPNS/DPM database is over
db vendor = MySQL
db = localhost
DPNS database user = dpmuser
DPNS database password = **********
DPNS database name = cns_db
DPM database name = dpm_db
INFO Schema version upgrade: Now, may you see the "Duplicate key name
'G_PFN_IDX' at UpdateDpmDatabase.pm" error message, it is harmless. The
indexes are already created.
...
Also mysql shows:
mysql> select * from cns_db.schema_version;
+-------+-------+-------+
| major | minor | patch |
+-------+-------+-------+
| 3 | 0 | 0 |
+-------+-------+-------+
1 row in set (0.00 sec)
mysql> select * from dpm_db.schema_version;
+-------+-------+-------+
| major | minor | patch |
+-------+-------+-------+
| 3 | 0 | 0 |
+-------+-------+-------+
1 row in set (0.00 sec)
I think that it's ok now.
Cheers,
George
-----Original Message-----
From: LHC Computer Grid - Rollout [mailto:[log in to unmask]]
On Behalf Of Sophie Lemaitre
Sent: Tuesday, April 03, 2007 4:25 PM
To: [log in to unmask]
Subject: Re: [LCG-ROLLOUT] TURL expired
You really need to run the migration script to support SRMv2.2, and have the
DPM database schema updated as needed.
It is not enough to have the SAM test pass...
Please re-run the YAIM ./configure_node and send us the output.
Thank you.
Sophie
>The test is now ok. I think that DEFPINTIME was the problem.
>
>Thanks for your time,
>George
>
>-----Original Message-----
>From: LHC Computer Grid - Rollout
>[mailto:[log in to unmask]]
>On Behalf Of Sophie Lemaitre
>Sent: Tuesday, April 03, 2007 4:08 PM
>To: [log in to unmask]
>Subject: Re: [LCG-ROLLOUT] TURL expired
>
>that was the meaning of my question ;-) but thanks for the translation
>! :-)))
>
>
>
>>What is the YAIM output ?
>>Gergo
>>
>>Sophie Lemaitre wrote:
>>
>>
>>
>>>Hum, then, there must have been an error during configuration. What
>>>was it ?
>>>
>>>If you don't have it anymore, can you please try to configure it again ?
>>>Please take a backup of the database beforehand.
>>>
>>>Thank you.
>>>Sophie.
>>>
>>>
>>>
>>>>I ran configure_node after the upgrade as mentioned at
>>>>http://glite.web.cern.ch/glite/packages/R3.0/deployment/glite-SE_dpm
>>>>_mysql/g
>>>>
>>>>lite-SE_dpm_mysql.asp and our cluster is not in apt-get auto update
>>>>mode.
>>>>
>>>>Cheers,
>>>>George
>>>>-----Original Message-----
>>>>From: LHC Computer Grid - Rollout
>>>>[mailto:[log in to unmask]]
>>>>On Behalf Of Sophie Lemaitre
>>>>Sent: Tuesday, April 03, 2007 3:26 PM
>>>>To: [log in to unmask]
>>>>Subject: Re: [LCG-ROLLOUT] TURL expired
>>>>
>>>>You haven't run the "./configure_node" apparently after the upgrade.
>>>>Please do it.
>>>>
>>>>It was explicitely mentioned that the DPM upgrade needed a
>>>>reconfiguration in the gLite release notes. See:
>>>>http://glite.web.cern.ch/glite/packages/R3.0/updates.asp
>>>>
>>>>Let me remind everybody that *it is not recommended to run the LFC
>>>>and DPM services in an apt-get auto update mode* (not sure if it is
>>>>your case
>>>>though...)
>>>>
>>>>Cheers, Sophie.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>1) Done (thanks)
>>>>>
>>>>>2)
>>>>># rpm -qa | grep DPM
>>>>>DPM-rfio-server-1.6.3-1sec
>>>>>DPM-gridftp-server-1.6.3-1sec
>>>>>DPM-srm-server-mysql-1.6.3-1sec
>>>>>DPM-server-mysql-1.6.3-1sec
>>>>>DPM-client-1.6.3-1sec
>>>>>DPM-name-server-mysql-1.6.3-1sec
>>>>>
>>>>># rpm -qa | grep glite-yaim
>>>>>glite-yaim-3.0.0-38
>>>>>
>>>>>
>>>>>mysql> select * from cns_db.schema_version; select * from
>>>>>dpm_db.schema_version;
>>>>>+-------+-------+-------+
>>>>>| major | minor | patch |
>>>>>+-------+-------+-------+
>>>>>| 2 | 2 | 0 |
>>>>>+-------+-------+-------+
>>>>>1 row in set (0.01 sec)
>>>>>
>>>>>+-------+-------+-------+
>>>>>| major | minor | patch |
>>>>>+-------+-------+-------+
>>>>>| 2 | 2 | 0 |
>>>>>+-------+-------+-------+
>>>>>1 row in set (0.01 sec)
>>>>>
>>>>>Thanks for your time,
>>>>>George
>>>>>
>>>>>-----Original Message-----
>>>>>From: LHC Computer Grid - Rollout
>>>>>[mailto:[log in to unmask]]
>>>>>On Behalf Of Sophie Lemaitre
>>>>>Sent: Tuesday, April 03, 2007 3:13 PM
>>>>>To: [log in to unmask]
>>>>>Subject: Re: [LCG-ROLLOUT] TURL expired
>>>>>
>>>>>1) You can use "dpm-modifypool" (see "man dpm-modifypool").
>>>>>
>>>>>For instance, for 2 hours :
>>>>>$ dpm-modifypool --poolname dpmpool --def_pintime 7200
>>>>>
>>>>>2) But I am surprised that this is not already set. The migration
>>>>>scripts to DPM 1.6.3 should have set it for you.
>>>>>
>>>>>Can you please do:
>>>>>$ rpm -qa | grep DPM
>>>>>$ rpm -qa | grep glite-yaim
>>>>>
>>>>>And in MySQL:
>>>>>mysql> select * from cns_db.schema_version; select * from mysql>
>>>>>dpm_db.schema_version;
>>>>>
>>>>>Thanks a lot.
>>>>>Sophie.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hello,
>>>>>>
>>>>>>1) glite-SE_dpm_mysql-3.0.14-1
>>>>>>
>>>>>>2) You are right about DEFPINTIME, it is 0, but I haven't changed
>>>>>>it. How can I configure DEFPINTIME to 2h?
>>>>>>
>>>>>># dpm-qryconf
>>>>>>POOL dpmpool DEFSIZE 10.00M GC_START_THRESH 0 GC_STOP_THRESH 0
>>>>>>DEF_LIFETIME 7.0d DEFPINTIME 0 MAX_LIFETIME 1.0m MAXPINTIME 12.0h
>>>>>>FSS_POLICY maxfreespace GC_POLICY lru RS_POLICY fifo GID 0 S_TYPE
>>>>>>-
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>MIG_POLICY none RET_POLICY R
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> CAPACITY 2.69T FREE 2.51T ( 93.6%)
>>>>>>se01.kallisto.hellasgrid.gr /data01 CAPACITY 1.34T FREE 1.25T (
>>>>>>93.5%)
>>>>>>se01.kallisto.hellasgrid.gr /data02 CAPACITY 1.34T FREE 1.26T (
>>>>>>93.8%)
>>>>>>
>>>>>>Cheers,
>>>>>>George
>>>>>>
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: LHC Computer Grid - Rollout
>>>>>>[mailto:[log in to unmask]]
>>>>>>On Behalf Of Sophie Lemaitre
>>>>>>Sent: Tuesday, April 03, 2007 2:52 PM
>>>>>>To: [log in to unmask]
>>>>>>Subject: Re: [LCG-ROLLOUT] TURL expired
>>>>>>
>>>>>>Hello,
>>>>>>
>>>>>>As far as I can see from the Information System, you are using a
>>>>>>DPM storage element.
>>>>>>
>>>>>>Between the time lcg_util got the TURL, and the time it tried to
>>>>>>use it, the TURL expired.
>>>>>>
>>>>>>1) Which version of the DPM are you running ?
>>>>>>
>>>>>>2) Can you please issue a "dpm-qryconf" ?
>>>>>>
>>>>>>The "DEFPINTIME" parameter corresponds to the TURL lifetime.
>>>>>>By default, it is 2 hours, but you might have configured your DPM
>>>>>>otherwise (like 0...)
>>>>>>
>>>>>>Cheers, Sophie.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hello all,
>>>>>>>
>>>>>>>The last few days our site (HG-04-CTI-CEID) is in error state at
>>>>>>>SAM tests because of CE-sft-lcg-rm.
>>>>>>>We get in srmv1/log the next error:
>>>>>>>srmv1: SRM02 - soap_serve error : TURL expired
>>>>>>>
>>>>>>>The sft-lcg-rm-cr.txt error writes ...
>>>>>>>instTURL expired
>>>>>>>...
>>>>>>>lcg_cr: Transport endpoint is not connected ...
>>>>>>>Setting SRM transfer to 'done' failed: Unregistering alias from
>>>>>>>catalog.+ result=1 ...
>>>>>>>
>>>>>>>Have you any idea what to check next?
>>>>>>>
>>>>>>>Thanks in advance,
>>>>>>>George Stathakopoulos
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
|