1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "AMCHECK" 8 "" "" ""
22 amcheck - run Amanda self-checks
25 \fBamcheck\fR [-am] [-w] [-sclt] [-M \fIaddress\fR]*
26 \fIconfig\fR [\fIhost\fR [\fIdisk\fR]*]*
27 [-o \fIconfigoption\fR]*
32 runs a number of self-checks on both the
34 tape server host and the
38 On the tape server host,
40 can go through the same tape checking used at the start of the nightly
42 run to verify the correct tape for the next run is mounted.
45 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.
47 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.
51 man page for more details about
56 Run the tape server local and tape checks (same as
60 Run the client host checks.Multiple specific clients can be checked by specifying the client name.
63 Run the local tests (e.g. permissions) on the server host.
66 Run the tape tests on the server host.
69 Enables a DESTRUCTIVE check for write-protection on the tape (which would otherwise cause the subsequent
71 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
87 but the mail is always sent.
89 \fB-M\fR \fIaddress\fR
95 \fBamanda.conf\fR. Implies
98 \fIhost\fR [\fIdisk\fR]*
99 Specify the host and disk on which the command will work.
101 \fB-o\fR \fIconfigoption\fR
102 See the "\fBCONFIGURATION OVERWRITE\fR" section in
109 In this example, both the tape server and client tests are run. The results are displayed on standard output.
113 \fBAmanda\fR Tape Server Host Check
114 -----------------------------
115 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
116 NOTE: skipping tape-writable test.
118 Server check took 34.966 seconds.
120 \fBAmanda\fR Backup Client Hosts Check
121 --------------------------------
122 WARNING: northstar: selfcheck request timed out. Host down?
123 WARNING: drinkme: selfcheck request timed out. Host down?
124 WARNING: scruffy: selfcheck request timed out. Host down?
125 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
127 (brought to you by \fBAmanda\fR 2.5.0)
130 In this example, if the line
131 \fBmailto csd-amanda\fR
133 \fBamanda.conf\fR, mail will be sent to
135 if the server check returns an error.
138 % amcheck -s -m daily
142 fatal slot \fBslot\fR: \fBerror message\fR
143 (error) The tape changer detected some kind of fatal error while trying to load slot
146 slot \fBslot\fR: \fBerror message\fR
147 (warning) The tape changer detected some kind of non-fatal error (e.g. an empty slot was detected) while trying to load slot
148 \fBslot\fR, or an error was detected trying to read the tape label.
150 slot \fBslot\fR: date \fBYYYYMMDD\fR label \fBlabel\fR (\fBresult\fR)
155 was loaded and found to have been last written on
156 \fBYYYYMMDD\fR. If the tape is new, the date field will be an
163 This is the expected tape.
166 This label does not match the
169 \fBamanda.conf\fR. Tape scanning will continue.
172 This tape is still active and cannot be overwritten. Tape scanning will continue.
175 This tape is the first one that matches the
178 \fBamanda.conf\fR. Tape scanning will continue if necessary.
181 This tape is the next one that matches the
184 \fBamanda.conf\fR. Tape scanning will continue.
188 ERROR: cannot look up dump user \fBuser\fR
193 could not be found in the system password information.
195 ERROR: cannot look up my own uid (\fBuid\fR)
200 could not be found in the system password information.
202 ERROR: running as user \fBrunuser\fR instead of \fBdumpuser\fR
205 should be run as the dump user
212 ERROR: program dir \fBdirectory\fR: not accessible
213 (error) The directory
215 expects to find its auxiliary programs in,
216 \fBdirectory\fR, is not accessible.
218 ERROR: program \fBprogram\fR: does not exist
221 needed on the tape server could not be found.
223 ERROR: program \fBprogram\fR: not a file
226 needed on the tape server exists but is not a file.
228 ERROR: program \fBprogram\fR: not executable
231 needed on the tape server exists but is not executable.
233 WARNING: program \fBprogram\fR: not setuid-root
236 needed on the tape server exists but should be owned by user "root" and setuid.
238 ERROR: \fBXXX\fR dir \fBdirectory\fR: not writable
241 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
255 for the directory that holds the old log files (see
263 database information directory (see
266 \fBamanda.conf\fR) or
279 tapelist directory (see
286 NOTE: \fBXXX\fR dir \fBdirectory\fR: does not exist
287 (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.
289 NOTE: it will be created on the next run
290 (info) This indicates the info directory listed in the previous message will be created on the next run.
292 ERROR: \fBXXX\fR dir \fBname\fR: not a directory
297 to be a directory, but it is something else (e.g. file).
299 WARNING: info file \fIfile\fR: does not exist
302 does not exist in the text format database. Since the parent directories do exist, the file should already have been created.
304 ERROR: info file \fIname\fR: not a file
309 to be a file, but it is something else (e.g. file).
311 ERROR: info file \fIfile\fR: not readable
312 (error) The text format database file
316 ERROR: log file \fIfile\fR: not writable
324 \fBamanda.conf\fR) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission.
326 ERROR: tape list \fBtapelist\fR: not writable
334 \fBamanda.conf\fR) is not writable or was not found.
336 ERROR: tape list \fBtapelist\fR: parse error
344 \fBamanda.conf\fR) could not be read or parsed.
346 WARNING: tapedev is /dev/null, dumps will be thrown away
355 uses that when debugging to throw all the dump images away.
357 WARNING: hold file \fIfile\fR exists
360 exists and will cause
362 to pause at the beginning until it is removed.
364 ERROR: holding disk \fBdisk\fR: statfs: \fBerror message\fR
365 (error) An error was returned from the
367 system call on holding disk
369 (maybe because it does not exist).
371 ERROR: holding disk \fBdisk\fR: not writable
373 \fBdisk\fR, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission.
375 WARNING: holding disk \fBdisk\fR: available space unknown \fBN\fR KB requested.
378 could not determine the amount of available space on holding disk
380 to see if there were at least
384 WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free (\fBR\fR KB requested).
389 KBytes of free space on holding disk
392 KBytes were available. 10 MBytes is subtracted for each backup process (see the
393 \fBinparallel\fR\fBamanda.conf\fR
394 option) to allow for unexpected overruns.
397 .nr an-no-space-flag 1
401 Even though this message is listed as a warning, it causes \fBamcheck\fR to exit with a non-zero status..TP
402 Holding disk \fBdisk\fR: \fBN\fR KB disk space available, that's plenty.
403 (info) There was sufficient free space on holding disk
406 WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free, using nothing
407 (warning) Holding disk
411 KBytes of free space, but that is not enough for what is requested in
414 Holding disk \fBdisk\fR: \fBF\fR KB disk space available, using \fBU\fR KB
419 KBytes of free space and
425 WARNING: if a tape changer is not available, runtapes must be set to 1.
427 \fBruntapes\fR\fBamanda.conf\fR
428 option must be set to 1 if the
429 \fBtpchanger\fR\fBamanda.conf\fR
432 ERROR: \fBerror message\fR.
433 (error) An error was detected while initializing the tape changer.
435 ERROR: \fBtape device\fR: \fBerror message\fR.
436 (error) An error was detected while processing the tape label.
438 ERROR: cannot overwrite active tape \fBlabel\fR.
441 is still active and cannot be used.
443 ERROR: label \fBlabel\fR doesn't match labelstr \fBpattern\fR .
444 (error) The label on tape
447 \fBlabelstr\fR\fBamanda.conf\fR
450 (expecting a new tape)
451 (info) The tape is not OK and a new tape was expected.
453 (expecting tape \fBlabel\fR or a new tape)
454 (info) The tape is not OK and either tape
456 or a new tape was expected.
458 ERROR: tape \fBlabel\fR label ok, but is not writable.
461 is OK, but the write enable test failed.
463 Tape \fBlabel\fR is writable.
466 is OK and the write enable test succeeded.
468 NOTE: skipping tape-writable test.
469 (info) The tape write test (see the
471 option) was not enabled.
473 WARNING: skipping tape test because amdump or amflush seem to be running, WARNING: if they are not, you must run amcleanup
474 (warning) It looked to
480 were running because a log file or amdump file exists. If they are not running, you probably need to run
482 to clear up a previous failure. Otherwise, you need to wait until they complete before running
485 NOTE: skipping tape checks
486 (info) The tape tests are being skipped because you used the
490 WARNING: \fBcompress\fR is not executable, server-compression and indexing will not work
491 (warning) Compression program
493 is not executable, so compression on the tape server host and creating index files will not work.
495 Tape \fBlabel\fR label ok.
498 is OK for the next run.
500 Server check took \fBS\fR seconds.
501 (info) Reports how long the tape server host checks took.
503 ERROR: \fBhost\fR: could not resolve hostname
504 (error) Could not look up client hostname
507 Client check: \fBH\fR hosts checked in \fBS\fR seconds, \fBN\fR problems found.
508 (info) Reports the number of client hosts checked, how long it took and the number of errors detected.
510 WARNING: \fBhost\fR: selfcheck request timed out. Host down?
511 (warning) There was no response from
513 when trying to do the client checks. The host might really be down or it might not be configured properly.
515 ERROR: \fBhost\fR NAK: \fBmessage\fR
518 reported a negative acknowledgment error of
520 to the status check request.
522 ERROR: \fBhost\fR NAK: [NAK parse failed]
525 could not parse the negative acknowledgment error from
526 \fBhost\fR. There might be an
528 version mismatch between the host running
533 ERROR: \fBhost\fR [mutual-authentication failed]
534 (error) Kerberos authentication failed while contacting
537 ERROR: \fBhost\fR: \fBmessage\fR
540 was reported by the status check on
548 Stefan G. Weichinger,
549 <sgw@amanda.org>, maintainer of the
550 \fBAmanda\fR-documentation: XML-conversion