Just a thought. Maybe that host's rsync has gotten updated and you
are not yet using the -D flag in an rsync backup. The 2.1.2pl2 diff
file can be applied to 2.1.2.tar.gz and will fix that issue.
I know I had that problem myself.
John
On 7/12/06, Nils Breunese (Lemonbit Internet) [EMAIL PROTECTED] wrote:
I wrote:
I wrote:
I'm getting this error for one of my hosts. I found the nightly run
hadn't succesfully backed up this host but when I ran the incremental
again I got the error again:
Got fatal error during xfer (aborted by signal=PIPE)
Any idea what could be wrong?
I started the incremental another time and this time it worked.
I still get a daily e-mail telling me that some of my hosts
(sometimes only one, not always the same hosts) have had errors:
The following hosts had an error that is probably caused by a
misconfiguration. Please fix these hosts:
- hostname (aborted by signal=PIPE)
What is the cause of signal=PIPE? What configuration options should I
be looking at?
Nils Breunese.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
