1AMCHECK(8) System Administration Commands AMCHECK(8)
2
6 amcheck - run Amanda self-checks
7
9 amcheck [-am] [-w] [-sclt] [-M address] config [host [disk...]...]
10 [-o configoption]...
11
13 Amcheck runs a number of self-checks on both the Amanda tape server
14 host and the Amanda client hosts.
15 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 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 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 See the amanda(8) man page for more details about Amanda.
29
31 -s
32 Run the tape server local and tape checks (same as -lt).
33 -c
35 Run the client host checks. Multiple specific clients can be
36 checked by specifying the client name.
37 -l
39 Run the local tests (e.g. permissions) on the server host.
40 -t
42 Run the tape tests on the server host.
43 -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 label_new_tapes option is enabled, this check may
49 ERASE any non-Amanda tape in the drive or changer. The check enable
50 the tape tests on the server host and is only made if the tape is
51 otherwise correct.
52 -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 -a
59 Like -m but the mail is always sent.
60 -M address
62 Mail the report to address instead of the mailto value from
63 amanda.conf. Implies -m.
64 host [disk]*
66 Specify the host and disk on which the command will work.
67 -o configoption
69 See the "CONFIGURATION OVERRIDE" section in amanda(8).
70 The default is -cs.
72
74 In this example, both the tape server and client tests are run. The
75 results are displayed on standard output.
76 % amcheck daily
77 Amanda Tape Server Host Check
78 -----------------------------
79 /amanda2/amanda/work: 911475 KB disk space available, that´s plenty.
80 NOTE: skipping tape-writable test.
81 Tape VOL10 label ok.
82 Server check took 34.966 seconds.
83 Amanda Backup Client Hosts Check
85 --------------------------------
86 WARNING: northstar: selfcheck request timed out. Host down?
87 WARNING: drinkme: selfcheck request timed out. Host down?
88 WARNING: scruffy: selfcheck request timed out. Host down?
89 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
90 (brought to you by Amanda 2.5.0)
92 In this example, if the line mailto csd-amanda is in amanda.conf, mail
94 will be sent to csd-amanda if the server check returns an error.
95 % amcheck -s -m daily
96
98 fatal slot slot: error message
99 (error) The tape changer detected some kind of fatal error while
100 trying to load slot slot.
101 slot slot: error message
103 (warning) The tape changer detected some kind of non-fatal error
104 (e.g. an empty slot was detected) while trying to load slot slot,
105 or an error was detected trying to read the tape label.
106 slot slot: date YYYYMMDD label label (result)
108 (info) Tape label in slot slot was loaded and found to have been
109 last written on YYYYMMDD. If the tape is new, the date field will
110 be an X. The result may be one of:
111 exact label match
113 This is the expected tape.
114 no match
116 This label does not match the labelstr pattern in amanda.conf.
117 Tape scanning will continue.
118 active tape
120 This tape is still active and cannot be overwritten. Tape
121 scanning will continue.
122 first labelstr match
124 This tape is the first one that matches the labelstr pattern in
125 amanda.conf. Tape scanning will continue if necessary.
126 labelstr match
128 This tape is the next one that matches the labelstr pattern in
129 amanda.conf. Tape scanning will continue.
130 ERROR: cannot look up dump user user
133 (error) Dump user user from amanda.conf could not be found in the
134 system password information.
135 ERROR: cannot look up my own uid (uid)
137 (error) User id uid running amcheck could not be found in the
138 system password information.
139 ERROR: running as user runuser instead of dumpuser
141 (error) Amcheck should be run as the dump user dumpuser from
142 amanda.conf instead of runuser.
143 ERROR: program dir directory: not accessible
145 (error) The directory Amanda expects to find its auxiliary programs
146 in, directory, is not accessible.
147 ERROR: program program: does not exist
149 (error) Program program needed on the tape server could not be
150 found.
151 ERROR: program program: not a file
153 (error) Program program needed on the tape server exists but is not
154 a file.
155 ERROR: program program: not executable
157 (error) Program program needed on the tape server exists but is not
158 executable.
159 WARNING: program program: not setuid-root
161 (warning) Program program needed on the tape server exists but
162 should be owned by user "root" and setuid.
163 ERROR: XXX dir directory: not writable
165 (error) Directory directory is either not writable, i.e. the dump
166 user will not be able to create or remove files, or cannot be
167 accessed, perhaps because a parent directory does not allow search
168 permission. The XXX may be:
169 log
171 for the Amanda log directory (see logdir in amanda.conf)
172 oldlog
174 for the directory that holds the old log files (see logdir in
175 amanda.conf)
176 info
178 for an Amanda database information directory (see curinfo in
179 amanda.conf) or
180 index
182 for an Amanda index directory (see indexdir in amanda.conf)
183 tapelist
185 for the tapelist(5)
186 NOTE: XXX dir directory: does not exist
189 (info) A database (info) or index directory does not exist or
190 cannot be accessed. This might just mean this is a new client or
191 disk, but if that is not the case, this should be treated as an
192 error.
193 NOTE: it will be created on the next run
195 (info) This indicates the info directory listed in the previous
196 message will be created on the next run.
197 ERROR: XXX dir name: not a directory
199 (error) Amcheck expected name to be a directory, but it is
200 something else (e.g. file).
201 WARNING: info file file: does not exist
203 (warning) File file does not exist in the text format database.
204 Since the parent directories do exist, the file should already have
205 been created.
206 ERROR: info file name: not a file
208 (error) Amcheck expected name to be a file, but it is something
209 else (e.g. file).
210 ERROR: info file file: not readable
212 (error) The text format database file file is not readable.
213 ERROR: log file file: not writable
215 (error) Log file file (file log in logdir from amanda.conf) is
216 either not writable, or cannot be accessed, perhaps because a
217 parent directory does not allow search permission.
218 ERROR: tape list tapelist: not writable
220 (error) tapelist(5) is not writable or was not found.
221 ERROR: tape list tapelist: parse error
223 (error) tapelist(5) could not be read or parsed.
224 WARNING: tapedev is /dev/null, dumps will be thrown away
226 (warning) The tapedev parameter in amanda.conf is set to /dev/null
227 and Amanda uses that when debugging to throw all the dump images
228 away.
229 WARNING: hold file file exists
231 (info) Hold file file exists and will cause amdump to pause at the
232 beginning until it is removed.
233 ERROR: holding disk disk: statfs: error message
235 (error) An error was returned from the statfs system call on
236 holding disk disk (maybe because it does not exist).
237 ERROR: holding disk disk: not writable
239 (error) Holding disk disk, is not writable, probably because the
240 caller does not have write permission or a parent directory does
241 not allow search permission.
242 WARNING: holding disk disk: available space unknown N KB requested.
244 (warning) Amcheck could not determine the amount of available space
245 on holding disk disk to see if there were at least N KBytes
246 available.
247 WARNING: holding disk disk: only F KB free (R KB requested).
249 (warning) amanda.conf requested R KBytes of free space on holding
250 disk disk, but only F KBytes were available. 10 MBytes is
251 subtracted for each backup process (see the inparallel amanda.conf
252 option) to allow for unexpected overruns.
253 Note
255 Even though this message is listed as a warning, it causes
256 amcheck to exit with a non-zero status.
257 Holding disk disk: N KB disk space available, that´s plenty.
259 (info) There was sufficient free space on holding disk disk.
260 WARNING: holding disk disk: only F KB free, using nothing
262 (warning) Holding disk disk has F KBytes of free space, but that is
263 not enough for what is requested in amanda.conf.
264 Holding disk disk: F KB disk space available, using U KB
266 (info) Holding disk disk has F KBytes of free space and Amanda will
267 be using up to U Kbytes.
268 WARNING: if a tape changer is not available, runtapes must be set to 1.
270 (warning) The runtapes amanda.conf option must be set to 1 if the
271 tpchanger amanda.conf option is not set.
272 ERROR: error message.
274 (error) An error was detected while initializing the tape changer.
275 ERROR: tape device: error message.
277 (error) An error was detected while processing the tape label.
278 ERROR: cannot overwrite active tape label.
280 (error) Tape label is still active and cannot be used.
281 ERROR: label label doesn´t match labelstr pattern .
283 (error) The label on tape label does not match the labelstr
284 amanda.conf option.
285 (expecting a new tape)
287 (info) The tape is not OK and a new tape was expected.
288 (expecting tape label or a new tape)
290 (info) The tape is not OK and either tape label or a new tape was
291 expected.
292 ERROR: tape label label ok, but is not writable.
294 (error) Tape label is OK, but the write enable test failed.
295 Tape label is writable.
297 (info) Tape label is OK and the write enable test succeeded.
298 NOTE: skipping tape-writable test.
300 (info) The tape write test (see the -w option) was not enabled.
301 WARNING: skipping tape test because amdump or amflush seem to be
303 running, WARNING: if they are not, you must run amcleanup
304 (warning) It looked to amcheck like either amdump or amflush were
305 running because a log file or amdump file exists. If they are not
306 running, you probably need to run amcleanup to clear up a previous
307 failure. Otherwise, you need to wait until they complete before
308 running amcheck.
309 NOTE: skipping tape checks
311 (info) The tape tests are being skipped because you used the -t
312 command line option.
313 WARNING: compress is not executable, server-compression and indexing
315 will not work
316 (warning) Compression program compress is not executable, so
317 compression on the tape server host and creating index files will
318 not work.
319 Tape label label ok.
321 (info) Tape label is OK for the next run.
322 Server check took S seconds.
324 (info) Reports how long the tape server host checks took.
325 ERROR: host: could not resolve hostname
327 (error) Could not look up client hostname host.
328 Client check: H hosts checked in S seconds, N problems found.
330 (info) Reports the number of client hosts checked, how long it took
331 and the number of errors detected.
332 WARNING: host: selfcheck request timed out. Host down?
334 (warning) There was no response from host when trying to do the
335 client checks. The host might really be down or it might not be
336 configured properly.
337 ERROR: host NAK: message
339 (error) Host reported a negative acknowledgment error of message to
340 the status check request.
341 ERROR: host NAK: [NAK parse failed]
343 (error) Amcheck could not parse the negative acknowledgment error
344 from host. There might be an Amanda version mismatch between the
345 host running amcheck and host.
346 ERROR: host [mutual-authentication failed]
348 (error) Kerberos authentication failed while contacting host.
349 ERROR: host: message
351 (error) Error message was reported by the status check on host.
352
354 The exit code of amcheck is one of:
355 0 = success
356 1 = error
357
359 amanda(8), amdump(8), : http://wiki.zmanda.com
360
362 James da Silva <jds@amanda.org>
363 Stefan G. Weichinger <sgw@amanda.org>
365Amanda 2.6.1p2 11/05/2009 AMCHECK(8)