Having no luck with fixing our dcache. I've tried switching the
spacemanager off as the error message reported to both ops and Peter
Love suggested that zero space was being reported:
lcg-cr -v --vo atlas -d fal-pygrid-20.lancs.ac.uk -l
lfn:/grid/atlas/users/plove/$rand file:///home/plove/bandwidth-10mb
Using grid catalog type: lfc
Using grid catalog : prod-lfc-atlas-central.cern.ch
Using LFN : /grid/atlas/users/plove/pal-29340
Using SURL :
srm://fal-pygrid-20.lancs.ac.uk/pnfs/lancs.ac.uk/data/atlas/generated/2008-01-17/file213c24c0-8489-4a6b-bc39-cd864a6e7202
httpg://fal-pygrid-20.lancs.ac.uk:8443/srm/managerv1: at Thu Jan 17
23:22:04 GMT 2008 state Pending : created
RequestFileStatus#-2143893561 failed with error:[ at Thu Jan 17
23:22:05 GMT 2008 state Failed : no space available]
lcg_cr: Communication error on send
Files can be copied out without error, and I successfully copied files
in using globus-url-copy, it's lcg-cr and srmcpPuts that fail. Lcg-cr
seems screwed for me due to different issues (I get a No User Mapping
error, but I'm dteam and not atlas).
I had enabled the SpaceManager but foolishly not enabled any space
tokens, so this might have been my downfall. After disabling the
SpaceManager however our ops tests are failing with the error message:
state Failed : SpaceManager is disabled in configuration
Maybe I missed something in my dcachesetup,
Matt
On 17/01/2008, Greig Alan Cowan <[log in to unmask]> wrote:
> Hi Matt,
>
> You are failing ops tests at the moment. Can you investigate? Looks like
> it might be related to your dCache upgrade to 1.8.0-12. Did everything
> come back OK?
>
> Greig
>
|