Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod8 / bos_status.pod
CommitLineData
805e021f
CE
1=head1 NAME
2
3bos_status - Displays the status of server processes
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10S<<< B<bos status -server> <I<machine name>> >>> [-instance <I<server process name>>+]
11[B<-long>] S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>] [B<-help>]
12
13S<<< B<bos stat -s> <I<machine name>> >>> [-i <I<server process name>>+]
14[B<-lon>] S<<< [B<-c> <I<cell name>>] >>> [B<-n>] [B<-loc>] [B<-h>]
15
16=for html
17</div>
18
19=head1 DESCRIPTION
20
21The bos status command reports the status of processes on the
22server machine named by the B<-server> argument, either
23
24=over 4
25
26=item *
27
28All of the AFS server processes listed in the
29F</usr/afs/local/BosConfig> file
30
31=item *
32
33Only these processes named by the -instance argument
34
35=back
36
37=head1 OPTIONS
38
39=over 4
40
41=item B<-server> <I<machine name>>
42
43Indicates the server machine for which to report server process
44status. Identify the machine by IP address or its host name (either
45fully-qualified or abbreviated unambiguously). For details, see L<bos(8)>.
46
47=item -instance
48
49Names each process for which to report status. Use the process name
50assigned with the B<-instance> argument to the B<bos>
51command. The output from the B<bos status> command lists the
52names.
53
54=item -long
55
56Produces more detailed status information.
57
58=item B<-cell> <I<cell name>>
59
60Names the cell in which to run the command. Do not combine this
61argument with the B<-localauth> flag. For more details, see L<bos(8)>.
62
63=item B<-noauth>
64
65Assigns the unprivileged identity C<anonymous> to the
66issuer. Do not combine this flag with the B<-localauth>
67flag. For more details, see L<bos(8)>.
68
69=item B<-localauth>
70
71Constructs a server ticket using a key from the local
72F</usr/afs/etc/KeyFile> or F</usr/afs/etc/KeyFileExt> file. The B<bos> command
73interpreter presents the ticket to the BOS Server during mutual
74authentication. Do not combine this flag with the B<-cell> or
75B<-noauth> options. For more details, see L<bos(8)>.
76
77=item B<-help>
78
79Prints the online help for this command. All other valid options
80are ignored.
81
82=back
83
84=head1 OUTPUT
85
86The output for a process includes at least one line, which reports one of
87the following as the process's current status:
88
89=over 4
90
91=item *
92
93C<currently running normally>. The process's status
94flag in the B<BosConfig> file is C<Run>. For
95B<cron> entries, this message indicates only that the command is
96scheduled to run, not necessarily that it was executing when the B<bos
97status> command was issued.
98
99=item *
100
101C<disabled>. The process is not running, and its
102B<BosConfig> status flag is C<NotRun>.
103
104=item *
105
106C<temporarily disabled>. The process is not running
107although its status flag in the B<BosConfig> file is
108C<Run>. Either an administrator used the B<bos
109shutdown> command to stop it, or the
110
111=item *
112
113BOS Server stopped trying to restart it after numerous failed
114attempts. In the second case, the auxiliary message is C<stopped for
115too many errors>.
116
117=item *
118
119C<temporarily enabled>. The process is running although its
120status flag in the B<BosConfig> file is C<NotRun>. An
121administrator has used the B<bos startup> command to start it.
122
123=back
124
125If one of the following special circumstances applies to the process, the
126indicated message appears in its entry:
127
128=over 4
129
130=item *
131
132C<has core file>. The process failed and created a core
133file in the F</usr/afs/logs> directory. If the BOS Server was
134able to restart the process after the failure, the primary status is
135C<currently running normally>.
136
137=item *
138
139C<stopped for too many errors>. The reason for the primary
140status C<temporarily disabled> is that the BOS Server's attempts
141to restart the process all failed.
142
143=back
144
145The entry for the fs process always includes a second line to
146report the process's C<Auxiliary status>, which is one of the
147following:
148
149=over 4
150
151=item *
152
153C<file server running>. The File Server and Volume Server
154components of the File Server process are running normally.
155
156=item *
157
158C<salvaging file system>. The Salvager is running, so the
159File Server and Volume Server are temporarily disabled. The BOS Server
160restarts them as soon as the Salvager is finished.
161
162=back
163
164The entry for a cron process includes an C<Auxiliary
165status> that reports when the command will next execute.
166
167If the -long flag is used, each entry includes the following
168additional information:
169
170=over 4
171
172=item *
173
174The process's type (C<simple>, C<fs>, or
175C<cron>).
176
177=item *
178
179The day and time the process last started or restarted.
180
181=item *
182
183The number of C<proc starts>, which is how many times the BOS
184Server has started or restarted the process since it started itself.
185
186=item *
187
188The C<Last exit> time when the process (or one of the component
189processes in the B<fs> process) last terminated. This line does
190not appear if the process has not terminated since the BOS Server
191started.
192
193=item *
194
195The C<Last error exit> time when the process (or one of the
196component processes in the B<fs> process) last failed due to an
197error. A further explanation such as C<due to shutdown request>
198sometimes appears. This line does not appear if the process has not
199failed since the BOS Server started.
200
201=item *
202
203Each command that the BOS Server invokes to start the process, as
204specified by the B<-cmd> argument to the B<bos create>
205command.
206
207=item *
208
209The pathname of the notifier program that the BOS Server invokes when the
210process terminates (if any), as specified by the B<-notifier> argument
211to the B<bos create> command.
212
213=back
214
215If the -long flag is provided and the BOS Server discovers that
216the mode bits on files and subdirectories in the local F</usr/afs>
217directory differ from the expected values, it prints the following warning
218message:
219
220 Bosserver reports inappropriate access on server directories
221
222The following chart summarizes the expected mode bit settings. A
223question mark indicates that the BOS Server does not check that bit.
224
225=head1 EXAMPLES
226
227The following example command displays the status of processes on the
228machine B<fs3.example.com>:
229
230 % bos status fs3.example.com
231 Instance buserver, currently running normally.
232 Instance kaserver, currently running normally.
233 Instance ptserver, currently running normally.
234 Instance vlserver, currently running normally.
235 Instance fs, has core file, currently running normally.
236 Auxiliary status is: file server running.
237 Instance upserver, currently running normally.
238
239The following example command displays a detailed status report for the
240B<fs> and B<ptserver> processes on the machine
241B<fs1.example.com>.
242
243 % bos status -server fs1.example.com -instance fs ptserver -long
244 Instance fs, (type is fs), currently running normally.
245 Auxiliary status is: file server running.
246 Process last started at Wed Jan 7 5:34:49 1998 (3 proc starts)
247 Last exit at Wed Jan 7 5:34:49 1998
248 Last error exit at Wed Jan 7 5:34:49 1998, due to shutdown
249 request
250 Command 1 is '/usr/afs/bin/fileserver'
251 Command 2 is '/usr/afs/bin/volserver'
252 Command 3 is '/usr/afs/bin/salvager'
253 Instance ptserver, (type is simple) currently running normally.
254 Process last started at Tue Jan 6 8:29:19 1998 (1 proc starts)
255 Command 1 is '/usr/afs/bin/ptserver'
256
257=head1 PRIVILEGE REQUIRED
258
259None
260
261=head1 SEE ALSO
262
263L<BosConfig(5)>,
264L<KeyFile(5)>,
265L<KeyFileExt(5)>,
266L<bos(8)>,
267L<bos_create(8)>,
268L<bos_shutdown(8)>,
269L<bos_startup(8)>,
270L<bos_status(8)>
271
272=head1 COPYRIGHT
273
274IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
275
276This documentation is covered by the IBM Public License Version 1.0. It was
277converted from HTML to POD by software written by Chas Williams and Russ
278Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.