3 .\" Generator: DocBook XSL Stylesheets v1.72.0 <http://docbook.sf.net/>
8 .TH "AMCHECK" "8" "02/07/2007" "" ""
9 .\" disable hyphenation
11 .\" disable justification (adjust text to left margin only)
14 amcheck \- run Amanda self\-checks
17 \fBamcheck\fR [\-am] [\-w] [\-sclt] [\-M\ \fIaddress\fR] \fIconfig\fR [\fIhost\fR\ [\fIdisk\fR...]...] [\-o\ \fIconfigoption\fR]...
21 runs a number of self\-checks on both the
23 tape server host and the
27 On the tape server host,
29 can go through the same tape checking used at the start of the nightly
31 run to verify the correct tape for the next run is mounted.
34 can also do a self\-check on all client hosts to make sure each host is running and that permissions on filesystems to be backed up are correct.
36 You can specify many host/disk expressions, only disks that match an expression will be checked. All disks are checked if no expressions are given.
40 man page for more details about
46 Run the tape server local and tape checks (same as
52 Run the client host checks. Multiple specific clients can be checked by specifying the client name.
57 Run the local tests (e.g. permissions) on the server host.
62 Run the tape tests on the server host.
67 Enables a DESTRUCTIVE check for write\-protection on the tape (which would otherwise cause the subsequent
69 to fail). If the tape is writable, this check causes all data after the tape label to be erased. If the label_new_tapes option is enabled, this check may ERASE any non\-Amanda tape in the drive or changer. The check enable the tape tests on the server host and is only made if the tape is otherwise correct.
74 Nothing is printed, but mail is sent if any errors are detected. The mail goes to the
76 address specified in the
89 but the mail is always sent.
92 \fB\-M\fR \fIaddress\fR
99 \fIamanda.conf\fR. Implies
103 \fIhost\fR [\fIdisk\fR]*
105 Specify the host and disk on which the command will work.
108 \fB\-o\fR \fIconfigoption\fR
110 See the "\fBCONFIGURATION OVERWRITE\fR" section in
118 In this example, both the tape server and client tests are run. The results are displayed on standard output.
123 \fIAmanda\fR Tape Server Host Check
124 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
125 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
126 NOTE: skipping tape\-writable test.
128 Server check took 34.966 seconds.
130 \fIAmanda\fR Backup Client Hosts Check
131 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
132 WARNING: northstar: selfcheck request timed out. Host down?
133 WARNING: drinkme: selfcheck request timed out. Host down?
134 WARNING: scruffy: selfcheck request timed out. Host down?
135 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
137 (brought to you by \fIAmanda\fR 2.5.0)
141 In this example, if the line
142 \fBmailto csd\-amanda\fR
144 \fIamanda.conf\fR, mail will be sent to
146 if the server check returns an error.
150 % amcheck \-s \-m daily
155 fatal slot \fIslot\fR: \fIerror message\fR
157 (error) The tape changer detected some kind of fatal error while trying to load slot
161 slot \fIslot\fR: \fIerror message\fR
163 (warning) The tape changer detected some kind of non\-fatal error (e.g. an empty slot was detected) while trying to load slot
164 \fIslot\fR, or an error was detected trying to read the tape label.
167 slot \fIslot\fR: date \fIYYYYMMDD\fR label \fIlabel\fR (\fIresult\fR)
173 was loaded and found to have been last written on
174 \fIYYYYMMDD\fR. If the tape is new, the date field will be an
182 This is the expected tape.
187 This label does not match the
190 \fIamanda.conf\fR. Tape scanning will continue.
195 This tape is still active and cannot be overwritten. Tape scanning will continue.
200 This tape is the first one that matches the
203 \fIamanda.conf\fR. Tape scanning will continue if necessary.
208 This tape is the next one that matches the
211 \fIamanda.conf\fR. Tape scanning will continue.
217 ERROR: cannot look up dump user \fIuser\fR
223 could not be found in the system password information.
226 ERROR: cannot look up my own uid (\fIuid\fR)
232 could not be found in the system password information.
235 ERROR: running as user \fIrunuser\fR instead of \fIdumpuser\fR
239 should be run as the dump user
247 ERROR: program dir \fIdirectory\fR: not accessible
249 (error) The directory
251 expects to find its auxiliary programs in,
252 \fIdirectory\fR, is not accessible.
255 ERROR: program \fIprogram\fR: does not exist
259 needed on the tape server could not be found.
262 ERROR: program \fIprogram\fR: not a file
266 needed on the tape server exists but is not a file.
269 ERROR: program \fIprogram\fR: not executable
273 needed on the tape server exists but is not executable.
276 WARNING: program \fIprogram\fR: not setuid\-root
280 needed on the tape server exists but should be owned by user "root" and setuid.
283 ERROR: \fIXXX\fR dir \fIdirectory\fR: not writable
287 is either not writable, i.e. the dump user will not be able to create or remove files, or cannot be accessed, perhaps because a parent directory does not allow search permission. The
304 for the directory that holds the old log files (see
314 database information directory (see
317 \fBamanda.conf\fR) or
334 tapelist directory (see
343 NOTE: \fIXXX\fR dir \fIdirectory\fR: does not exist
345 (info) A database (info) or index directory does not exist or cannot be accessed. This might just mean this is a new client or disk, but if that is not the case, this should be treated as an error.
348 NOTE: it will be created on the next run
350 (info) This indicates the info directory listed in the previous message will be created on the next run.
353 ERROR: \fIXXX\fR dir \fIname\fR: not a directory
359 to be a directory, but it is something else (e.g. file).
362 WARNING: info file \fIfile\fR: does not exist
366 does not exist in the text format database. Since the parent directories do exist, the file should already have been created.
369 ERROR: info file \fIname\fR: not a file
375 to be a file, but it is something else (e.g. file).
378 ERROR: info file \fIfile\fR: not readable
380 (error) The text format database file
385 ERROR: log file \fIfile\fR: not writable
394 \fBamanda.conf\fR) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission.
397 ERROR: tape list \fItapelist\fR: not writable
406 \fBamanda.conf\fR) is not writable or was not found.
409 ERROR: tape list \fItapelist\fR: parse error
418 \fBamanda.conf\fR) could not be read or parsed.
421 WARNING: tapedev is /dev/null, dumps will be thrown away
431 uses that when debugging to throw all the dump images away.
434 WARNING: hold file \fIfile\fR exists
438 exists and will cause
440 to pause at the beginning until it is removed.
443 ERROR: holding disk \fIdisk\fR: statfs: \fIerror message\fR
445 (error) An error was returned from the
447 system call on holding disk
449 (maybe because it does not exist).
452 ERROR: holding disk \fIdisk\fR: not writable
455 \fIdisk\fR, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission.
458 WARNING: holding disk \fIdisk\fR: available space unknown \fIN\fR KB requested.
462 could not determine the amount of available space on holding disk
464 to see if there were at least
469 WARNING: holding disk \fIdisk\fR: only \fIF\fR KB free (\fIR\fR KB requested).
475 KBytes of free space on holding disk
478 KBytes were available. 10 MBytes is subtracted for each backup process (see the
481 option) to allow for unexpected overruns.
484 .nr an-no-space-flag 1
488 Even though this message is listed as a warning, it causes
490 to exit with a non\-zero status.
493 Holding disk \fIdisk\fR: \fIN\fR KB disk space available, that's plenty.
495 (info) There was sufficient free space on holding disk
499 WARNING: holding disk \fIdisk\fR: only \fIF\fR KB free, using nothing
501 (warning) Holding disk
505 KBytes of free space, but that is not enough for what is requested in
509 Holding disk \fIdisk\fR: \fIF\fR KB disk space available, using \fIU\fR KB
515 KBytes of free space and
522 WARNING: if a tape changer is not available, runtapes must be set to 1.
527 option must be set to 1 if the
533 ERROR: \fIerror message\fR.
535 (error) An error was detected while initializing the tape changer.
538 ERROR: \fItape device\fR: \fIerror message\fR.
540 (error) An error was detected while processing the tape label.
543 ERROR: cannot overwrite active tape \fIlabel\fR.
547 is still active and cannot be used.
550 ERROR: label \fIlabel\fR doesn't match labelstr \fIpattern\fR .
552 (error) The label on tape
560 (expecting a new tape)
562 (info) The tape is not OK and a new tape was expected.
565 (expecting tape \fIlabel\fR or a new tape)
567 (info) The tape is not OK and either tape
569 or a new tape was expected.
572 ERROR: tape \fIlabel\fR label ok, but is not writable.
576 is OK, but the write enable test failed.
579 Tape \fIlabel\fR is writable.
583 is OK and the write enable test succeeded.
586 NOTE: skipping tape\-writable test.
588 (info) The tape write test (see the
590 option) was not enabled.
593 WARNING: skipping tape test because amdump or amflush seem to be running, WARNING: if they are not, you must run amcleanup
595 (warning) It looked to
601 were running because a log file or amdump file exists. If they are not running, you probably need to run
603 to clear up a previous failure. Otherwise, you need to wait until they complete before running
607 NOTE: skipping tape checks
609 (info) The tape tests are being skipped because you used the
614 WARNING: \fIcompress\fR is not executable, server\-compression and indexing will not work
616 (warning) Compression program
618 is not executable, so compression on the tape server host and creating index files will not work.
621 Tape \fIlabel\fR label ok.
625 is OK for the next run.
628 Server check took \fIS\fR seconds.
630 (info) Reports how long the tape server host checks took.
633 ERROR: \fIhost\fR: could not resolve hostname
635 (error) Could not look up client hostname
639 Client check: \fIH\fR hosts checked in \fIS\fR seconds, \fIN\fR problems found.
641 (info) Reports the number of client hosts checked, how long it took and the number of errors detected.
644 WARNING: \fIhost\fR: selfcheck request timed out. Host down?
646 (warning) There was no response from
648 when trying to do the client checks. The host might really be down or it might not be configured properly.
651 ERROR: \fIhost\fR NAK: \fImessage\fR
655 reported a negative acknowledgment error of
657 to the status check request.
660 ERROR: \fIhost\fR NAK: [NAK parse failed]
664 could not parse the negative acknowledgment error from
665 \fIhost\fR. There might be an
667 version mismatch between the host running
673 ERROR: \fIhost\fR [mutual\-authentication failed]
675 (error) Kerberos authentication failed while contacting
679 ERROR: \fIhost\fR: \fImessage\fR
683 was reported by the status check on
692 Stefan G. Weichinger,
693 <sgw@amanda.org>, maintainer of the
694 \fIAmanda\fR\-documentation: XML\-conversion