amcheck — run Amanda self-checks
amcheck [-mwsclt ] [-Maddress ]
Amcheck runs a number of self-checks on both the Amanda tape server host and the Amanda client hosts.
On the tape server host, amcheck can go through the same tape checking used at the start of the nightly amdump run to verify the correct tape for the next run is mounted.
Amcheck 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.
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.
See the amanda(8) man page for more details about Amanda.
Run the tape server local and tape checks (same as
Run the client host checks.
Run the local tests (e.g. permissions) on the server host.
Run the tape tests on the server host.
Enables a DESTRUCTIVE check for write-protection on the
tape (which would otherwise cause the subsequent
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
and is only made if the tape is otherwise correct.
Nothing is printed, but mail is sent if any errors are detected.
The mail goes to the
address specified in the
file or the
but the mail is always sent.
Mail the report to
instead of the
The default is
In this example, both the tape server and client tests are run. The results are displayed on standard output.
% amcheck daily Amanda Tape Server Host Check ----------------------------- /amanda2/amanda/work: 911475 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape VOL10 label ok. Server check took 34.966 seconds. Amanda Backup Client Hosts Check -------------------------------- WARNING: northstar: selfcheck request timed out. Host down? WARNING: drinkme: selfcheck request timed out. Host down? WARNING: scruffy: selfcheck request timed out. Host down? Client check: 136 hosts checked in 51.945 seconds, 3 problems found. (brought to you by Amanda 2.5.0)
In this example, if the line mailto csd-amanda is in amanda.conf, mail will be sent to csd-amanda if the server check returns an error.
% amcheck -s -m daily
(error) The tape changer detected some kind of fatal error while trying to load slot slot.
(warning) The tape changer detected some kind of non-fatal error (e.g. an empty slot was detected) while trying to load slot slot, or an error was detected trying to read the tape label.
(info) Tape label in slot slot was loaded and found to have been last written on YYYYMMDD. If the tape is new, the date field will be an X. The result may be one of:
This is the expected tape.
This label does not match the labelstr pattern in amanda.conf. Tape scanning will continue.
This tape is still active and cannot be overwritten. Tape scanning will continue.
This tape is the first one that matches the labelstr pattern in amanda.conf. Tape scanning will continue if necessary.
This tape is the next one that matches the labelstr pattern in amanda.conf. Tape scanning will continue.
(error) Dump user user from amanda.conf could not be found in the system password information.
(error) User id uid running amcheck could not be found in the system password information.
(error) Amcheck should be run as the dump user dumpuser from amanda.conf instead of runuser.
(error) The directory Amanda expects to find its auxiliary programs in, directory, is not accessible.
(error) Program program needed on the tape server could not be found.
(error) Program program needed on the tape server exists but is not a file.
(error) Program program needed on the tape server exists but is not executable.
(warning) Program program needed on the tape server exists but should be owned by user "root" and setuid.
(error) Directory directory 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 XXX may be:
for the Amanda log directory (see logdir in amanda.conf)
for the directory that holds the old log files (see logdir in amanda.conf)
for an Amanda database information directory (see curinfo in amanda.conf) or
for an Amanda index directory (see indexdir in amanda.conf)
for the Amanda tapelist directory (see tapelist in amanda.conf)
(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.
(info) This indicates the info directory listed in the previous message will be created on the next run.
(error) Amcheck expected name to be a directory, but it is something else (e.g. file).
file: does not exist
(warning) File file does not exist in the text format database. Since the parent directories do exist, the file should already have been created.
name: not a file
(error) Amcheck expected name to be a file, but it is something else (e.g. file).
file: not readable
(error) The text format database file file is not readable.
file: not writable
(error) Log file file (file log in logdir from amanda.conf) is either not writable, or cannot be accessed, perhaps because a parent directory does not allow search permission.
(error) Amanda tape list file tapelist (see tapelist in amanda.conf) is not writable or was not found.
(error) Amanda tape list file tapelist (see tapelist in amanda.conf) could not be read or parsed.
is set to
and Amanda uses that when debugging to throw all the dump images away.
(info) Hold file file exists and will cause amdump to pause at the beginning until it is removed.
(error) An error was returned from the statfs system call on holding disk disk (maybe because it does not exist).
(error) Holding disk disk, is not writable, probably because the caller does not have write permission or a parent directory does not allow search permission.
(warning) Amcheck could not determine the amount of available space on holding disk disk to see if there were at least N KBytes available.
(warning) amanda.conf requested R KBytes of free space on holding disk disk, but only F KBytes were available. 10 MBytes is subtracted for each backup process (see the inparallel amanda.conf option) to allow for unexpected overruns.
(info) There was sufficient free space on holding disk disk.
(warning) Holding disk disk has F KBytes of free space, but that is not enough for what is requested in amanda.conf.
(info) Holding disk disk has F KBytes of free space and Amanda will be using up to U Kbytes.
(warning) The runtapes amanda.conf option must be set to 1 if the tpchanger amanda.conf option is not set.
(error) An error was detected while initializing the tape changer.
(error) An error was detected while processing the tape label.
(error) Tape label is still active and cannot be used.
(error) The label on tape label does not match the labelstr amanda.conf option.
(info) The tape is not OK and a new tape was expected.
(info) The tape is not OK and either tape label or a new tape was expected.
(error) Tape label is OK, but the write enable test failed.
(info) Tape label is OK and the write enable test succeeded.
The tape write test (see the
option) was not enabled.
It looked to
were running because a log file or amdump file exists.
If they are not running, you probably need to run
to clear up a previous failure.
Otherwise, you need to wait until they complete before running
The tape tests are being skipped because you used the
command line option.
(warning) Compression program compress is not executable, so compression on the tape server host and creating index files will not work.
(info) Tape label is OK for the next run.
(info) Reports how long the tape server host checks took.
(error) Could not look up client hostname host.
(info) Reports the number of client hosts checked, how long it took and the number of errors detected.
(warning) There was no response from host when trying to do the client checks. The host might really be down or it might not be configured properly.
(error) Host reported a negative acknowledgment error of message to the status check request.
(error) Amcheck could not parse the negative acknowledgment error from host. There might be an Amanda version mismatch between the host running amcheck and host.
(error) Kerberos authentication failed while contacting host.
(error) Error message was reported by the status check on host.
James da Silva,
<email@example.com> : Original text
Stefan G. Weichinger,
<firstname.lastname@example.org>, maintainer of the