[AG-TECH] Private Registry Peer

[Gabriel Noronha]

Thanks for that Chris 

I got it working... --help doesn't really give enough information sometimes to work it out yourself. 

Gabriel 

>>> Christoph Willing <c.willing at uq.edu.au> 5/08/2010 2:44 pm >>>

On 05/08/2010, at 1:45 PM, Gabriel Noronha wrote:

> Trying to run my own Peer Registry
>
> currently getting errors  like the following
>
> Traceback (most recent call last):
>  File "/usr/bin/RegistryPeer", line 218, in <module>
>    main()
>  File "/usr/bin/RegistryPeer", line 213, in main
>    r = RegistryPeer(peerListUrl=peerListUrl, port=port)
>  File "/usr/bin/RegistryPeer", line 159, in __init__
>    RegistryBase.__init__(self, port, peerListUrl)
>  File "/usr/bin/RegistryPeer", line 52, in __init__
>    self._readPeerList(url=self.peerListUrl)
>  File "/usr/bin/RegistryPeer", line 67, in _readPeerList
>    raise Exception ("Error: this peer " + localPeerName + " is not  
> listed in the master list.  The current registry requires all peers  
> to know about each other.")
> Exception: Error: this peer cv206-agr3.newcastle.edu.au:8030 is not  
> listed in the master list.  The current registry requires all peers  
> to know about each other.
>
>
> I can't find anything about a master list ?


Gabriel,

The master list is where your registry is advertised and it should  
include the name of the machine you're running the registry on (cv206- 
agr3...). When you start the RegistryPeer, it checks that the service  
its going to provide will be suitably advertised. You can see in the  
traceback that the trouble starts when trying to load some peerListUrl  
- my guess is that you didn't provide such a url when you started  
RegistryPeer. You need to do that with the -u option. Without that, it  
probably defaults to looking at ANL's master list at:
     http://www.accessgrid.org/registry/peers.txt 
which doesn't include your registry. What that url shows is the name  
of a machine and the port number at which its registry service can be  
contacted. In this case, its running on the machine vv3.mcs.anl.gov at  
port 8030.

What you need to do is create a similar entry, referencing your cv206- 
agr3 machine, on a web server somewhere. Then pass the url of that  
entry (your peerlist url) to the RegistryPeer at startup using the -u  
option.

BTW, its that same peerlist url that applications use to find your  
registry. In the case AG VenueClients, they know to look up any url(s)  
via entries in the Tools/Preferences/Bridging tab. Anyone wanting to  
use your registry will have to add you peerlist url to the "Bridge  
Registries" section at that tab (and remember to Save after adding).


chris


Christoph Willing                       +61 7 3365 8316
QCIF Access Grid Manager
University of Queensland