Rsync Log Error

[John Van Essen]

Apparently this initial email from 2 days ago got trapped by a probable
20K limit on email size, and was just now approved by the admin.  In
the meantime a truncated version was sent that omitted some key info...

I have unwrapped the log lines for readability.

We've been on a wild goose chase, fellas...  :-/

On Wed, 21 Apr 2004, Kevin Kallsen <kallsen at e101.com> wrote:
>
> I have the latest rsync running on mandrake official 10.  At 2:30 I run
> rsync --daemon from cron to run an offsite backup for all my customers.  At
> 8:00 I run killall rsync.
> 
> 
> However my log files show the following:
> 
> 
> 2004/04/20 02:00:00 [2702] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/20 02:00:59 [2707] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/20 02:00:59 [2707] rsync: open inbound socket on port 873 failed: Address already in use
> 2004/04/20 02:00:59 [2707] rsync error: error in socket IO (code 10) at socket.c(395)
> 2004/04/20 02:02:01 [2719] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/20 02:02:01 [2719] rsync: open inbound socket on port 873 failed: Address already in use
> 2004/04/20 02:02:01 [2719] rsync error: error in socket IO (code 10) at socket.c(395)
> 2004/04/20 02:03:00 [2722] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/20 02:03:00 [2722] rsync: open inbound socket on port 873 failed: Address already in use
> 2004/04/20 02:03:00 [2722] rsync error: error in socket IO (code 10) at socket.c(395)
[ ... snip ... ]
> 2004/04/20 02:58:00 [2889] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/20 02:58:00 [2889] rsync: open inbound socket on port 873 failed: Address already in use
> 2004/04/20 02:58:00 [2889] rsync error: error in socket IO (code 10) at socket.c(395)
> 2004/04/20 02:59:00 [2892] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/20 02:59:00 [2892] rsync: open inbound socket on port 873 failed: Address already in use
> 2004/04/20 02:59:00 [2892] rsync error: error in socket IO (code 10) at socket.c(395)
> 2004/04/20 04:30:23 [14016] auth failed on module trinity from 227.15.252.64.snet.net (64.252.15.227)
> 2004/04/20 08:00:01 [2702] rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(249)
> 2004/04/21 02:00:00 [16340] rsyncd version 2.6.0 starting, listening on port 873
> 2004/04/21 04:30:00 [5206] rsync to trinity/ from 227.15.252.64.snet.net (64.252.15.227)
> 2004/04/21 04:30:20 [5207] wrote 108 bytes  read 217084 bytes  total size 5129738286
> 2004/04/21 04:30:20 [5206] rsync: writefd_unbuffered failed to write 78 bytes: phase "unknown": Broken pipe
> 2004/04/21 04:30:20 [5206] rsync error: error in rsync protocol data stream (code 12) at io.c(666)
> 2004/04/21 08:00:00 [16340] rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(249)


This clearly shows that the multiple rsync restarts were only on the
first day (4/20) and not on the 2nd day (4/21) so Kevin fixed the
crontab line already (as was indicated by the correct entry that
he posted later).  So that is not the problem, butthat was what
we were all scratching our heads about...

So ignoring all the 04/20 errors, brings us to the 04/21 errors.

The ones at 04:30 looks like a minor shutdown problem that didn't
affect the transfer.

The one at 08:00 is from the kill.
-- 
        John Van Essen  Univ of MN Alumnus  <vanes002 at umn.edu>