On Tue, 18 Jan 2011 03:49:32 +0100 Jaap Winius <[email protected]> wrote:
> If this is all because of DNS, what should I do? Both AFS servers also > run Bind9 with split views -- internal and external. Each AFS server > sees an internal view that includes its private IP address. > > Perhaps I should simply associate each server's internal address with > a different name. That way, the current names of the servers will only > be associated with their public IP addresses -- both internally and > externally. If DNS is causing these problems, I think this will fix it. If you're giving "vos addsite" a server name that resolves to an internal IP, well, there you go. You can have the fileserver set up completely correctly, but if you tell AFS 'vos addsite 192.168.1.1', it's going to add 192.168.1.1 as a site. "vos" doesn't have a way of knowing that 192.168.1.1 is really 128.2.200.90 or whatever address, if you've configured the fileserver to not advertsie the internal address. Giving the internal and external address different names would help, but it's still up to you to use the correct ones. If we gave the volserver a "what is your UUID?" RPC, we could get around this by having 'vos' look up the server addresses by UUID in the VLDB. But that's not how it is now. -- Andrew Deason [email protected] _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
