> I read in the archives that this error is usually caused by bad
>tapes, or write protect etc. I know that the tape is in good condition,
>because I tar'd to it before labeling.
This particular problem would not be caused by a bad tape.
> On the client, the sendbackup.debug file says after the runtar
>command:
>
> sendbackup [pid]: index tee cannot write [Broken pipe]
> sendbackup [pid]: error [/usr/local/bin/tar got signal 13]
>...
> The amdump.1 file has the following errors:
>
>driver: result time 548.663 from dumper0: FAILED 00-00001 [data read:
> Connection reset by peer]
For some reason, the network connection between client and server was
reset. The server side saw the reset and reported that in amdump.1.
The client side saw that as a SIGPIPE (signal 13) and died because there
didn't appear to be anyone to talk to.
Any firewalls or that kind of thing between these two machines?
> cjw
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
