On Friday, October 27, 2006 03:41:24 PM +0300 Juha Jäykkä <[EMAIL PROTECTED]> wrote:
It seemed to me as if openafs servers thought there are two distinct servers: the one with the old ip and the one with the new. It never seemed to occur to openafs that they were indeed the same server. (Would it even be possible? I mean, how could it tell?)
As a matter of fact, it can tell. Each server has an identifier (UUID), and registers its addresses with the VLDB on every startup. So, if all you are doing is renumbering an existing server, just change the address and restart it - the rest will happen automatically.
The problems occur when you use 'vos changeaddr' inappropriately, or if the VLDB already thinks there is a server at the new address. In the latter case, it won't let the fileserver register the new address, because it belongs to some other server. In current versions of OpenAFS, this should prevent the fileserver from starting, and result in log messages in both the fileserver and vlserver logs. You can correct the problem by using 'vos changeaddr -delete' to remove the existing server entry for the _new_ address, and then restarting the fileserver to let it re-register.
-- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
