Why no reports?
Been setting up Amanda, and she seems to be happy. Ran nightly (as spawned by cron) for the past two nights. For some reason, however, I didn't get an email report from last night's run. What could cause this? I looked at lots of different things, and it *looks* line it ran fine last night. This is the first time its failed to send a report, in the past I would always get 'em. Here's the line from amanda.conf: mailto "[EMAIL PROTECTED] [EMAIL PROTECTED]" I've been fiddling with procmail to handle the report that is sent to the operator account, but it appears that it didn't get one either. Idea? === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
RE: Why no reports?
I would suggest running amstatus to make sure it really did finish. I usually don't get a report when it's waiting for user input. -Original Message- From: Eric Wadsworth [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 30, 2000 4:43 PM To: [EMAIL PROTECTED] Subject: Why no reports? Been setting up Amanda, and she seems to be happy. Ran nightly (as spawned by cron) for the past two nights. For some reason, however, I didn't get an email report from last night's run. What could cause this? I looked at lots of different things, and it *looks* line it ran fine last night. This is the first time its failed to send a report, in the past I would always get 'em. Here's the line from amanda.conf: mailto "[EMAIL PROTECTED] [EMAIL PROTECTED]" I've been fiddling with procmail to handle the report that is sent to the operator account, but it appears that it didn't get one either. Idea? === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: Why no reports?
Yes, this was actually the first thing I did: % amstatus DailySet1 no /usr/local/etc/amanda/DailySet1/log/amdump file at /usr/local/sbin/amstatus line 87. I assume that this means it finished? --- Eric "Bort, Paul" wrote: > > I would suggest running amstatus to make sure it really did > finish. I usually don't get a report when it's waiting for user input. > > -Original Message- > From: Eric Wadsworth [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 30, 2000 4:43 PM > To: [EMAIL PROTECTED] > Subject: Why no reports? > > Been setting up Amanda, and she seems to be happy. Ran nightly (as spawned > by > cron) for the past two nights. For some reason, however, I didn't get an > email > report from last night's run. What could cause this? I looked at lots of > different things, and it *looks* line it ran fine last night. This is the > first > time its failed to send a report, in the past I would always get 'em. > > Here's the line from amanda.conf: > > mailto "[EMAIL PROTECTED] [EMAIL PROTECTED]" > > I've been fiddling with procmail to handle the report that is sent to the > operator account, but it appears that it didn't get one either. === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
RE: Why no reports?
As far as I know that means it's finished, since amstatus looks for a 'work-in-progress' log instead of a completed log. When I had a problem like this, it turned out that sometimes my sendmail wasn't getting DNS, so the messages sat in a queue, and would eventually have been bounced. Does procmail have a similar queue? -Original Message- From: Eric Wadsworth [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 30, 2000 5:11 PM To: Bort, Paul; [EMAIL PROTECTED] Subject: Re: Why no reports? Yes, this was actually the first thing I did: % amstatus DailySet1 no /usr/local/etc/amanda/DailySet1/log/amdump file at /usr/local/sbin/amstatus line 87. I assume that this means it finished? --- Eric "Bort, Paul" wrote: > > I would suggest running amstatus to make sure it really did > finish. I usually don't get a report when it's waiting for user input. > > -Original Message- > From: Eric Wadsworth [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 30, 2000 4:43 PM > To: [EMAIL PROTECTED] > Subject: Why no reports? > > Been setting up Amanda, and she seems to be happy. Ran nightly (as spawned > by > cron) for the past two nights. For some reason, however, I didn't get an > email > report from last night's run. What could cause this? I looked at lots of > different things, and it *looks* line it ran fine last night. This is the > first > time its failed to send a report, in the past I would always get 'em. > > Here's the line from amanda.conf: > > mailto "[EMAIL PROTECTED] [EMAIL PROTECTED]" > > I've been fiddling with procmail to handle the report that is sent to the > operator account, but it appears that it didn't get one either. === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
RE: Why no reports?
yeah, the amdump log is there when the dump is running. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Wadsworth Sent: Thursday, November 30, 2000 2:11 PM To: Bort, Paul; [EMAIL PROTECTED] Subject: Re: Why no reports? Yes, this was actually the first thing I did: % amstatus DailySet1 no /usr/local/etc/amanda/DailySet1/log/amdump file at /usr/local/sbin/amstatus line 87. I assume that this means it finished? --- Eric "Bort, Paul" wrote: > > I would suggest running amstatus to make sure it really did > finish. I usually don't get a report when it's waiting for user input. > > -Original Message- > From: Eric Wadsworth [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 30, 2000 4:43 PM > To: [EMAIL PROTECTED] > Subject: Why no reports? > > Been setting up Amanda, and she seems to be happy. Ran nightly (as spawned > by > cron) for the past two nights. For some reason, however, I didn't get an > email > report from last night's run. What could cause this? I looked at lots of > different things, and it *looks* line it ran fine last night. This is the > first > time its failed to send a report, in the past I would always get 'em. > > Here's the line from amanda.conf: > > mailto "[EMAIL PROTECTED] [EMAIL PROTECTED]" > > I've been fiddling with procmail to handle the report that is sent to the > operator account, but it appears that it didn't get one either. === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: Why no reports?
>... For some reason, however, I didn't get an email >report from last night's run. What could cause this? ... I don't know, but you can regenerate the E-mail by running amreport (see the man page). If that works, then it was probably a transient mail problem. If it doesn't, hopefully it will either say something or give you at least a debugging tool to find out what's wrong with your mailer. >Eric Wadsworth John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Why no reports?
I followed John Jackson's advice, and attempted to generate the report manually, with the command, executed from /usr/local/etc/amanda/DailySet1/ amreport DailySet1 log/log.20001130.0 What resulted were these errors: /var: write failed, file system is full postdrop: fatal: uid=2: queue file write error send-mail: fatal: operator(2): error writing queue file: Broken pipe While I ran it, though, I watched my /var partition, and it didn't seem to change. I could have missed it though, especially if it tried to write a big file all at once. Does anyone know which subdirectory under /var amreport might be using? I'll make a symbolic link of this spot over to another disk that has 60 gigs of free space... that's what I did when amanda filled up my /tmp partition. === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: Why no reports?
>What resulted were these errors: > >/var: write failed, file system is full >postdrop: fatal: uid=2: queue file write error >send-mail: fatal: operator(2): error writing queue file: Broken pipe I'm pretty sure those are all generated by your mailer, not Amanda. How about running amreport with the -f option to send the report to a file instead of via E-mail. Make sure it is not gigantic for some reason. If it is, that might be an Amanda problem. If it isn't, then it's a problem with your mail system. >Eric Wadsworth John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Why no reports?
Yes, this was the problem. This report was 9 megs in size... The backup includes lots of samba shares, and for each one it insists on including a listing of every file on the share. I spent 2 days last week trying to get it to not do this, but I was unsuccessfull. The email setup simply couldn't handle a file this big. *sigh* I'm using samba version 2.0.6 on a FreeBSD machine. Using amanda 2.4.1p1 right now, and I dropped the samba 2 patch into the 'files' directory of the FreeBSD ports skeleton, but I don't know how to tell if the patch actually made it in, as the patch modified the configure command itself. Probably the best thing I could do to fix this would be to uninstall 2.4.1p1 and put in 2.4.2 but I'm waiting until it appears in the FreeBSD ports first, as I have had zero success in getting amanda to install when doing it manually (tried 2.4.1p1 and 2.4.2b2 manually with no success). So for now, I guess I should just live with it. Maybe after it does a level 0 dump of these samba shares, it will skip the file listings in the reports? Then they might make it through the email system. --- Eric "John R. Jackson" wrote: > > >What resulted were these errors: > > > >/var: write failed, file system is full > >postdrop: fatal: uid=2: queue file write error > >send-mail: fatal: operator(2): error writing queue file: Broken pipe > > I'm pretty sure those are all generated by your mailer, not Amanda. > > How about running amreport with the -f option to send the report to a file > instead of via E-mail. Make sure it is not gigantic for some reason. > If it is, that might be an Amanda problem. If it isn't, then it's a > problem with your mail system. > > >Eric Wadsworth > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: Why no reports?
Eric Wadsworth <[EMAIL PROTECTED]> wrote: >I'm using samba version 2.0.6 on a FreeBSD machine. Using amanda 2.4.1p1 right >now, and I dropped the samba 2 patch into the 'files' directory of the FreeBSD >ports skeleton, but I don't know how to tell if the patch actually made it in, >as the patch modified the configure command itself. I've added these three lines to /usr/ports/misc/amanda24/Makefile (after the DISTNAME= line): PATCH_SITES=http://www.amanda.org/patches/2.4.1p1/ PATCHFILES= samba2-2418.diff PATCH_DIST_STRIP= -p1 and added a line to /usr/ports/misc/amanda24/distinfo too (in the old ports layout this was /usr/ports/misc/amanda24/files/md5 IIRC): MD5 (samba2-2418.diff) = 6a66c8750a4ebeed1de7f43613035c7f HTH Lipo -- Roland E. Lipovits Vienna, Austria
Re: Why no reports? (fwd)
This was it! This installs the patch! Thanks so much. Tomorrow we'll see if this patch solved the huge report problem. My latest report was 24 megs in size! The emailer doesn't handle it very well. :) Eric > Eric Wadsworth <[EMAIL PROTECTED]> wrote: > >I'm using samba version 2.0.6 on a FreeBSD machine. Using amanda 2.4.1p1 right > >now, and I dropped the samba 2 patch into the 'files' directory of the FreeBSD > >ports skeleton, but I don't know how to tell if the patch actually made it in, > >as the patch modified the configure command itself. > > I've added these three lines to /usr/ports/misc/amanda24/Makefile > (after the DISTNAME= line): > PATCH_SITES=http://www.amanda.org/patches/2.4.1p1/ > PATCHFILES= samba2-2418.diff > PATCH_DIST_STRIP= -p1 > > and added a line to /usr/ports/misc/amanda24/distinfo too > (in the old ports layout this was /usr/ports/misc/amanda24/files/md5 IIRC): > MD5 (samba2-2418.diff) = 6a66c8750a4ebeed1de7f43613035c7f > > HTH > Lipo > > -- > Roland E. Lipovits > Vienna, Austria === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
