1AMCHECK(8) 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 OVERWRITE" 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
78 Amanda Tape Server Host Check
79 -----------------------------
80 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
81 NOTE: skipping tape-writable test.
82 Tape VOL10 label ok.
83 Server check took 34.966 seconds.
84 Amanda Backup Client Hosts Check
86 --------------------------------
87 WARNING: northstar: selfcheck request timed out. Host down?
88 WARNING: drinkme: selfcheck request timed out. Host down?
89 WARNING: scruffy: selfcheck request timed out. Host down?
90 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
91 (brought to you by Amanda 2.5.0)
93 In this example, if the line mailto csd-amanda is in amanda.conf, mail
95 will be sent to csd-amanda if the server check returns an error.
96 % amcheck -s -m daily
98
100 fatal slot slot: error message
101 (error) The tape changer detected some kind of fatal error while
102 trying to load slot slot.
103 slot slot: error message
105 (warning) The tape changer detected some kind of non-fatal error
106 (e.g. an empty slot was detected) while trying to load slot slot,
107 or an error was detected trying to read the tape label.
108 slot slot: date YYYYMMDD label label (result)
110 (info) Tape label in slot slot was loaded and found to have been
111 last written on YYYYMMDD. If the tape is new, the date field will
112 be an X. The result may be one of:
113 exact label match
115 This is the expected tape.
116 no match
118 This label does not match the labelstr pattern in
119 amanda.conf. Tape scanning will continue.
120 active tape
122 This tape is still active and cannot be overwritten. Tape
123 scanning will continue.
124 first labelstr match
126 This tape is the first one that matches the labelstr
127 pattern in amanda.conf. Tape scanning will continue if
128 necessary.
129 labelstr match
131 This tape is the next one that matches the labelstr pattern
132 in amanda.conf. Tape scanning will continue.
133 ERROR: cannot look up dump user user
137 (error) Dump user user from amanda.conf could not be found in the
138 system password information.
139 ERROR: cannot look up my own uid (uid)
141 (error) User id uid running amcheck could not be found in the
142 system password information.
143 ERROR: running as user runuser instead of dumpuser
145 (error) Amcheck should be run as the dump user dumpuser from
146 amanda.conf instead of runuser.
147 ERROR: program dir directory: not accessible
149 (error) The directory Amanda expects to find its auxiliary programs
150 in, directory, is not accessible.
151 ERROR: program program: does not exist
153 (error) Program program needed on the tape server could not be
154 found.
155 ERROR: program program: not a file
157 (error) Program program needed on the tape server exists but is not
158 a file.
159 ERROR: program program: not executable
161 (error) Program program needed on the tape server exists but is not
162 executable.
163 WARNING: program program: not setuid-root
165 (warning) Program program needed on the tape server exists but
166 should be owned by user "root" and setuid.
167 ERROR: XXX dir directory: not writable
169 (error) Directory directory is either not writable, i.e. the dump
170 user will not be able to create or remove files, or cannot be
171 accessed, perhaps because a parent directory does not allow search
172 permission. The XXX may be:
173 log
175 for the Amanda log directory (see logdir in amanda.conf)
176 oldlog
178 for the directory that holds the old log files (see logdir
179 in amanda.conf)
180 info
182 for an Amanda database information directory (see curinfo
183 in amanda.conf) or
184 index
186 for an Amanda index directory (see indexdir in amanda.conf)
187 tapelist
189 for the Amanda tapelist directory (see tapelist in
190 amanda.conf)
191 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 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 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 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 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 ERROR: info file file: not readable
218 (error) The text format database file file is not readable.
219 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 ERROR: tape list tapelist: not writable
226 (error) Amanda tape list file tapelist (see tapelist in
227 amanda.conf) is not writable or was not found.
228 ERROR: tape list tapelist: parse error
230 (error) Amanda tape list file tapelist (see tapelist in
231 amanda.conf) could not be read or parsed.
232 WARNING: tapedev is /dev/null, dumps will be thrown away
234 (warning) The tapedev parameter in amanda.conf is set to /dev/null
235 and Amanda uses that when debugging to throw all the dump images
236 away.
237 WARNING: hold file file exists
239 (info) Hold file file exists and will cause amdump to pause at the
240 beginning until it is removed.
241 ERROR: holding disk disk: statfs: error message
243 (error) An error was returned from the statfs system call on
244 holding disk disk (maybe because it does not exist).
245 ERROR: holding disk disk: not writable
247 (error) Holding disk disk, is not writable, probably because the
248 caller does not have write permission or a parent directory does
249 not allow search permission.
250 WARNING: holding disk disk: available space unknown N KB requested.
252 (warning) Amcheck could not determine the amount of available space
253 on holding disk disk to see if there were at least N KBytes
254 available.
255 WARNING: holding disk disk: only F KB free (R KB requested).
257 (warning) amanda.conf requested R KBytes of free space on holding
258 disk disk, but only F KBytes were available. 10 MBytes is
259 subtracted for each backup process (see the inparallel amanda.conf
260 option) to allow for unexpected overruns.
261 Note
263 Even though this message is listed as a warning, it causes amcheck
264 to exit with a non-zero status.
265 Holding disk disk: N KB disk space available, that's plenty.
267 (info) There was sufficient free space on holding disk disk.
268 WARNING: holding disk disk: only F KB free, using nothing
270 (warning) Holding disk disk has F KBytes of free space, but that is
271 not enough for what is requested in amanda.conf.
272 Holding disk disk: F KB disk space available, using U KB
274 (info) Holding disk disk has F KBytes of free space and Amanda will
275 be using up to U Kbytes.
276 WARNING: if a tape changer is not available, runtapes must be set to 1.
278 (warning) The runtapes amanda.conf option must be set to 1 if the
279 tpchanger amanda.conf option is not set.
280 ERROR: error message.
282 (error) An error was detected while initializing the tape changer.
283 ERROR: tape device: error message.
285 (error) An error was detected while processing the tape label.
286 ERROR: cannot overwrite active tape label.
288 (error) Tape label is still active and cannot be used.
289 ERROR: label label doesn't match labelstr pattern .
291 (error) The label on tape label does not match the labelstr
292 amanda.conf option.
293 (expecting a new tape)
295 (info) The tape is not OK and a new tape was expected.
296 (expecting tape label or a new tape)
298 (info) The tape is not OK and either tape label or a new tape was
299 expected.
300 ERROR: tape label label ok, but is not writable.
302 (error) Tape label is OK, but the write enable test failed.
303 Tape label is writable.
305 (info) Tape label is OK and the write enable test succeeded.
306 NOTE: skipping tape-writable test.
308 (info) The tape write test (see the -w option) was not enabled.
309 WARNING: skipping tape test because amdump or amflush seem to be
311 running, WARNING: if they are not, you must run amcleanup
312 (warning) It looked to amcheck like either amdump or amflush were
313 running because a log file or amdump file exists. If they are not
314 running, you probably need to run amcleanup to clear up a previous
315 failure. Otherwise, you need to wait until they complete before
316 running amcheck.
317 NOTE: skipping tape checks
319 (info) The tape tests are being skipped because you used the -t
320 command line option.
321 WARNING: compress is not executable, server-compression and indexing
323 will not work
324 (warning) Compression program compress is not executable, so
325 compression on the tape server host and creating index files will
326 not work.
327 Tape label label ok.
329 (info) Tape label is OK for the next run.
330 Server check took S seconds.
332 (info) Reports how long the tape server host checks took.
333 ERROR: host: could not resolve hostname
335 (error) Could not look up client hostname host.
336 Client check: H hosts checked in S seconds, N problems found.
338 (info) Reports the number of client hosts checked, how long it took
339 and the number of errors detected.
340 WARNING: host: selfcheck request timed out. Host down?
342 (warning) There was no response from host when trying to do the
343 client checks. The host might really be down or it might not be
344 configured properly.
345 ERROR: host NAK: message
347 (error) Host reported a negative acknowledgment error of message to
348 the status check request.
349 ERROR: host NAK: [NAK parse failed]
351 (error) Amcheck could not parse the negative acknowledgment error
352 from host. There might be an Amanda version mismatch between the
353 host running amcheck and host.
354 ERROR: host [mutual-authentication failed]
356 (error) Kerberos authentication failed while contacting host.
357 ERROR: host: message
359 (error) Error message was reported by the status check on host.
360
362 James da Silva, <jds@amanda.org> : Original text
363 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the
365 Amanda-documentation: XML-conversion
366
368 amanda(8), amdump(8)
369 02/07/2007 AMCHECK(8)