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

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.

I can also use successfully:
   rsync -e ssh --recursive -a gdoc rsync-acct at 99.99.99.99:/gdoc
but the problem is that putting the file selection on the client is
(for many reasons)
too painful.  So, I want the selection on the server side using a config file.
But I cannot seem to get it working.

All thoughts and help greatfully appreciated!!

Regards, Bruce

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.

-- 
Matt

On Tue, 2010-03-23 at 17:05 -0700, Bruce Korb wrote:
> On Tue, Mar 23, 2010 at 4:59 PM, Matt McCutchen <matt at
mattmccutchen.net> wrote:
> > On Tue, 2010-03-23 at 16:54 -0700, Bruce Korb wrote:
> >> I now have an strace output file.  It opens rsyncd.conf correctly
> >> and reads in all the data in one gulp.  I've trimmed the
strace to start from
> >> there.  Notice that it tries to open the log file and fails
because it
> >> isn't found.
> >
> > That failure:
> >
> > 29833 open("/home/rsync-abbot/log.txt",
O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 ENOENT (No such file or directory)
> >
> > Is the "rsync-abbot" a typo in your rsyncd.conf or a glitch
in
> > redaction?
> 
> redaction glitch:  s at abbott@acct at g was supposed to fix it....
Then you're missing a "t" in rsyncd.conf.

-- 
Matt