rsync: connection unexpectedly closed (0 bytes received so far)

[Bruce Korb]

Hi Matt,

On Tue, Mar 23, 2010 at 3:25 PM, Matt McCutchen <matt at mattmccutchen.net> wrote:
> On Tue, 2010-03-23 at 15:05 -0700, Bruce Korb wrote:
>> Please forgive my digging up a two year old thread, but I've got the
>> same problem, but the pointers there give no help.  This is using
>> versions 3.0.6 (server) and 3.0.7 (client).
>>
>> Unfortunately, I have to type the client stuff in by hand.  ("Secured"
>> laptop with highlighting & copying disabled.)  Anyway:
>>
>> $ rsync -vvvvvv -a -e ssh --recursive gdoc rsync-acct at 99.99.99.99::doc
>> file_struct_len=16, extra_len=4
>> opening connection ....
>> note: iconv_open("UTF-8", "UTF-8") succeeded.
>> sending daemon args: ..
>> rsync: connection unexpectedly closed (0 byes received so far) [sender]
>> [sender] _exit_cleanup(code=12, file=.../io.c, line=601): about to call exit(12)
>>
>> ==== Yet this works correctly:
>>
>> rsync -vvvvv -e ssh rsync-acct at 99.99.99.99::
>> <<blah, blah, followed by the module list>>
>>
>> =========== The rsync daemon log file had no entries from
>> this interchange, despite being started with a bunch of "v"s.
>
> Are you certain that you transcribed both commands accurately?  As you
> have written them here, both commands are using a single-use daemon
> invoked over ssh (a daemon source or destination with "-e ssh"); is that
> what you intend?  The error from the first command is consistent with
> not having set up the rsyncd.conf file in the remote ssh user's home
> directory.

Without the "-e ssh" I was getting no response at all.  tcpdump wasn't showing
any port 873 packets, but port 22 was getting through the vyatta virtual switch.
So, "-e ssh", though I'd actually like to get the daemon working
correctly through
its 873 port -- as long as it will use a secure encrypted tunnel.  First, I need
the data moved around though.

I did have it in the user home directory:  /home/rsync-acct/rsyncd.conf
and it points to PID and log files in that directory, too.  So, can you guess
where I went south?  :)  thanks so much!  Regards, Bruce

$ ls -l
total 24
drwxrwxrwx 2 rsync-acct rsync-acct 4096 2010-03-23 15:47 acct-project
drwxr-xr-x 2 rsync-acct rsync-acct 4096 2010-03-23 14:07 bin
drwxrwxrwx 3 rsync-acct rsync-acct 4096 2010-03-23 12:03 data
-rw-r--r-- 1 root         root         2451 2010-03-23 15:30 log.txt
-rw-r--r-- 1 rsync-acct rsync-acct 1902 2010-03-23 13:57 rsyncd.conf
-rw-rw-rw- 1 rsync-acct rsync-acct    0 2010-03-23 13:58 rsyncd.lock
drwxr-xr-x 3 rsync-acct rsync-acct 4096 2010-03-18 10:57 var

$ cat rsyncd.conf
use chroot = yes
max connections = 4
log file   = /home/rsync-acct/log.txt
lock file  = /home/rsync-acct/rsyncd.lock
pid file   = /home/rsync-acct/var/run/rsyncd.pid
fake super = yes
transfer logging = yes

[doc]
        path       = /home/rsync-acct/acct-project
        comment    = doc project
        read only  = yes
        use chroot = yes
        filter     = /gdoc/***