To display the status of the AFS server processes on a server machine, issue the bos status command. Adding the -long flag displays most of the information from each process's entry in the BosConfig file, including its type and command parameters. It also displays a warning message if the mode bits on files and subdirectories in the /usr/afs directory do not match the expected values.
Issue the bos status command.
% bos status <
machine name> [<
server process name>+] [-long]
Is the shortest acceptable abbreviation of status.
Specifies the file server machine for which to display process status.
Names each process for which to display status, using the name assigned when its entry was defined with the bos create command. Omit this argument to display the status of all server processes.
Displays, in addition to status, information from the process's entry in the BosConfig file: its type, its status flag, its command parameters, the associated notifier program, and so on.
The output includes an entry for each process and uses one of the following strings to indicate the process's status:
currently running normally indicates that the process is running and its status
flag in the BosConfig file is
Run. For cron entries,
this message indicates that the command is still scheduled to run, not necessarily that it is actually running when the
bos status command was issued.
temporarily enabled indicates that the process is running but that its status
flag in the BosConfig file is
NotRun. The most common
reason is that a system administrator has used the bos startup command to start the
temporarily disabled indicates that the process is not running even though its
status flag in the BosConfig file is
Run. The most
common reasons are either that a system administrator has used the bos shutdown command
to stop the process or that the BOS Server ceased trying to restart the process after numerous failed attempts. In the
latter case, a supplementary message appears:
stopped for too many errors.
disabled indicates that the process is not running and that its status flag in the BosConfig file is
NotRun. The BOS Server is not monitoring the
process. Only a system administrator can set the flag this way; the BOS Server never does.
The output for the fs process always includes a message marked
Auxiliary status, which can be one of the following:
file server running indicates that the File Server and Volume Server components
of the File Server process are running normally.
salvaging file system indicates that the Salvager is running, which usually
implies that the File Server and Volume Server are temporarily disabled. The BOS Server restarts them as soon as the
Salvager is finished.
The output for a cron process also includes an
Auxiliary status message to report when
the command is scheduled to run next; see the example that follows.
The output for any process can include the supplementary message
has core file to
indicate that at some point the process failed and generated a core file in the /usr/afs/logs
directory. In most cases, the BOS Server is able to restart the process and it is running.
The following example includes a user-defined cron entry called backupusers:
% bos status fs3.example.com Instance kaserver, currently running normally. Instance ptserver, currently running normally. Instance vlserver, has core file, currently running normally. Instance buserver, currently running normally. Instance fs, currently running normally. Auxiliary status is: file server running. Instance upserver, currently running normally. Instance backupusers, currently running normally. Auxiliary status is: run next at Mon Jun 7 02:00:00 1999.
If you include the -long flag to the bos status command, a process's entry in the output includes the following additional information from the BosConfig file:
The process's type (
The day and time the process last started or restarted.
The number of
proc starts, which is how many times the BOS Server has started or
restarted the process since it started itself.
Last exit time when the process (or one of the component processes in the
fs process) last terminated. This line does not appear if the process has not
terminated since the BOS Server started.
Last error exit time when the process (or one of the component processes in
the fs process) last failed due to an error. A further explanation such as
due to shutdown request sometimes appears. This line does not appear if the process has
not failed since the BOS Server started.
Each command that the BOS Server invokes to start the process, as specified by the -cmd argument to the bos create command.
The pathname of the notifier program that the BOS Server invokes when the process terminates (if any), as specified by the -notifier argument to the bos create command.
In addition, if the BOS Server has found that the mode bits on certain files and directories under /usr/afs deviate from what it expects, it prints the following warning message:
Bosserver process reports inappropriate access on server directories
The expected protections for the directories and files in the /usr/afs directory are as follows. A question mark indicates that the BOS Server does not check the mode bit. See the OpenAFS Quick Beginnings for more information about setting the protections on these files and directories.
The following illustrates the extended output for the fs process running on the machine fs3.example.com:
% bos status fs3.example.com fs -long Instance fs, (type is fs), currently running normally. Auxiliary status is file server running Process last started at Mon May 3 8:29:19 1999 (3 proc starts) Last exit at Mon May 3 8:29:19 1999 Last error exit at Mon May 3 8:29:19 1999, due to shutdown request Command 1 is '/usr/afs/bin/fileserver' Command 2 is '/usr/afs/bin/volserver' Command 3 is '/usr/afs/bin/salvager'