[Ibergrid-support] [IBERGRID-SUPPORT #301] [Comment] lcg-cr:Registration failed
Pablo Orviz Fernandez via IBERGRID-RT
helpdesk-ibergrid-comment at rediris.es
Fri May 31 12:04:56 CEST 2013
https://rt-ngi.rediris.es/Ticket/Display.html?id=301
This is a comment. It is not sent to the Requestor(s):
Hi Esteban,
just to give an answer to Susana, could this ibergrid-support list made public?
Thanks,
Pablo.
On Thu May 23 11:43:33 2013, Goncalo Borges wrote:
> Hi Susana...
>
> These emails are under ibergrid-support mailing list but I think the
> archives are not public.
>
> Maybe we can debate about this.
>
> Cheers
> Goncalo
>
> On 05/22/2013 06:59 PM, sse at iaa.es via IBERGRID-RT wrote:
> > <URL: https://rt-ngi.rediris.es/Ticket/Display.html?id=301 >
> >
> > Thanks Gonçalo,
> >
> > And sorry for the silly question, I didn't realized that I was
> uploading
> > the same file, sorry.
> >
> > But, anyway, this mail is very helpful for me, now I clearly
> understand
> > the lcg-cp, lcg-cr commands.
> >
> > I was wondering if there is any place where the mails sent to the
> help-desk
> > are publicly available. It could be very useful to check if your
> question
> > has been answered before, so you can save time
> >
> > Thanks again
> > Susana
> >
> >
> > 2013/5/22 Goncalo Filipe Mauricio dos Santos Borges via IBERGRID-RT
> <
> > helpdesk-ibergrid at rediris.es>
> >
> >> Hi Susana...
> >>
> >> >From what I'm able to check, the registration of the file failed
> because
> >> there
> >> is already a file registered in the LFC with the same name (from
> the 17th
> >> of
> >> March)
> >>
> >> $ lfc-ls -l /grid/phys.vo.ibergrid.eu/susana/NGC7331MOM2D.descr
> >> -rw-rw-r-- 1 188 133 12288 May 17 08:33
> >> /grid/phys.vo.ibergrid.eu/susana/NGC7331MOM2D.descr
> >>
> >> Now some clarifications regarding the copy and registering of
> files:
> >>
> >> 1) lcg-CR means "COPY a file to a SE and REGISTER it in the LFC".
> The
> >> syntax is
> >> as follows, and if you do not provide the "-d <SE>" option, it will
> simply
> >> use
> >> the closest defined SE which I guess in your case is the IFCA SE.
> >>
> >> $ lcg-cr -v --vo phys.vo.ibergrid.eu -d srm01.lip.pt -l
> >> lfn:/grid/phys.vo.ibergrid.eu/gborges/test-`date +%s`.txt
> >> file:///home/hpc/goncalo/teste.txt
> >> Using grid catalog type: lfc
> >> Using grid catalog : lfc01.ncg.ingrid.pt
> >> Checksum type: None
> >> SE type: SRMv2
> >> Destination SURL :
> >> srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> Source SRM Request Token: 10b60df6-dc44-41d5-82ee-21ab03de9604
> >> Source URL: file:/home/hpc/goncalo/teste.txt
> >> File size: 427667
> >> VO name: phys.vo.ibergrid.eu
> >> Destination specified: srm01.lip.pt
> >> Destination URL for copy:
> >> gsiftp://
> >> gftp03.lip.pt:2811//lustre/lip.pt/data/physiber//generated/2013-05-
> 22/file65ee2e42-a1e2-4365-9b17-be1529f888ad
> >> # streams: 1
> >> 427667 bytes 1886.81 KB/sec avg 1886.81 KB/sec inst
> >> Transfer took 1120 ms
> >> Using grid catalog type: lfc
> >> Using grid catalog : lfc01.ncg.ingrid.pt
> >> Site URL to be registered:
> >> srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> File size: 427667
> >> Using LFN: lfn:/grid/phys.vo.ibergrid.eu/gborges/test-
> 1369240627.txt
> >> Using GUID: guid:746a42ee-e469-4c90-b4bc-8886980456e5
> >> Registering LFN: /grid/phys.vo.ibergrid.eu/gborges/test-
> 1369240627.txt
> >> (746a42ee-e469-4c90-b4bc-8886980456e5)
> >> Registering SURL:
> >> srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> (746a42ee-e469-4c90-b4bc-8886980456e5)
> >> guid:746a42ee-e469-4c90-b4bc-8886980456e5
> >>
> >> So, the file is identified in the SE by a SURL
> >> (srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> ) and in the LFC by a LFN
> >> (/grid/phys.vo.ibergrid.eu/gborges/test-1369240627.txt)
> >>
> >>
> >> 2) Sometimes, by a network problem or similar, while doing a lcg-
> CR, the
> >> registration fails but the copy suceeds. That was what happen in
> your
> >> case. You
> >> can then register the file by hand using the comand lcg-rf. The
> comand to
> >> execute in such cases is
> >>
> >> lcg-rf -v --vo <VO> -l lfn:<LFN> <SURL>
> >>
> >> For my example above, and if the original registration failed, I
> could
> >> issue
> >> the following command (don't forget that LFN as to be unique)
> >>
> >> $ lcg-rf -v --vo phys.vo.ibergrid.eu -l
> >> lfn:/grid/phys.vo.ibergrid.eu/gborges/test-1369240627.txt
> >> srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> Using grid catalog type: lfc
> >> Using grid catalog : lfc01.ncg.ingrid.pt
> >> Site URL to be registered:
> >> srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> File size: 427667
> >> Using LFN: lfn:/grid/phys.vo.ibergrid.eu/gborges/test-
> 1369240627.txt
> >> Using GUID: guid:54b1fb6f-145c-46c6-825f-f988cd9e1e81
> >> Registering LFN: /grid/phys.vo.ibergrid.eu/gborges/test-
> 1369240627.txt
> >> (54b1fb6f-145c-46c6-825f-f988cd9e1e81)
> >> Registering SURL:
> >> srm://
> >> srm01.lip.pt/physiber/generated/2013-05-22/file65ee2e42-a1e2-4365-
> 9b17-be1529f888ad
> >> (54b1fb6f-145c-46c6-825f-f988cd9e1e81)
> >> guid:54b1fb6f-145c-46c6-825f-f988cd9e1e81
> >>
> >> Hope it is clear now
> >> Cheers
> >> Goncalo
> >>
> >
> >
>
>
More information about the Ibergrid-support
mailing list