On Sun, Jun 27, 2004 at 11:58:41PM -0400, Paul M Foster wrote:
> On Mon, Jun 14, 2004 at 10:51:39PM -0400, Ian Blenke wrote:
>
> > Paul M Foster wrote:
> >
> > >I'm using rsync to back up my desktop to another machine daily (cron
> > >job). I'm consistently getting the error below, though in different
> > >places. I've googled for this, but seen no definite source for the
> > >problem, nor solution. Anyone seen this before or have a good idea why
> > >it happens?
> > >
> > >Paul
> > >
> > >----- Forwarded message from Anacron <root@hobbes.mars.lan> -----
> > >
> > >From: Anacron <root@hobbes.mars.lan>
> > >Date: Sun, 13 Jun 2004 05:20:35 -0400 (EDT)
> > >To: root@hobbes.mars.lan
> > >Subject: Anacron job 'cron.daily'
> > >Message-Id: <20040613092035.8574F1256BC@hobbes.mars.lan>
> > >
> > >/etc/cron.daily/backup:
> > >building file list ... done
> > >etc/
> > >etc/adjtime
> > >etc/printcap
> > >usr/lib/freedos/pss/
> > >usr/lib/freedos/pss/pmcc/
> > >usr/lib/freedos/pss/qmsi/
> > >usr/lib/freedos/q8dos/data/
> > >var/backups/
> > >var/cache/apt/
> > >var/cache/debconf/
> > >var/cache/debconf/templates.dat-old
> > >var/cache/fonts/ls-R
> > >var/cache/locate/
> > >var/cache/locate/locatedb
> > >rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown":
> > Broken pipe
> > >rsync error: error in rsync protocol data stream (code 12) at io.c(515)
> > >rsync: writefd_unbuffered failed to write 70 bytes: phase "unknown":
> > Broken pipe
> > >rsync error: error in rsync protocol data stream (code 12) at io.c(515)
> > >run-parts: /etc/cron.daily/backup exited with return code 12
> > >/etc/cron.daily/timesync:
> > >13 Jun 05:20:33 ntpdate[26029]: step time server 192.168.10.1 offset
> > 3.858411 sec
> > >
> > >
> > This commonly appears when you are using two different versions of rsync
> > (the remote end is different from the local version). This has usually
> > happened to me only between minor number differences in varying versions
> > of rsync.
> >
> > What does "rsync --version" say on both sides?
> >
>
> I've now revved the repository's version to be the same as the machine
> to be backed up (2.6.2 protocol version 28). The results are the same.
> I'm mystified. Any other ideas?
>
It would appear that adding the --temp-dir=/tmp directive and ensuring
you have enough space in the /tmp directory resolves this specific
problem. I do, however, have some errors from inability to open or close
files. Puzzling.
Paul
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:02:54 EDT