3 Prev Chapter 36. The Amanda Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amcheck
\14 run Amanda self-checks
13 amcheck [-am] [-w] [-sclt] [-M address] config [ host [disk...] ...] [ -
18 Amcheck runs a number of self-checks on both the Amanda tape server host and
19 the Amanda client hosts.
20 On the tape server host, amcheck can go through the same tape checking used at
21 the start of the nightly amdump run to verify the correct tape for the next run
23 Amcheck can also do a self-check on all client hosts to make sure each host is
24 running and that permissions on filesystems to be backed up are correct.
25 You can specify many host/disk expressions, only disks that match an expression
26 will be checked. All disks are checked if no expressions are given.
27 See the amanda(8) man page for more details about Amanda.
34 Run the tape server local and tape checks (same as -lt).
37 Run the client host checks. Multiple specific clients can be checked by
38 specifying the client name.
41 Run the local tests (e.g. permissions) on the server host.
44 Run the tape tests on the server host.
47 Enables a DESTRUCTIVE check for write-protection on the tape (which would
48 otherwise cause the subsequent amdump to fail). If the tape is writable,
49 this check causes all data after the tape label to be erased. If the
50 label_new_tapes option is enabled, this check may ERASE any non-Amanda
51 tape in the drive or changer. The check enable the tape tests on the
52 server host and is only made if the tape is otherwise correct.
55 Nothing is printed, but mail is sent if any errors are detected. The mail
56 goes to the mailto address specified in the amanda.conf file or the
57 address value if -M is set.
60 Like -m but the mail is always sent.
63 Mail the report to address instead of the mailto value from amanda.conf.
67 Specify the host and disk on which the command will work.
70 See the "CONFIGURATION OVERRIDE" section in amanda(8).
76 In this example, both the tape server and client tests are run. The results are
77 displayed on standard output.
80 Amanda Tape Server Host Check
81 -----------------------------
82 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
83 NOTE: skipping tape-writable test.
85 Server check took 34.966 seconds.
87 Amanda Backup Client Hosts Check
88 --------------------------------
89 WARNING: northstar: selfcheck request timed out. Host down?
90 WARNING: drinkme: selfcheck request timed out. Host down?
91 WARNING: scruffy: selfcheck request timed out. Host down?
92 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
94 (brought to you by Amanda 2.5.0)
96 In this example, if the line mailto csd-amanda is in amanda.conf, mail will be
97 sent to csd-amanda if the server check returns an error.
106 fatal slot slot: error message
107 (error) The tape changer detected some kind of fatal error while trying
110 slot slot: error message
111 (warning) The tape changer detected some kind of non-fatal error (e.g. an
112 empty slot was detected) while trying to load slot slot, or an error was
113 detected trying to read the tape label.
115 slot slot: date YYYYMMDD label label (result)
116 (info) Tape label in slot slot was loaded and found to have been last
117 written on YYYYMMDD. If the tape is new, the date field will be an X. The
118 result may be one of:
122 This is the expected tape.
125 This label does not match the labelstr pattern in amanda.conf. Tape
126 scanning will continue.
129 This tape is still active and cannot be overwritten. Tape scanning
133 This tape is the first one that matches the labelstr pattern in
134 amanda.conf. Tape scanning will continue if necessary.
137 This tape is the next one that matches the labelstr pattern in
138 amanda.conf. Tape scanning will continue.
141 ERROR: cannot look up dump user user
142 (error) Dump user user from amanda.conf could not be found in the system
143 password information.
145 ERROR: cannot look up my own uid (uid)
146 (error) User id uid running amcheck could not be found in the system
147 password information.
149 ERROR: running as user runuser instead of dumpuser
150 (error) Amcheck should be run as the dump user dumpuser from amanda.conf
153 ERROR: program dir directory: not accessible
154 (error) The directory Amanda expects to find its auxiliary programs in,
155 directory, is not accessible.
157 ERROR: program program: does not exist
158 (error) Program program needed on the tape server could not be found.
160 ERROR: program program: not a file
161 (error) Program program needed on the tape server exists but is not a
164 ERROR: program program: not executable
165 (error) Program program needed on the tape server exists but is not
168 WARNING: program program: not setuid-root
169 (warning) Program program needed on the tape server exists but should be
170 owned by user "root" and setuid.
172 ERROR: XXX dir directory: not writable
173 (error) Directory directory is either not writable, i.e. the dump user
174 will not be able to create or remove files, or cannot be accessed,
175 perhaps because a parent directory does not allow search permission. The
180 for the Amanda log directory (see logdir in amanda.conf)
183 for the directory that holds the old log files (see logdir in
187 for an Amanda database information directory (see curinfo in
191 for an Amanda index directory (see indexdir in amanda.conf)
194 for the Amanda tapelist directory (see tapelist in amanda.conf)
197 NOTE: XXX dir directory: does not exist
198 (info) A database (info) or index directory does not exist or cannot be
199 accessed. This might just mean this is a new client or disk, but if that
200 is not the case, this should be treated as an error.
202 NOTE: it will be created on the next run
203 (info) This indicates the info directory listed in the previous message
204 will be created on the next run.
206 ERROR: XXX dir name: not a directory
207 (error) Amcheck expected name to be a directory, but it is something else
210 WARNING: info file file: does not exist
211 (warning) File file does not exist in the text format database. Since the
212 parent directories do exist, the file should already have been created.
214 ERROR: info file name: not a file
215 (error) Amcheck expected name to be a file, but it is something else
218 ERROR: info file file: not readable
219 (error) The text format database file file is not readable.
221 ERROR: log file file: not writable
222 (error) Log file file (file log in logdir from amanda.conf) is either not
223 writable, or cannot be accessed, perhaps because a parent directory does
224 not allow search permission.
226 ERROR: tape list tapelist: not writable
227 (error) Amanda tape list file tapelist (see tapelist in amanda.conf) is
228 not writable or was not found.
230 ERROR: tape list tapelist: parse error
231 (error) Amanda tape list file tapelist (see tapelist in amanda.conf)
232 could not be read or parsed.
234 WARNING: tapedev is /dev/null, dumps will be thrown away
235 (warning) The tapedev parameter in amanda.conf is set to /dev/null and
236 Amanda uses that when debugging to throw all the dump images away.
238 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.
242 ERROR: holding disk disk: statfs: error message
243 (error) An error was returned from the statfs system call on holding disk
244 disk (maybe because it does not exist).
246 ERROR: holding disk disk: not writable
247 (error) Holding disk disk, is not writable, probably because the caller
248 does not have write permission or a parent directory does not allow
251 WARNING: holding disk disk: available space unknown N KB requested.
252 (warning) Amcheck could not determine the amount of available space on
253 holding disk disk to see if there were at least N KBytes available.
255 WARNING: holding disk disk: only F KB free (R KB requested).
256 (warning) amanda.conf requested R KBytes of free space on holding disk
257 disk, but only F KBytes were available. 10 MBytes is subtracted for each
258 backup process (see the inparallel amanda.conf option) to allow for
263 Even though this message is listed as a warning, it causes amcheck to
264 exit with a non-zero status.
268 Holding disk disk: N KB disk space available, that's plenty.
269 (info) There was sufficient free space on holding disk disk.
271 WARNING: holding disk disk: only F KB free, using nothing
272 (warning) Holding disk disk has F KBytes of free space, but that is not
273 enough for what is requested in amanda.conf.
275 Holding disk disk: F KB disk space available, using U KB
276 (info) Holding disk disk has F KBytes of free space and Amanda will be
277 using up to U Kbytes.
279 WARNING: if a tape changer is not available, runtapes must be set to 1.
280 (warning) The runtapes amanda.conf option must be set to 1 if the
281 tpchanger amanda.conf option is not set.
283 ERROR: error message.
284 (error) An error was detected while initializing the tape changer.
286 ERROR: tape device: error message.
287 (error) An error was detected while processing the tape label.
289 ERROR: cannot overwrite active tape label.
290 (error) Tape label is still active and cannot be used.
292 ERROR: label label doesn't match labelstr pattern .
293 (error) The label on tape label does not match the labelstr amanda.conf
296 (expecting a new tape)
297 (info) The tape is not OK and a new tape was expected.
299 (expecting tape label or a new tape)
300 (info) The tape is not OK and either tape label or a new tape was
303 ERROR: tape label label ok, but is not writable.
304 (error) Tape label is OK, but the write enable test failed.
306 Tape label is writable.
307 (info) Tape label is OK and the write enable test succeeded.
309 NOTE: skipping tape-writable test.
310 (info) The tape write test (see the -w option) was not enabled.
312 WARNING: skipping tape test because amdump or amflush seem to be running,
313 WARNING: if they are not, you must run amcleanup
314 (warning) It looked to amcheck like either amdump or amflush were running
315 because a log file or amdump file exists. If they are not running, you
316 probably need to run amcleanup to clear up a previous failure. Otherwise,
317 you need to wait until they complete before running amcheck.
319 NOTE: skipping tape checks
320 (info) The tape tests are being skipped because you used the -t command
323 WARNING: compress is not executable, server-compression and indexing will not
325 (warning) Compression program compress is not executable, so compression
326 on the tape server host and creating index files will not work.
329 (info) Tape label is OK for the next run.
331 Server check took S seconds.
332 (info) Reports how long the tape server host checks took.
334 ERROR: host: could not resolve hostname
335 (error) Could not look up client hostname host.
337 Client check: H hosts checked in S seconds, N problems found.
338 (info) Reports the number of client hosts checked, how long it took and
339 the number of errors detected.
341 WARNING: host: selfcheck request timed out. Host down?
342 (warning) There was no response from host when trying to do the client
343 checks. The host might really be down or it might not be configured
346 ERROR: host NAK: message
347 (error) Host reported a negative acknowledgment error of message to the
348 status check request.
350 ERROR: host NAK: [NAK parse failed]
351 (error) Amcheck could not parse the negative acknowledgment error from
352 host. There might be an Amanda version mismatch between the host running
355 ERROR: host [mutual-authentication failed]
356 (error) Kerberos authentication failed while contacting host.
359 (error) Error message was reported by the status check on host.
364 James da Silva, <jds@amanda.org> : Original text
365 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the Amanda-documentation:
371 -------------------------------------------------------------------------------
374 amanda-client.conf Home amcheckdb