12 amcheck \- run Amanda self\-checks
30 runs a number of self\-checks on both the Amanda tape server host and
31 the Amanda client hosts.
33 On the tape server host,
35 can go through the same tape checking used at the start of the nightly
37 run to verify the correct tape for the next run is mounted.
40 can also do a self\-check on all client hosts
41 to make sure each host is running and that permissions
42 on filesystems to be backed up are correct.
44 You can specify many host/disk expressions, only disks that
45 match an expression will be checked. All disk are checked if no
50 man page for more details about Amanda.
54 Run the tape server local and tape checks
59 Run the client host checks.
62 Run the local tests (e.g. permissions) on the server host.
65 Run the tape tests on the server host.
68 Enables a destructive check for write\-protection on the
69 tape (which would otherwise cause the subsequent
73 is writable, this check causes all data after the tape label to be
74 erased (actually depends on the device driver: there is no portable
75 non\-destructive way to check for write\-protection).
78 and is only made if the tape is otherwise correct.
81 Nothing is printed, but mail is sent
82 if any errors are detected.
85 address specified in the
96 but the mail is always sent.
111 In this example, both the tape server and client tests are run.
112 The results are displayed on standard output.
116 % amcheck @DEFAULT_CONFIG@
117 Amanda Tape Server Host Check
118 -----------------------------
119 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
120 NOTE: skipping tape-writable test.
122 Server check took 34.966 seconds.
124 Amanda Backup Client Hosts Check
125 --------------------------------
126 WARNING: northstar: selfcheck request timed out. Host down?
127 WARNING: drinkme: selfcheck request timed out. Host down?
128 WARNING: scruffy: selfcheck request timed out. Host down?
129 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
131 (brought to you by Amanda 2.4.2)
135 In this example, if the line
141 if the server check returns an error.
145 % amcheck \-s \-m @DEFAULT_CONFIG@
150 fatal slot \fIslot\fP: \fIerror message\fP
152 The tape changer detected some kind of fatal error
153 while trying to load slot
156 slot \fIslot\fP: \fIerror message\fP
158 The tape changer detected some kind of non-fatal error
159 (e.g. an empty slot was detected)
160 while trying to load slot
162 or an error was detected trying to read the tape label.
164 slot \fIslot\fP: date \fIYYYYMMDD\fP label \fIlabel\fP (\fIresult\fP)
170 was loaded and found to have been last written on
172 If the tape is new, the date field will be an
180 This is the expected tape.
183 This label does not match the
187 Tape scanning will continue.
190 This tape is still active and cannot be overwritten.
191 Tape scanning will continue.
194 This tape is the first one that matches the
198 Tape scanning will continue if necessary.
201 This tape is the next one that matches the
205 Tape scanning will continue.
208 ERROR: cannot look up dump user "\fIuser\fP"
214 could not be found in the system password information.
216 ERROR: cannot look up my own uid (\fIuid\fP)
222 could not be found in the system password information.
224 ERROR: running as user "\fIrunuser\fP" instead of "\fIdumpuser\fP"
227 should be run as the dump user
234 ERROR: program dir \fIdirectory\fP: not accessible
236 The directory Amanda expects to find its auxiliary programs in,
240 ERROR: program \fIprogram\fP: does not exist
244 needed on the tape server could not be found.
246 ERROR: program \fIprogram\fP: not a file
250 needed on the tape server exists but is not a file.
252 ERROR: program \fIprogram\fP: not executable
256 needed on the tape server exists but is not executable.
258 WARNING: program \fIprogram\fP: not setuid-root
262 needed on the tape server exists but should be owned by user "root"
265 ERROR: \fIXXX\fP dir \fIdirectory\fP: not writable
269 is either not writable,
270 i.e. the dump user will not be able to create or remove files,
271 or cannot be accessed, perhaps because a parent directory
272 does not allow search permission.
279 for the Amanda log directory (see
285 for the directory that holds the old log files (see
291 for an Amanda database information directory (see
298 for an Amanda index directory (see
304 for the Amanda tapelist directory (see
310 NOTE: \fIXXX\fP dir \fIdirectory\fP: does not exist
312 A database (info) or index directory does not exist or cannot be accessed.
313 This might just mean this is a new client or disk,
314 but if that is not the case,
315 this should be treated as an error.
317 NOTE: it will be created on the next run
319 This indicates the info directory listed in the previous message
320 will be created on the next run.
322 ERROR: \fIXXX\fP dir \fIname\fP: not a directory
328 but it is something else (e.g. file).
330 WARNING: info file \fIfile\fP: does not exist
334 does not exist in the text format database.
335 Since the parent directories do exist,
336 the file should already have been created.
338 ERROR: info file \fIname\fP: not a file
344 but it is something else (e.g. file).
346 ERROR: info file \fIfile\fP: not readable
348 The text format database file
352 ERROR: log file \fIfile\fP: not writable
362 is either not writable,
363 or cannot be accessed, perhaps because a parent directory
364 does not allow search permission.
366 ERROR: tape list \fItapelist\fP: not writable
368 Amanda tape list file
374 is not writable or was not found.
376 ERROR: tape list \fItapelist\fP: parse error
378 Amanda tape list file
384 could not be read or parsed.
386 WARNING: tapedev is /dev/null, dumps will be thrown away
394 and Amanda uses that when debugging to throw all the dump images away.
396 WARNING: hold file \fIfile\fP exists
400 exists and will cause
402 to pause at the beginning until it is removed.
404 ERROR: holding disk \fIdisk\fP: statfs: \fIerror message\fP
406 An error was returned from the
408 system call on holding disk
410 (maybe because it does not exist).
412 ERROR: holding disk \fIdisk\fP: not writable
417 probably because the caller does not have write permission
418 or a parent directory does not allow search permission.
420 WARNING: holding disk \fIdisk\fP: available space unknown \fIN\fP KB requested.
423 could not determine the amount of available space on holding disk
425 to see if there were at least
429 WARNING: holding disk \fIdisk\fP: only \fIF\fP KB free (\fIR\fP KB requested).
434 KBytes of free space on holding disk
438 KBytes were available.
439 10 MBytes is subtracted for each backup process
444 to allow for unexpected overruns.
447 even though this message is listed as a warning, it causes
449 to exit with a non-zero status.
451 Holding disk \fIdisk\fP: \fIN\fP KB disk space available, that's plenty.
453 There was sufficient free space on holding disk
456 WARNING: holding disk \fIdisk\fP: only \fIF\fP KB free, using nothing
462 KBytes of free space, but that is not enough for what is requested in
465 Holding disk \fIdisk\fP: \fIF\fP KB disk space available, using \fIU\fP KB
471 KBytes of free space and Amanda will be using up to
475 WARNING: if a tape changer is not available, runtapes must be set to 1.
480 option must be set to 1 if the
485 ERROR: \fIerror message\fP.
487 An error was detected while initializing the tape changer.
489 ERROR: \fItape device\fP: \fIerror message\fP.
491 An error was detected while processing the tape label.
493 ERROR: cannot overwrite active tape \fIlabel\fP.
497 is still active and cannot be used.
499 ERROR: label \fIlabel\fP doesn't match labelstr "\fIpattern\fP".
508 (expecting a new tape)
510 The tape is not OK and a new tape was expected.
512 (expecting tape \fIlabel\fP or a new tape)
514 The tape is not OK and either tape
516 or a new tape was expected.
518 ERROR: tape \fIlabel\fP label ok, but is not writable.
522 is OK, but the write enable test failed.
524 Tape \fIlabel\fP is writable.
528 is OK and the write enable test succeeded.
530 NOTE: skipping tape-writable test.
532 The tape write test (see the
534 option) was not enabled.
536 WARNING: skipping tape test because amdump or amflush seem to be running
538 WARNING: if they are not, you must run amcleanup
546 were running because a log file or amdump file exists.
547 If they are not running, you probably need to run
549 to clear up a previous failure.
550 Otherwise, you need to wait until they complete before running
553 NOTE: skipping tape checks
555 The tape tests are being skipped because you used the
559 WARNING: \fIcompress\fP is not executable, server-compression and indexing will not work
564 so compression on the tape server host and creating index files will not work.
566 Tape \fIlabel\fP label ok.
573 Server check took \fIS\fP seconds.
575 Reports how long the tape server host checks took.
577 ERROR: \fIhost\fP: could not resolve hostname
579 Could not look up client hostname
582 Client check: \fIH\fP hosts checked in \fIS\fP seconds, \fIN\fP problems found.
584 Reports the number of client hosts checked,
585 how long it took and the number of errors detected.
587 WARNING: \fIhost\fP: selfcheck request timed out. Host down?
589 There was no response from
591 when trying to do the client checks.
592 The host might really be down or it might not be configured properly.
594 ERROR: \fIhost\fP NAK: \fImessage\fP
597 reported a negative acknowledgment error of
599 to the status check request.
601 ERROR: \fIhost\fP NAK: [NAK parse failed]
604 could not parse the negative acknowledgment error from
606 There might be an Amanda version mismatch between the host running
611 ERROR: \fIhost\fP [mutual-authentication failed]
613 Kerberos authentication failed while contacting
616 ERROR: \fIhost\fP: \fImessage\fP
620 was reported by the status check on
623 James da Silva <jds@cs.umd.edu>
625 University of Maryland, College Park