3 Prev Chapter 35. The AMANDA Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amcheck
\14 run AMANDA self-checks
13 amcheck [-mwsclt ] [-Maddress ] config [ host [disk...]...]
17 Amcheck runs a number of self-checks on both the AMANDA tape server host and
18 the AMANDA client hosts.
19 On the tape server host, amcheck can go through the same tape checking used at
20 the start of the nightly amdump run to verify the correct tape for the next run
22 Amcheck can also do a self-check on all client hosts to make sure each host is
23 running and that permissions on filesystems to be backed up are correct.
24 You can specify many host/disk expressions, only disks that match an expression
25 will be checked. All disks are checked if no expressions are given.
26 See the amanda(8) man page for more details about AMANDA.
33 Run the tape server local and tape checks (same as -lt).
36 Run the client host checks.
39 Run the local tests (e.g. permissions) on the server host.
42 Run the tape tests on the server host.
45 Enables a destructive check for write-protection on the tape (which would
46 otherwise cause the subsequent amdump to fail). If the tape is writable,
47 this check causes all data after the tape label to be erased (actually
48 depends on the device driver: there is no portable non-destructive way to
49 check for write-protection). The check implies -t and is only made if the
50 tape is otherwise correct.
53 Nothing is printed, but mail is sent if any errors are detected. The mail
54 goes to the mailto address specified in the amanda.conf file or the
55 address value if -M is set.
58 Like -m but the mail is always sent.
61 Mail the report to address instead of the mailto value from amanda.conf.
68 In this example, both the tape server and client tests are run. The results are
69 displayed on standard output.
72 AMANDA Tape Server Host Check
73 -----------------------------
74 /amanda2/amanda/work: 911475 KB disk space available, that's plenty.
75 NOTE: skipping tape-writable test.
77 Server check took 34.966 seconds.
79 AMANDA Backup Client Hosts Check
80 --------------------------------
81 WARNING: northstar: selfcheck request timed out. Host down?
82 WARNING: drinkme: selfcheck request timed out. Host down?
83 WARNING: scruffy: selfcheck request timed out. Host down?
84 Client check: 136 hosts checked in 51.945 seconds, 3 problems found.
86 (brought to you by AMANDA 2.4.5)
88 In this example, if the line mailto csd-amanda is in amanda.conf, mail will be
89 sent to csd-amanda if the server check returns an error.
98 fatal slot slot: error message
99 (error) The tape changer detected some kind of fatal error while trying
102 slot slot: error message
103 (warning) The tape changer detected some kind of non-fatal error (e.g. an
104 empty slot was detected) while trying to load slot slot, or an error was
105 detected trying to read the tape label.
107 slot slot: date YYYYMMDD label label (result)
108 (info) Tape label in slot slot was loaded and found to have been last
109 written on YYYYMMDD. If the tape is new, the date field will be an X. The
110 result may be one of:
114 This is the expected tape.
117 This label does not match the labelstr pattern in amanda.conf. Tape
118 scanning will continue.
121 This tape is still active and cannot be overwritten. Tape scanning
125 This tape is the first one that matches the labelstr pattern in
126 amanda.conf. Tape scanning will continue if necessary.
129 This tape is the next one that matches the labelstr pattern in
130 amanda.conf. Tape scanning will continue.
133 ERROR: cannot look up dump user user
134 (error) Dump user user from amanda.conf could not be found in the system
135 password information.
137 ERROR: cannot look up my own uid (uid)
138 (error) User id uid running amcheck could not be found in the system
139 password information.
141 ERROR: running as user runuser instead of dumpuser
142 (error) Amcheck should be run as the dump user dumpuser from amanda.conf
145 ERROR: program dir directory: not accessible
146 (error) The directory AMANDA expects to find its auxiliary programs in,
147 directory, is not accessible.
149 ERROR: program program: does not exist
150 (error) Program program needed on the tape server could not be found.
152 ERROR: program program: not a file
153 (error) Program program needed on the tape server exists but is not a
156 ERROR: program program: not executable
157 (error) Program program needed on the tape server exists but is not
160 WARNING: program program: not setuid-root
161 (warning) Program program needed on the tape server exists but should be
162 owned by user "root" and setuid.
164 ERROR: XXX dir directory: not writable
165 (error) Directory directory is either not writable, i.e. the dump user
166 will not be able to create or remove files, or cannot be accessed,
167 perhaps because a parent directory does not allow search permission. The
172 for the AMANDA log directory (see logdir in amanda.conf)
175 for the directory that holds the old log files (see logdir in
179 for an AMANDA database information directory (see curinfo in
183 for an AMANDA index directory (see indexdir in amanda.conf)
186 for the AMANDA tapelist directory (see tapelist in amanda.conf)
189 NOTE: XXX dir directory: does not exist
190 (info) A database (info) or index directory does not exist or cannot be
191 accessed. This might just mean this is a new client or disk, but if that
192 is not the case, this should be treated as an error.
194 NOTE: it will be created on the next run
195 (info) This indicates the info directory listed in the previous message
196 will be created on the next run.
198 ERROR: XXX dir name: not a directory
199 (error) Amcheck expected name to be a directory, but it is something else
202 WARNING: info file file: does not exist
203 (warning) File file does not exist in the text format database. Since the
204 parent directories do exist, the file should already have been created.
206 ERROR: info file name: not a file
207 (error) Amcheck expected name to be a file, but it is something else
210 ERROR: info file file: not readable
211 (error) The text format database file file is not readable.
213 ERROR: log file file: not writable
214 (error) Log file file (file log in logdir from amanda.conf) is either not
215 writable, or cannot be accessed, perhaps because a parent directory does
216 not allow search permission.
218 ERROR: tape list tapelist: not writable
219 (error) AMANDA tape list file tapelist (see tapelist in amanda.conf) is
220 not writable or was not found.
222 ERROR: tape list tapelist: parse error
223 (error) AMANDA tape list file tapelist (see tapelist in amanda.conf)
224 could not be read or parsed.
226 WARNING: tapedev is /dev/null, dumps will be thrown away
227 (warning) The tapedev parameter in amanda.conf is set to /dev/null and
228 AMANDA uses that when debugging to throw all the dump images away.
230 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.
234 ERROR: holding disk disk: statfs: error message
235 (error) An error was returned from the statfs system call on holding disk
236 disk (maybe because it does not exist).
238 ERROR: holding disk disk: not writable
239 (error) Holding disk disk, is not writable, probably because the caller
240 does not have write permission or a parent directory does not allow
243 WARNING: holding disk disk: available space unknown N KB requested.
244 (warning) Amcheck could not determine the amount of available space on
245 holding disk disk to see if there were at least N KBytes available.
247 WARNING: holding disk disk: only F KB free (R KB requested).
248 (warning) amanda.conf requested R KBytes of free space on holding disk
249 disk, but only F KBytes were available. 10 MBytes is subtracted for each
250 backup process (see the inparallel amanda.conf option) to allow for
255 Even though this message is listed as a warning, it causes amcheck to
256 exit with a non-zero status.
260 Holding disk disk: N KB disk space available, that's plenty.
261 (info) There was sufficient free space on holding disk disk.
263 WARNING: holding disk disk: only F KB free, using nothing
264 (warning) Holding disk disk has F KBytes of free space, but that is not
265 enough for what is requested in amanda.conf.
267 Holding disk disk: F KB disk space available, using U KB
268 (info) Holding disk disk has F KBytes of free space and AMANDA will be
269 using up to U Kbytes.
271 WARNING: if a tape changer is not available, runtapes must be set to 1.
272 (warning) The runtapes amanda.conf option must be set to 1 if the
273 tpchanger amanda.conf option is not set.
275 ERROR: error message.
276 (error) An error was detected while initializing the tape changer.
278 ERROR: tape device: error message.
279 (error) An error was detected while processing the tape label.
281 ERROR: cannot overwrite active tape label.
282 (error) Tape label is still active and cannot be used.
284 ERROR: label label doesn't match labelstr pattern .
285 (error) The label on tape label does not match the labelstr amanda.conf
288 (expecting a new tape)
289 (info) The tape is not OK and a new tape was expected.
291 (expecting tape label or a new tape)
292 (info) The tape is not OK and either tape label or a new tape was
295 ERROR: tape label label ok, but is not writable.
296 (error) Tape label is OK, but the write enable test failed.
298 Tape label is writable.
299 (info) Tape label is OK and the write enable test succeeded.
301 NOTE: skipping tape-writable test.
302 (info) The tape write test (see the -w option) was not enabled.
304 WARNING: skipping tape test because amdump or amflush seem to be running,
305 WARNING: if they are not, you must run amcleanup,
306 (warning) It looked to amcheck like either amdump or amflush were running
307 because a log file or amdump file exists. If they are not running, you
308 probably need to run amcleanup to clear up a previous failure. Otherwise,
309 you need to wait until they complete before running amcheck.
311 NOTE: skipping tape checks
312 (info) The tape tests are being skipped because you used the -t command
315 WARNING: compress is not executable, server-compression and indexing will not
317 (warning) Compression program compress is not executable, so compression
318 on the tape server host and creating index files will not work.
321 (info) Tape label is OK for the next run.
323 Server check took S seconds.
324 (info) Reports how long the tape server host checks took.
326 ERROR: host: could not resolve hostname
327 (error) Could not look up client hostname host.
329 Client check: H hosts checked in S seconds, N problems found.
330 (info) Reports the number of client hosts checked, how long it took and
331 the number of errors detected.
333 WARNING: host: selfcheck request timed out. Host down?
334 (warning) There was no response from host when trying to do the client
335 checks. The host might really be down or it might not be configured
338 ERROR: host NAK: message
339 (error) Host reported a negative acknowledgment error of message to the
340 status check request.
342 ERROR: host NAK: [NAK parse failed]
343 (error) Amcheck could not parse the negative acknowledgment error from
344 host. There might be an AMANDA version mismatch between the host running
347 ERROR: host [mutual-authentication failed]
348 (error) Kerberos authentication failed while contacting host.
351 (error) Error message was reported by the status check on host.
356 James da Silva, <jds@amanda.org> : Original text
357 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the AMANDA-documentation:
363 -------------------------------------------------------------------------------
366 amanda.conf Home amcheckdb