3 .\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
8 .TH "AMCHECK" "8" "08/22/2008" "" ""
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 OVERRIDE\fR" section in
118 In this example, both the tape server and client tests are run\. The results are displayed on standard output\.
121 \fIAmanda\fR Tape Server Host Check
122 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
123 /amanda2/amanda/work: 911475 KB disk space available, that\'s plenty\.
124 NOTE: skipping tape\-writable test\.
125 Tape VOL10 label ok\.
126 Server check took 34\.966 seconds\.
128 \fIAmanda\fR Backup Client Hosts Check
129 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
130 WARNING: northstar: selfcheck request timed out\. Host down?
131 WARNING: drinkme: selfcheck request timed out\. Host down?
132 WARNING: scruffy: selfcheck request timed out\. Host down?
133 Client check: 136 hosts checked in 51\.945 seconds, 3 problems found\.
135 (brought to you by \fIAmanda\fR 2\.5\.0)
138 In this example, if the line
139 \fBmailto csd\-amanda\fR
141 \fIamanda\.conf\fR, mail will be sent to
143 if the server check returns an error\.
145 % amcheck \-s \-m daily
149 fatal slot \fIslot\fR: \fIerror message\fR
151 (error) The tape changer detected some kind of fatal error while trying to load slot
155 slot \fIslot\fR: \fIerror message\fR
157 (warning) The tape changer detected some kind of non\-fatal error (e\.g\. an empty slot was detected) while trying to load slot
158 \fIslot\fR, or an error was detected trying to read the tape label\.
161 slot \fIslot\fR: date \fIYYYYMMDD\fR label \fIlabel\fR (\fIresult\fR)
167 was loaded and found to have been last written on
168 \fIYYYYMMDD\fR\. If the tape is new, the date field will be an
175 This is the expected tape\.
180 This label does not match the
183 \fIamanda\.conf\fR\. Tape scanning will continue\.
188 This tape is still active and cannot be overwritten\. Tape scanning will continue\.
193 This tape is the first one that matches the
196 \fIamanda\.conf\fR\. Tape scanning will continue if necessary\.
201 This tape is the next one that matches the
204 \fIamanda\.conf\fR\. Tape scanning will continue\.
209 ERROR: cannot look up dump user \fIuser\fR
215 could not be found in the system password information\.
218 ERROR: cannot look up my own uid (\fIuid\fR)
224 could not be found in the system password information\.
227 ERROR: running as user \fIrunuser\fR instead of \fIdumpuser\fR
231 should be run as the dump user
239 ERROR: program dir \fIdirectory\fR: not accessible
241 (error) The directory
243 expects to find its auxiliary programs in,
244 \fIdirectory\fR, is not accessible\.
247 ERROR: program \fIprogram\fR: does not exist
251 needed on the tape server could not be found\.
254 ERROR: program \fIprogram\fR: not a file
258 needed on the tape server exists but is not a file\.
261 ERROR: program \fIprogram\fR: not executable
265 needed on the tape server exists but is not executable\.
268 WARNING: program \fIprogram\fR: not setuid\-root
272 needed on the tape server exists but should be owned by user "root" and setuid\.
275 ERROR: \fIXXX\fR dir \fIdirectory\fR: not writable
279 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
295 for the directory that holds the old log files (see
305 database information directory (see
308 \fBamanda\.conf\fR) or
325 tapelist directory (see
333 NOTE: \fIXXX\fR dir \fIdirectory\fR: does not exist
335 (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\.
338 NOTE: it will be created on the next run
340 (info) This indicates the info directory listed in the previous message will be created on the next run\.
343 ERROR: \fIXXX\fR dir \fIname\fR: not a directory
349 to be a directory, but it is something else (e\.g\. file)\.
352 WARNING: info file \fIfile\fR: does not exist
356 does not exist in the text format database\. Since the parent directories do exist, the file should already have been created\.
359 ERROR: info file \fIname\fR: not a file
365 to be a file, but it is something else (e\.g\. file)\.
368 ERROR: info file \fIfile\fR: not readable
370 (error) The text format database file
375 ERROR: log file \fIfile\fR: not writable
384 \fBamanda\.conf\fR) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission\.
387 ERROR: tape list \fItapelist\fR: not writable
396 \fBamanda\.conf\fR) is not writable or was not found\.
399 ERROR: tape list \fItapelist\fR: parse error
408 \fBamanda\.conf\fR) could not be read or parsed\.
411 WARNING: tapedev is /dev/null, dumps will be thrown away
421 uses that when debugging to throw all the dump images away\.
424 WARNING: hold file \fIfile\fR exists
428 exists and will cause
430 to pause at the beginning until it is removed\.
433 ERROR: holding disk \fIdisk\fR: statfs: \fIerror message\fR
435 (error) An error was returned from the
437 system call on holding disk
439 (maybe because it does not exist)\.
442 ERROR: holding disk \fIdisk\fR: not writable
445 \fIdisk\fR, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission\.
448 WARNING: holding disk \fIdisk\fR: available space unknown \fIN\fR KB requested\.
452 could not determine the amount of available space on holding disk
454 to see if there were at least
459 WARNING: holding disk \fIdisk\fR: only \fIF\fR KB free (\fIR\fR KB requested)\.
465 KBytes of free space on holding disk
468 KBytes were available\. 10 MBytes is subtracted for each backup process (see the
471 option) to allow for unexpected overruns\.
474 .nr an-no-space-flag 1
478 Even though this message is listed as a warning, it causes
480 to exit with a non\-zero status\.
483 Holding disk \fIdisk\fR: \fIN\fR KB disk space available, that\'s plenty\.
485 (info) There was sufficient free space on holding disk
489 WARNING: holding disk \fIdisk\fR: only \fIF\fR KB free, using nothing
491 (warning) Holding disk
495 KBytes of free space, but that is not enough for what is requested in
499 Holding disk \fIdisk\fR: \fIF\fR KB disk space available, using \fIU\fR KB
505 KBytes of free space and
512 WARNING: if a tape changer is not available, runtapes must be set to 1\.
517 option must be set to 1 if the
523 ERROR: \fIerror message\fR\.
525 (error) An error was detected while initializing the tape changer\.
528 ERROR: \fItape device\fR: \fIerror message\fR\.
530 (error) An error was detected while processing the tape label\.
533 ERROR: cannot overwrite active tape \fIlabel\fR\.
537 is still active and cannot be used\.
540 ERROR: label \fIlabel\fR doesn\'t match labelstr \fIpattern\fR \.
542 (error) The label on tape
550 (expecting a new tape)
552 (info) The tape is not OK and a new tape was expected\.
555 (expecting tape \fIlabel\fR or a new tape)
557 (info) The tape is not OK and either tape
559 or a new tape was expected\.
562 ERROR: tape \fIlabel\fR label ok, but is not writable\.
566 is OK, but the write enable test failed\.
569 Tape \fIlabel\fR is writable\.
573 is OK and the write enable test succeeded\.
576 NOTE: skipping tape\-writable test\.
578 (info) The tape write test (see the
580 option) was not enabled\.
583 WARNING: skipping tape test because amdump or amflush seem to be running, WARNING: if they are not, you must run amcleanup
585 (warning) It looked to
591 were running because a log file or amdump file exists\. If they are not running, you probably need to run
593 to clear up a previous failure\. Otherwise, you need to wait until they complete before running
597 NOTE: skipping tape checks
599 (info) The tape tests are being skipped because you used the
601 command line option\.
604 WARNING: \fIcompress\fR is not executable, server\-compression and indexing will not work
606 (warning) Compression program
608 is not executable, so compression on the tape server host and creating index files will not work\.
611 Tape \fIlabel\fR label ok\.
615 is OK for the next run\.
618 Server check took \fIS\fR seconds\.
620 (info) Reports how long the tape server host checks took\.
623 ERROR: \fIhost\fR: could not resolve hostname
625 (error) Could not look up client hostname
629 Client check: \fIH\fR hosts checked in \fIS\fR seconds, \fIN\fR problems found\.
631 (info) Reports the number of client hosts checked, how long it took and the number of errors detected\.
634 WARNING: \fIhost\fR: selfcheck request timed out\. Host down?
636 (warning) There was no response from
638 when trying to do the client checks\. The host might really be down or it might not be configured properly\.
641 ERROR: \fIhost\fR NAK: \fImessage\fR
645 reported a negative acknowledgment error of
647 to the status check request\.
650 ERROR: \fIhost\fR NAK: [NAK parse failed]
654 could not parse the negative acknowledgment error from
655 \fIhost\fR\. There might be an
657 version mismatch between the host running
663 ERROR: \fIhost\fR [mutual\-authentication failed]
665 (error) Kerberos authentication failed while contacting
669 ERROR: \fIhost\fR: \fImessage\fR
673 was reported by the status check on
678 The exit code of \fBamcheck\fR is one of:
689 Stefan G\. Weichinger,
690 <sgw@amanda\.org>, maintainer of the
691 \fIAmanda\fR\-documentation: XML\-conversion
696 : http://wiki.zmanda.com