Hi,
At the moment we believe that there must be a space token mis-configuration at Manchester, and that this is not an FTS3 bug. E.g.:
lcg-stmd -be httpg://bohr3226.tier2.hep.manchester.ac.uk:8446/srm/managerv2 -s ATLASDATADISK
[SE][GetSpaceTokens][SRM_INVALID_REQUEST] httpg://bohr3226.tier2.hep.manchester.ac.uk:8446/srm/managerv2: dpm_getspacetoken: Unknown user space token description
lcg_stmd: Invalid argument
Regards,
Andrew.
-----Original Message-----
From: Testbed Support for GridPP member institutes [mailto:[log in to unmask]] On Behalf Of Alessandra Forti
Sent: 22 November 2012 18:36
To: [log in to unmask]
Subject: Re: FTS3 and StoRM don't work if you use spacetokens.
Manchester is not liking the functional tests either since RAL has come back. It claims there is no space left in DATADISK but there are 37TB and I could copy a couple of test files myself. Other activities seem fine.
On 22/11/2012 18:28, Christopher J. Walker wrote:
> Brian has carried out some FTS3 tests against QMUL's StoRM SEs.
>
> It would appear that it's a StoRM bug:
>
> https://ggus.eu/tech/ticket_show.php?ticket=88607
>
> says:
>
> "This is a StoRM bug. A fix will be released as an Update of StoRM EMI
> 2 released within EMI 2 Update 8 on 24.01.2013 No updates for EMI 1
> (21.8.X) will be provided, see http://www.eu-emi.eu/releases#MajRel
>
> As workaround simply do not specify the token in the request"
>
> Chris
--
Facts aren't facts if they come from the wrong people. (Paul Krugman)
--
Scanned by iCritical.
|