From the write man page:

    [EAGAIN]       The file was marked for non-blocking I/O, and no data could
                   be written immediately.


But sendbackup or gzip write the index to a blocking pipe.
Maybe it's the firewall that returns that error.

Jean-Louis

stan wrote:

On Tue, Aug 18, 2009 at 08:06:46AM -0400, Jean-Louis Martineau wrote:

stan wrote:

Any thoughts as to why I have twice as many debug files as I expect?

When a dump fail, amanda try it a second time.

Got it.

Now, hee are what I think are the pertinant lines from a dump this morning
W/O compression:

250596583.437206: sendbackup:  91:  normal(|):   DUMP: Volume 1 started at: Tue
 Aug 18 07:56:23 2009
1250596583.481419: sendbackup: critical (fatal): index tee cannot write [Resourc
 e temporarily unavailable]
1250596583.484261: sendbackup: 116: strange(?): sendbackup: index tee cannot 
wri te [Resource temporarily unavailable]
1250596583.485035: sendbackup:  91:  normal(|):   DUMP: Broken pipe
1250596583.485826: sendbackup:  91:  normal(|):   DUMP: The ENTIRE dump is 
aborted.
1250596583.500258: sendbackup: critical (fatal): error [dump (10626) /sbin/dump 
returned 3]

That's from a sendbackup debug file.

Do you need me to send the entire debug files?

What can I try to help further narow down the problem?