Sergio Gelato <[EMAIL PROTECTED]> writes: > * AFSDB: I added a record to my DNS before running afs-newcell. This > may be why I didn't run into the "can't find cell '<default>'" issue. > It would be nice to mention AFSDB records in the setup instructions, > but I don't think they should be an absolute requirement for > afs-newcell to work.
Do you have your new cell listed in /etc/openafs/CellServDB? You have to have it listed there if AFSDB records are not used. I've clarified the instructions, telling people to run dpkg-reconfigure openafs-client if the client was previously configured for another cell. The configuration process of openafs-client will add the entry if it's not already present. I also added documentation on setting up AFSDB records. > * my new cell name (test.astro.su.se) didn't match my Kerberos realm > name (ASTRO.SU.SE). Apart from the insufficiently documented need to > echo ASTRO.SU.SE > /etc/openafs/server/krb.conf > this doesn't seem to invalidate anything in afs-newcell, which is nice. I've added documentation of this. > The brackets around the IP address caused my server to lose the > election, so "vos create" later on in afs-newcell would fail. > Hand-editing /etc/openafs/server/CellServDB solved the problem, > as it did for Faheem. > I wonder if using > server=`hostname -f` > in afs-newcell instead of > server=`hostname` > would help. I have afs-newcell just generating the server CellServDB itself now. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
