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 [-mwsclt] [-Maddress] \fIconfig\fR [\fIhost\fRĀ [\fIdisk\fR...]...]
29 runs a number of self-checks on both the
31 tape server host and the
35 On the tape server host,
37 can go through the same tape checking used at the start of the nightly
39 run to verify the correct tape for the next run is mounted.
42 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.
44 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.
48 man page for more details about
53 Run the tape server local and tape checks (same as
57 Run the client host checks.
60 Run the local tests (e.g. permissions) on the server host.
63 Run the tape tests on the server host.
66 Enables a DESTRUCTIVE check for write-protection on the tape (which would otherwise cause the subsequent
68 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 implies
70 and is only made if the tape is otherwise correct.
73 Nothing is printed, but mail is sent if any errors are detected. The mail goes to the
75 address specified in the
86 but the mail is always sent.
94 \fBamanda.conf\fR. Implies
101 In this example, both the tape server and client tests are run. The results are displayed on standard output.
105 \fBAmanda\fR Tape Server Host Check
106 -----------------------------
107 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
108 NOTE: skipping tape-writable test.
110 Server check took 34.966 seconds.
112 \fBAmanda\fR Backup Client Hosts Check
113 --------------------------------
114 WARNING: northstar: selfcheck request timed out. Host down?
115 WARNING: drinkme: selfcheck request timed out. Host down?
116 WARNING: scruffy: selfcheck request timed out. Host down?
117 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
119 (brought to you by \fBAmanda\fR 2.5.0)
122 In this example, if the line
123 \fBmailto csd-amanda\fR
125 \fBamanda.conf\fR, mail will be sent to
127 if the server check returns an error.
130 % amcheck -s -m daily
134 fatal slot \fBslot\fR: \fBerror message\fR
135 (error) The tape changer detected some kind of fatal error while trying to load slot
138 slot \fBslot\fR: \fBerror message\fR
139 (warning) The tape changer detected some kind of non-fatal error (e.g. an empty slot was detected) while trying to load slot
140 \fBslot\fR, or an error was detected trying to read the tape label.
142 slot \fBslot\fR: date \fBYYYYMMDD\fR label \fBlabel\fR (\fBresult\fR)
147 was loaded and found to have been last written on
148 \fBYYYYMMDD\fR. If the tape is new, the date field will be an
155 This is the expected tape.
158 This label does not match the
161 \fBamanda.conf\fR. Tape scanning will continue.
164 This tape is still active and cannot be overwritten. Tape scanning will continue.
167 This tape is the first one that matches the
170 \fBamanda.conf\fR. Tape scanning will continue if necessary.
173 This tape is the next one that matches the
176 \fBamanda.conf\fR. Tape scanning will continue.
180 ERROR: cannot look up dump user \fBuser\fR
185 could not be found in the system password information.
187 ERROR: cannot look up my own uid (\fBuid\fR)
192 could not be found in the system password information.
194 ERROR: running as user \fBrunuser\fR instead of \fBdumpuser\fR
197 should be run as the dump user
204 ERROR: program dir \fBdirectory\fR: not accessible
205 (error) The directory
207 expects to find its auxiliary programs in,
208 \fBdirectory\fR, is not accessible.
210 ERROR: program \fBprogram\fR: does not exist
213 needed on the tape server could not be found.
215 ERROR: program \fBprogram\fR: not a file
218 needed on the tape server exists but is not a file.
220 ERROR: program \fBprogram\fR: not executable
223 needed on the tape server exists but is not executable.
225 WARNING: program \fBprogram\fR: not setuid-root
228 needed on the tape server exists but should be owned by user "root" and setuid.
230 ERROR: \fBXXX\fR dir \fBdirectory\fR: not writable
233 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
247 for the directory that holds the old log files (see
255 database information directory (see
258 \fBamanda.conf\fR) or
271 tapelist directory (see
278 NOTE: \fBXXX\fR dir \fBdirectory\fR: does not exist
279 (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.
281 NOTE: it will be created on the next run
282 (info) This indicates the info directory listed in the previous message will be created on the next run.
284 ERROR: \fBXXX\fR dir \fBname\fR: not a directory
289 to be a directory, but it is something else (e.g. file).
291 WARNING: info file \fIfile\fR: does not exist
294 does not exist in the text format database. Since the parent directories do exist, the file should already have been created.
296 ERROR: info file \fIname\fR: not a file
301 to be a file, but it is something else (e.g. file).
303 ERROR: info file \fIfile\fR: not readable
304 (error) The text format database file
308 ERROR: log file \fIfile\fR: not writable
316 \fBamanda.conf\fR) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission.
318 ERROR: tape list \fBtapelist\fR: not writable
326 \fBamanda.conf\fR) is not writable or was not found.
328 ERROR: tape list \fBtapelist\fR: parse error
336 \fBamanda.conf\fR) could not be read or parsed.
338 WARNING: tapedev is /dev/null, dumps will be thrown away
347 uses that when debugging to throw all the dump images away.
349 WARNING: hold file \fIfile\fR exists
352 exists and will cause
354 to pause at the beginning until it is removed.
356 ERROR: holding disk \fBdisk\fR: statfs: \fBerror message\fR
357 (error) An error was returned from the
359 system call on holding disk
361 (maybe because it does not exist).
363 ERROR: holding disk \fBdisk\fR: not writable
365 \fBdisk\fR, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission.
367 WARNING: holding disk \fBdisk\fR: available space unknown \fBN\fR KB requested.
370 could not determine the amount of available space on holding disk
372 to see if there were at least
376 WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free (\fBR\fR KB requested).
381 KBytes of free space on holding disk
384 KBytes were available. 10 MBytes is subtracted for each backup process (see the
385 \fBinparallel\fR\fBamanda.conf\fR
386 option) to allow for unexpected overruns.
389 .nr an-no-space-flag 1
393 Even though this message is listed as a warning, it causes \fBamcheck\fR to exit with a non-zero status..TP
394 Holding disk \fBdisk\fR: \fBN\fR KB disk space available, that's plenty.
395 (info) There was sufficient free space on holding disk
398 WARNING: holding disk \fBdisk\fR: only \fBF\fR KB free, using nothing
399 (warning) Holding disk
403 KBytes of free space, but that is not enough for what is requested in
406 Holding disk \fBdisk\fR: \fBF\fR KB disk space available, using \fBU\fR KB
411 KBytes of free space and
417 WARNING: if a tape changer is not available, runtapes must be set to 1.
419 \fBruntapes\fR\fBamanda.conf\fR
420 option must be set to 1 if the
421 \fBtpchanger\fR\fBamanda.conf\fR
424 ERROR: \fBerror message\fR.
425 (error) An error was detected while initializing the tape changer.
427 ERROR: \fBtape device\fR: \fBerror message\fR.
428 (error) An error was detected while processing the tape label.
430 ERROR: cannot overwrite active tape \fBlabel\fR.
433 is still active and cannot be used.
435 ERROR: label \fBlabel\fR doesn't match labelstr \fBpattern\fR .
436 (error) The label on tape
439 \fBlabelstr\fR\fBamanda.conf\fR
442 (expecting a new tape)
443 (info) The tape is not OK and a new tape was expected.
445 (expecting tape \fBlabel\fR or a new tape)
446 (info) The tape is not OK and either tape
448 or a new tape was expected.
450 ERROR: tape \fBlabel\fR label ok, but is not writable.
453 is OK, but the write enable test failed.
455 Tape \fBlabel\fR is writable.
458 is OK and the write enable test succeeded.
460 NOTE: skipping tape-writable test.
461 (info) The tape write test (see the
463 option) was not enabled.
465 WARNING: skipping tape test because amdump or amflush seem to be running, WARNING: if they are not, you must run amcleanup
466 (warning) It looked to
472 were running because a log file or amdump file exists. If they are not running, you probably need to run
474 to clear up a previous failure. Otherwise, you need to wait until they complete before running
477 NOTE: skipping tape checks
478 (info) The tape tests are being skipped because you used the
482 WARNING: \fBcompress\fR is not executable, server-compression and indexing will not work
483 (warning) Compression program
485 is not executable, so compression on the tape server host and creating index files will not work.
487 Tape \fBlabel\fR label ok.
490 is OK for the next run.
492 Server check took \fBS\fR seconds.
493 (info) Reports how long the tape server host checks took.
495 ERROR: \fBhost\fR: could not resolve hostname
496 (error) Could not look up client hostname
499 Client check: \fBH\fR hosts checked in \fBS\fR seconds, \fBN\fR problems found.
500 (info) Reports the number of client hosts checked, how long it took and the number of errors detected.
502 WARNING: \fBhost\fR: selfcheck request timed out. Host down?
503 (warning) There was no response from
505 when trying to do the client checks. The host might really be down or it might not be configured properly.
507 ERROR: \fBhost\fR NAK: \fBmessage\fR
510 reported a negative acknowledgment error of
512 to the status check request.
514 ERROR: \fBhost\fR NAK: [NAK parse failed]
517 could not parse the negative acknowledgment error from
518 \fBhost\fR. There might be an
520 version mismatch between the host running
525 ERROR: \fBhost\fR [mutual-authentication failed]
526 (error) Kerberos authentication failed while contacting
529 ERROR: \fBhost\fR: \fBmessage\fR
532 was reported by the status check on
540 Stefan G. Weichinger,
541 <sgw@amanda.org>, maintainer of the
542 \fBAmanda\fR-documentation: XML-conversion