Re: amreport analysis



Dustin J. Mitchell wrote:

On Dec 14, 2007 11:11 AM, Tom Herrera <therrera AT nvisia DOT com> wrote:

? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error


These are a problem.  You should add an exclude for /mnt to your DLE:

brain.milw / {
  WHATEVER_DUMPTYPE_YOU_HAD
  exclude list append "./mnt"
  } -1 le0

| gtar: ./lib/dev-state/gpmctl: socket ignored
| gtar: ./lib/dev-state/log: socket ignored
| gtar: ./opt/IBMHTTPServer-V1.x/logs/siddport: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26158: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26307: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.26386: socket ignored
| gtar: ./opt/IBMHttpServer/conf/socket.27585: socket ignored
| gtar: ./opt/save-IBMHTTPServer/logs/siddport: socket ignored


These are harmless, but you can exclude them, too, if you'd like.



Minor correction:  they are harmless indeed, but you do not need
to exclude them, because Amanda expects that output, and classifies
it as "normal".  You will not see these "normal" lines in the report
unless there are also "error" or "strange" lines.

Each output line of the dumpprogram (gtar above) is classified
as "normal"  All the other lines are flagged with a question mark.
When the return code of gtar indicates success, but contains
unexpected lines, Amanda flags the dump as strange, but still puts
in on tape.  Amanda leaves it up to you to interpret the strange
lines, and see if they are harmful or not.
When the return code of gtar indicates a failure, those non-normal
output lines are probably the cause of the error.

When informing you about "strange" or "error" in the report, Amanda
always shows the complete output, including the "normal" lines, to
allow you to interpret those lines in the context.