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 Wadsworth email: [EMAIL PROTECTED]
Conceptual Systems and Software http://www.consys.com
===========================================================
