> On Tuesday 19 July 2005 15:59, William Hay wrote:
>
> > The reference to LRC &RMC URL's on the Testzone page
> > (http://www.gridpp.ac.uk/deployment/testzone/) were removed today at
> > 12:22.
>
> Hi William
>
> Those servers have not been running for a while (the machines were recycled
> into dCache test nodes, DPM servers and all manner of stuff as the testzone
> was unused at that time). Apologies for not having deleted them earlier.
>
> I have setup a pre-2.6.0 dteam LFC server today on grid08.ph.gla.ac.uk,
> however there are problems with the information publishing - I have a
> corrupt /opt/lcg/var/gip/lcg-info-generic.conf file. Until I can track down
> why this is happening you'd have to use another file catalog.
How do I configure a machine to use a particular file catalogue?
>
> What I can see at the moment is:
>
> grid05:~$ export LCG_GFAL_INFOSYS=lxn1189.cern.ch:2170
> grid05:~$ lcg-infosites --vo dteam lrc
> LRC endpoint for dteam:
> http://lcg01.sinp.msu.ru:8080/rdteam/edg-local-replica-catalog/services/edg-local-replica-catalo
> g
> grid05:~$ lcg-infosites --vo dteam rmc
> RMC endpoint for dteam:
> http://lcg01.sinp.msu.ru:8080/rdteam/edg-replica-metadata-catalog/services/edg-replica-metadata-
> catalog
Setting LCG_GFAL_INFOSYS as above gets lcg-infosites to produce the same information as above
(which is the same as on my production CE) but if I try lcg-cr I still get:
-bash-2.05b$ LCG_GFAL_INFOSYS=lxn1189.cern.ch:2170 lcg-cr -v --vo gridpp -l testFile.UCLSGE.txt.`date +%m.%d.%y:%H:%M:%S` -d se-a.ccc.ucl.ac.uk file://`pwd`/testFile.UCLSGE.txt
Using grid catalog type: edg
LRC endpoint not found
RMC endpoint not found
lcg_cr: Invalid argument
I've checked the gocwiki at :
http://goc.grid.sinica.edu.tw/gocwiki/lcg_cr%3a_Invalid_argument
Of the various items listed under diagnosis:
1.se-a.ccc.ucl.ac.uk is a valid hostname
2.LCG_GFAL_INFOSYS normally has the value gfe01.hep.ph.ic.ac.uk:2170 which looks to be good.
However I still have problems when using the lxn1189 value above as used on my working
production system.
3.The se is available and works when files are copied to it from the production site.
4.se-a is referenced in both production and test-zone BDII.
5.The message "SE type not found" is not printed.
William
|