> > That seems a little odd; is it only ptserver that fails? Try these, to > check each individual server: > > bosserver: bos status <server> -localauth > vlserver: vos listaddrs -noresolv -localauth > ptserver: pts listmax -localauth > buserver: backup listhosts -localauth > > It looks like all three servers are unhappy, despite what bos status thinks:
# bos status localhost -localauth Instance buserver, currently running normally. Instance vlserver, currently running normally. Instance ptserver, currently running normally. # vos listaddrs -noresolve -localauth vos: could not list the server addresses Possible communication failure # pts listmax -localauth pts: server or network not responding getting maximum user id # backup listhosts -localauth backup: server or network not responding ; Can't access backup database backup: server or network not responding ; Can't initialize backup > I guess you don't have any fileservers up yet, but if you did, you could > check volserver via: > > volserver: vos listpart <server> -localauth > > If doing that still shows only ptserver as failing, maybe try getting a > packet trace while trying to run the 'pts' command, and sharing that > privately. For pts, just capture udp port 7002. (If you want to capture > traffic for others, you can just get all udp traffic to be sure.) > > > > Can you show the contents of rxkad.keytab? Not the keys, obviously; > > > just what the principals and enctypes are. > > > > Sure thing: > > > > Vno Type Principal Aliases > > 2 aes256-cts-hmac-sha1-96 afs/[email protected] > > 2 des3-cbc-sha1 afs/[email protected] > > 2 arcfour-hmac-md5 afs/[email protected] > > That's fine. > > -- > Andrew Deason > [email protected] > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Eric Shell
