Hi Bdale,
FYI, you mistyped the bug number for this one. It's 361716, not 361715.
So your email got appended to a GCC bug. More info below...
On Thu, 1 Jun 2006, Bdale Garbee wrote:
I have several questions for those of you seeing this problem, to try
and get to the root cause. I don't use amcheck in cron myself, so could
use your help chasing down the problem.
Thanks for following up with this one, I really appreciate your help! I
just did some additional testing and I think I found some useful
data points. More info below...
First, have any of you tried the 2.5.0p2-1 amanda-server package yet?
I just installed it and it has not helped at all.
Second, are the cron entries being run as the right user, most likely
user 'backup' if you're using a near-stock config?
Yes. Here is the line from our /etc/cron.d/amanda file:
0 11 * * 1-6 backup /usr/sbin/amcheck -m dm
Third, is anyone seeing anything "interesting or unusual" in the logs
from cron? A 'grep -i cron /var/log/*' is worth perusing.
Unfortunately, no. It shows that it's running the daily 'amcheck' but no
errors or anything interesting.
Fourth, you do have a 'mailto' defined in your amanda.conf if you're
using the -m option to amcheck, right?
Yes. We get a report email after a backup run or 'amflush' run completes.
And we *do* get an email warning from the 'amcheck' cron job when an
'amflush' process is running! (Due to forgetting to change the tapes
because the previous day's email reminder didn't go out)
I think the problem is with amcheck itself and might not have anything to
do with cron. I say that because I'm unable to get 'amcheck' to send an
email even when I run the command manually, contrary to my last report. I
don't know if something has really changed since then or if I was doing
something wrong the last time I tested manually running the command.
We use a Seagate DDS4 tape drive which takes 6-tape magazines and has an
autochanger.
When there's a tape problem (no tapes or the wrong tapes) then running
amcheck without an email report produces what appears to be a error
message to stdout, but running it with -m produces no email (as verified
in the Exim log) and no output to stdout, though it takes the right amount
of time (i.e. minutes to check all tapes in the magazine when the wrong
tapes are inserted). Here are some output examples:
----- [NO TAPES] -----
[EMAIL PROTECTED]:~$ sudo -u backup amcheck dm
Amanda Tape Server Host Check
-----------------------------
Holding disk /scratch/amanda: 58649448 kB disk space available, using
58648424 kB
(null)
(expecting tape dm-032 or a new tape)
Server check took 1.090 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 7 hosts checked in 0.371 seconds, 0 problems found
(brought to you by Amanda 2.5.0p2)
----------------------
That "(null)" line seems suspicious to me. I think there used to be some
text along the lines of "ERROR: No usable tape found" in its place...?
----- [WRONG TAPES] -----
[EMAIL PROTECTED]:~$ sudo -u backup amcheck dm
Amanda Tape Server Host Check
-----------------------------
Holding disk /scratch/amanda: 58649448 kB disk space available, using
58648424 kB
slot 1: read label `dm-025', date `20060528'
slot 2: read label `dm-026', date `20060528'
slot 3: read label `dm-027', date `20060530'
slot 4: read label `dm-028', date `20060530'
slot 5: read label `dm-029', date `20060531'
slot 6: read label `dm-030', date `20060531'
(expecting tape dm-032 or a new tape)
Server check took 417.366 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 7 hosts checked in 0.282 seconds, 0 problems found
(brought to you by Amanda 2.5.0p2)
-------------------------
Again, I thought I remember some other text above the "(expecting tape..."
line.
And if I run either of those commands manually with a -m flag when there
is a tape problem then no email is sent and no output is printed to
stdout. Weird.
I hope this helps!
Jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
