1AMCHECK(8)              System Administration Commands              AMCHECK(8)
2
3
4

NAME

6       amcheck - run Amanda self-checks
7

SYNOPSIS

9       amcheck [-am] [-w] [-sclt] [-M address] [--client-verbose]
10               [--exact-match] [-o configoption...] config [host [disk...]...]
11

DESCRIPTION

13       Amcheck runs a number of self-checks on both the Amanda tape server
14       host and the Amanda client hosts.
15
16       On the tape server host, amcheck can go through the same tape checking
17       used at the start of the nightly amdump run to verify the correct tape
18       for the next run is mounted.
19
20       Amcheck can also do a self-check on all client hosts to make sure each
21       host is running and that permissions on filesystems to be backed up are
22       correct.
23
24       You can specify many host/disk expressions, only disks that match an
25       expression will be checked. All disks are checked if no expressions are
26       given.
27
28       See the amanda(8) man page for more details about Amanda.
29

OPTIONS

31       -s
32           Run the tape server local and tape checks (same as -lt).
33
34       -c
35           Run the client host checks. Multiple specific clients can be
36           checked by specifying the client name.
37
38       -l
39           Run the local tests (e.g. permissions) on the server host.
40
41       -t
42           Run the tape tests on the server host.
43
44       -w
45           Enables a DESTRUCTIVE check for write-protection on the tape (which
46           would otherwise cause the subsequent amdump to fail). If the tape
47           is writable, this check causes all data after the tape label to be
48           erased. If the autolabel option is enabled, this check may ERASE
49           any non-Amanda tape in the drive or changer. The check enable the
50           tape tests on the server host and is only made if the tape is
51           otherwise correct.
52
53       -m
54           Nothing is printed, but mail is sent if any errors are detected.
55           The mail goes to the mailto address specified in the amanda.conf
56           file or the address value if -M is set.
57
58       -a
59           Like -m but the mail is always sent.
60
61       -M address
62           Mail the report to address instead of the mailto value from
63           amanda.conf. Implies -m.
64
65       --client-verbose
66           Print all client messages.
67
68       --exact-match
69           The host and disk are parsed as exact values
70
71       host [disk]*
72           Specify the host and disk on which the command will work.
73
74       -o configoption
75           See the "CONFIGURATION OVERRIDE" section in amanda(8).
76
77       The default is -cs.
78

EXAMPLES

80       In this example, both the tape server and client tests are run. The
81       results are displayed on standard output.
82       % amcheck daily
83       Amanda Tape Server Host Check
84       -----------------------------
85       /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
86       NOTE: skipping tape-writable test.
87       Tape VOL10 label ok.
88       Server check took 34.966 seconds.
89
90       Amanda Backup Client Hosts Check
91       --------------------------------
92       WARNING: northstar: selfcheck request timed out.  Host down?
93       WARNING: drinkme: selfcheck request timed out.  Host down?
94       WARNING: scruffy: selfcheck request timed out.  Host down?
95       Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
96
97       (brought to you by Amanda 2.5.0)
98
99       In this example, if the line mailto csd-amanda is in amanda.conf, mail
100       will be sent to csd-amanda if the server check returns an error.
101       % amcheck -s -m daily
102

MESSAGES

104       fatal slot slot: error message
105           (error) The tape changer detected some kind of fatal error while
106           trying to load slot slot.
107
108       slot slot: error message
109           (warning) The tape changer detected some kind of non-fatal error
110           (e.g. an empty slot was detected) while trying to load slot slot,
111           or an error was detected trying to read the tape label.
112
113       slot slot: date YYYYMMDD label label (result)
114           (info) Tape label in slot slot was loaded and found to have been
115           last written on YYYYMMDD. If the tape is new, the date field will
116           be an X. The result may be one of:
117
118           exact label match
119               This is the expected tape.
120
121           no match
122               This label does not match the labelstr pattern in amanda.conf.
123               Tape scanning will continue.
124
125           active tape
126               This tape is still active and cannot be overwritten. Tape
127               scanning will continue.
128
129           first labelstr match
130               This tape is the first one that matches the labelstr pattern in
131               amanda.conf. Tape scanning will continue if necessary.
132
133           labelstr match
134               This tape is the next one that matches the labelstr pattern in
135               amanda.conf. Tape scanning will continue.
136
137
138       ERROR: cannot look up dump user user
139           (error) Dump user user from amanda.conf could not be found in the
140           system password information.
141
142       ERROR: cannot look up my own uid (uid)
143           (error) User id uid running amcheck could not be found in the
144           system password information.
145
146       ERROR: running as user runuser instead of dumpuser
147           (error) Amcheck should be run as the dump user dumpuser from
148           amanda.conf instead of runuser.
149
150       ERROR: program dir directory: not accessible
151           (error) The directory Amanda expects to find its auxiliary programs
152           in, directory, is not accessible.
153
154       ERROR: program program: does not exist
155           (error) Program program needed on the tape server could not be
156           found.
157
158       ERROR: program program: not a file
159           (error) Program program needed on the tape server exists but is not
160           a file.
161
162       ERROR: program program: not executable
163           (error) Program program needed on the tape server exists but is not
164           executable.
165
166       WARNING: program program: not setuid-root
167           (warning) Program program needed on the tape server exists but
168           should be owned by user "root" and setuid.
169
170       ERROR: XXX dir directory: not writable
171           (error) Directory directory is either not writable, i.e. the dump
172           user will not be able to create or remove files, or cannot be
173           accessed, perhaps because a parent directory does not allow search
174           permission. The XXX may be:
175
176           log
177               for the Amanda log directory (see logdir in amanda.conf)
178
179           oldlog
180               for the directory that holds the old log files (see logdir in
181               amanda.conf)
182
183           info
184               for an Amanda database information directory (see curinfo in
185               amanda.conf) or
186
187           index
188               for an Amanda index directory (see indexdir in amanda.conf)
189
190           tapelist
191               for the tapelist(5)
192
193
194       NOTE: XXX dir directory: does not exist
195           (info) A database (info) or index directory does not exist or
196           cannot be accessed. This might just mean this is a new client or
197           disk, but if that is not the case, this should be treated as an
198           error.
199
200       NOTE: it will be created on the next run
201           (info) This indicates the info directory listed in the previous
202           message will be created on the next run.
203
204       ERROR: XXX dir name: not a directory
205           (error) Amcheck expected name to be a directory, but it is
206           something else (e.g. file).
207
208       WARNING: info file file: does not exist
209           (warning) File file does not exist in the text format database.
210           Since the parent directories do exist, the file should already have
211           been created.
212
213       ERROR: info file name: not a file
214           (error) Amcheck expected name to be a file, but it is something
215           else (e.g. file).
216
217       ERROR: info file file: not readable
218           (error) The text format database file file is not readable.
219
220       ERROR: log file file: not writable
221           (error) Log file file (file log in logdir from amanda.conf) is
222           either not writable, or cannot be accessed, perhaps because a
223           parent directory does not allow search permission.
224
225       ERROR: tape list tapelist: not writable
226           (error) tapelist(5) is not writable or was not found.
227
228       ERROR: tape list tapelist: parse error
229           (error) tapelist(5) could not be read or parsed.
230
231       WARNING: tapedev is /dev/null, dumps will be thrown away
232           (warning) The tapedev parameter in amanda.conf is set to /dev/null
233           and Amanda uses that when debugging to throw all the dump images
234           away.
235
236       WARNING: hold file file exists
237           (info) Hold file file exists and will cause amdump to pause at the
238           beginning until it is removed.
239
240       ERROR: holding disk disk: statfs: error message
241           (error) An error was returned from the statfs system call on
242           holding disk disk (maybe because it does not exist).
243
244       ERROR: holding disk disk: not writable
245           (error) Holding disk disk, is not writable, probably because the
246           caller does not have write permission or a parent directory does
247           not allow search permission.
248
249       WARNING: holding disk disk: available space unknown N KB requested.
250           (warning) Amcheck could not determine the amount of available space
251           on holding disk disk to see if there were at least N KBytes
252           available.
253
254       WARNING: holding disk disk: only F KB free (R KB requested).
255           (warning) amanda.conf requested R KBytes of free space on holding
256           disk disk, but only F KBytes were available. 10 MBytes is
257           subtracted for each backup process (see the inparallelamanda.conf
258           option) to allow for unexpected overruns.
259
260               Note
261               Even though this message is listed as a warning, it causes
262               amcheck to exit with a non-zero status.
263
264       Holding disk disk: N KB disk space available, that's plenty.
265           (info) There was sufficient free space on holding disk disk.
266
267       WARNING: holding disk disk: only F KB free, using nothing
268           (warning) Holding disk disk has F KBytes of free space, but that is
269           not enough for what is requested in amanda.conf.
270
271       Holding disk disk: F KB disk space available, using U KB
272           (info) Holding disk disk has F KBytes of free space and Amanda will
273           be using up to U Kbytes.
274
275       WARNING: if a tape changer is not available, runtapes must be set to 1.
276           (warning) The runtapesamanda.conf option must be set to 1 if the
277           tpchangeramanda.conf option is not set.
278
279       ERROR: error message.
280           (error) An error was detected while initializing the tape changer.
281
282       ERROR: tape device: error message.
283           (error) An error was detected while processing the tape label.
284
285       ERROR: cannot overwrite active tape label.
286           (error) Tape label is still active and cannot be used.
287
288       ERROR: label label doesn't match labelstr pattern .
289           (error) The label on tape label does not match the
290           labelstramanda.conf option.
291
292       (expecting a new tape)
293           (info) The tape is not OK and a new tape was expected.
294
295       (expecting tape label or a new tape)
296           (info) The tape is not OK and either tape label or a new tape was
297           expected.
298
299       ERROR: tape label label ok, but is not writable.
300           (error) Tape label is OK, but the write enable test failed.
301
302       Tape label is writable.
303           (info) Tape label is OK and the write enable test succeeded.
304
305       NOTE: skipping tape-writable test.
306           (info) The tape write test (see the -w option) was not enabled.
307
308       WARNING: skipping tape test because amdump or amflush seem to be
309       running, WARNING: if they are not, you must run amcleanup
310           (warning) It looked to amcheck like either amdump or amflush were
311           running because a log file or amdump file exists. If they are not
312           running, you probably need to run amcleanup to clear up a previous
313           failure. Otherwise, you need to wait until they complete before
314           running amcheck.
315
316       NOTE: skipping tape checks
317           (info) The tape tests are being skipped because you used the -t
318           command line option.
319
320       WARNING: compress is not executable, server-compression and indexing
321       will not work
322           (warning) Compression program compress is not executable, so
323           compression on the tape server host and creating index files will
324           not work.
325
326       Tape label label ok.
327           (info) Tape label is OK for the next run.
328
329       Server check took S seconds.
330           (info) Reports how long the tape server host checks took.
331
332       ERROR: host: could not resolve hostname
333           (error) Could not look up client hostname host.
334
335       Client check: H hosts checked in S seconds, N problems found.
336           (info) Reports the number of client hosts checked, how long it took
337           and the number of errors detected.
338
339       WARNING: host: selfcheck request timed out. Host down?
340           (warning) There was no response from host when trying to do the
341           client checks. The host might really be down or it might not be
342           configured properly.
343
344       ERROR: host NAK: message
345           (error) Host reported a negative acknowledgment error of message to
346           the status check request.
347
348       ERROR: host NAK: [NAK parse failed]
349           (error) Amcheck could not parse the negative acknowledgment error
350           from host. There might be an Amanda version mismatch between the
351           host running amcheck and host.
352
353       ERROR: host [mutual-authentication failed]
354           (error) Kerberos authentication failed while contacting host.
355
356       ERROR: host: message
357           (error) Error message was reported by the status check on host.
358

EXIT CODE

360       The exit code of amcheck is one of:
361        0  = success
362        1  = error
363

SEE ALSO

365       amanda(8), amanda.conf(5), amdump(8)
366
367       The Amanda Wiki: : http://wiki.zmanda.com/
368

AUTHORS

370       James da Silva <jds@amanda.org>
371
372       Stefan G. Weichinger <sgw@amanda.org>
373
374
375
376Amanda 3.5.1                      12/01/2017                        AMCHECK(8)
Impressum