[OpenAFS] Problems configuring the top level of the AFS filespace

Woodman, Joel woodman@chuma1.cas.usf.edu
Mon, 3 Mar 2003 12:50:59 -0500


I've reached the point in the OpenAFS installation where I configure the top
level of the AFS filespace, and've gotten the following error:

# fs setacl /afs system:anyuser rl
fs: Invalid argument; it is possible that /afs is not in AFS.

According to some of the comments I've read elsewhere this problem is
associated with the OpenAFS client, however I'm reasonably certain I've
installed it, on account of having installed and enabled it. Here's my
package list:


And here I've enabled the client in /etc/sysconfig/afs:

# AFS_CLIENT and AFS_SERVER determine if we should start the client and or
# the bosserver. Possible values are on and off.

So, what am I missing?

Now, I'm having another problem that may or may not be associated with this:

# bos status -server XXXXXXX.cas.usf.edu
Instance buserver, currently running normally.
Instance ptserver, currently running normally.
Instance vlserver, currently running normally.
Instance kaserver, currently running normally.
Instance fs, currently running normally.
    Auxiliary status is: file server running.
Instance upserver, currently running normally.
Instance runntp, temporarily disabled, stopped for too many errors,
currently shutdown.

/usr/afs/bin/runntp doesn't exist in /usr/afs/bin, and hasn't been installed
elsewhere on the system.

I used the following option to configure time services:

 ./bos create  XXXXXXX.cas.usf.edu runntp simple  \ 
        "/usr/afs/bin/runntp -localclock"  -cell cas.usf.edu  -noauth

This didn't work, since, well, no runntp.

For the record, this is a RedHat 8.0 system, running the 2.4.18-24.8.0
kernel and OpenAFS 1.2.8. It is intended to be the first system in the cell.