Re: Strange Error with Amanda

2002-02-15 Thread John R. Jackson

>DailySet1 AMANDA MAIL REPORT FOR BogusMonth 0, 0
>
>*** THE DUMPS DID NOT FINISH PROPERLY!
>
>These dumps were to tapes .
>Tonight's dumps should go onto 1 tape: Daily03.
>
>FAILURE AND STRANGE DUMP SUMMARY:
>  chaffee/ RESULTS MISSING
>etc. (Every filesystem & server RESULTS MISSING)

I'd start by checking the permissions on **everything** in your Amanda
config areas, such as the directories, the curinfo area, the tapelist
file, the log.MMDD.NN files, etc (btw, amcheck at 2.4.2p2 will do
that for you -- you might consider upgrading).

Next, look through the log.MMDD.NN file for this report, if there
is any.

Next, look through the amdump.NN file for anything odd (compare it with
a good run).

Also look for core files in the amanda.conf or /tmp/amanda area.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]



Strange Error with Amanda

2002-02-13 Thread Wayne Byarlay

Greetings.

I have encountered a weird problem. Everything's been running fine for
months; running a 15-tape rotation cycle and backing up maybe about 36
filesystems on about 8 servers or so.

But this morning, I get the e-mail which Amanda dutifully sends every
morning... it says:
--

DailySet1 AMANDA MAIL REPORT FOR BogusMonth 0, 0

*** THE DUMPS DID NOT FINISH PROPERLY!

These dumps were to tapes .
Tonight's dumps should go onto 1 tape: Daily03.

FAILURE AND STRANGE DUMP SUMMARY:
  chaffee/ RESULTS MISSING
etc. (Every filesystem & server RESULTS MISSING)

STATISTICS:
  Total   Full  Daily
      
Dump Time (hrs:min)0:00   0:00   0:00   (0:00 start)
Output Size (meg)   0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%)   0.00.00.0
Filesystems Dumped0  0  0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --


DUMP SUMMARY:
  DUMPER STATS  TAPER
STATS
HOSTNAME  DISK   L  ORIG-KB   OUT-KB COMP%  MMM:SS   KB/s  MMM:SS
KB/s
-- -- --

chaffee/
MISSING 
(etc every filesystem & server, MISSING)

(brought to you by Amanda version 2.4.1p1)

Interesting, eh? Does anybody have a guess what could cause this?