rsync - Dec 2001 - problem uploading to an rsync server

For some reason I'm having a problem uploading to an rsync server:

[root@csa i386]# rsync -azvv --progress --stats /home/www/www.blah.com/* 
blah@localhost::test/
Password: 
building file list ... done
ERROR: module is read only
unexpected EOF in read_timeout

It claims my module is read only, but it is not:

[test]
        uid = root
        gid = root
        path = /home/www/www.blah.com-test
        comment = this is a test
        auth users = blah
        secrets file = /etc/rsyncd.secrets

It's set to localhost because this is going over an stunnel.  Yes, I did 
try it without the stunnel and same results.  How can I debug this.  This 
is 2.4.6 on both sides because 2.5.0 just fails completely for uploading 
and downloading.

Thanks
-jeremy

-- 
.o--0O0--o.

These are two redhat machines, running 6.2.

server side error in systlog:

Dec  5 12:11:25 geo rsyncd[15335]: rsync to test/ from 
blah@blah.net (192.168.0.50)
Dec  5 12:11:25 geo rsyncd[15335]: transfer interrupted (code 1) at 
main.c(401)

This is the error not going over stunnel.

Thanks
-jeremy


On Wed, 5 Dec 2001, Jeremy Hansen wrote:
> 
> For some reason I'm having a problem uploading to an rsync server:
> 
> [root@csa i386]# rsync -azvv --progress --stats /home/www/www.blah.com/* 
> blah@localhost::test/
> Password: 
> building file list ... done
> ERROR: module is read only
> unexpected EOF in read_timeout
> 
> It claims my module is read only, but it is not:
> 
> [test]
>         uid = root
>         gid = root
>         path = /home/www/www.blah.com-test
>         comment = this is a test
>         auth users = blah
>         secrets file = /etc/rsyncd.secrets
> 
> It's set to localhost because this is going over an stunnel.  Yes, I
did
> try it without the stunnel and same results.  How can I debug this.  This 
> is 2.4.6 on both sides because 2.5.0 just fails completely for uploading 
> and downloading.
> 
> Thanks
> -jeremy
> 
> 
-- 
.o--0O0--o.

On Wed, Dec 05, 2001 at 03:05:19PM -0500, Jeremy Hansen
wrote:
> It claims my module is read only, but it is not:
> 
> [test]
>         uid = root
>         gid = root
>         path = /home/www/www.blah.com-test
>         comment = this is a test
>         auth users = blah
>         secrets file = /etc/rsyncd.secrets
from the man page for rsyncd.conf:
"
       read only
              The  "read  only" option determines whether clients
              will be able to upload files or not. If "read only"
              is  true  then  any attempted uploads will fail. If
              "read only" is false then uploads will be  possible
              if  file  permissions on the server allow them. The
              default is for all modules to be read only.
"

Note that read only is the default. You'll need to explicitly set read
only to false if you want the module to be writeable.

-drew

-- 
M. Drew Streib <dtype@dtype.org>, Free Standards Group (freestandards.org)
co-founder, SourceForge.net | core team, freedb | sysadmin, Linux Intl.
creator, keyanalyze report | maintnr, *.us.pgp.net | other, see freedom/law
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
Url :
http://lists.samba.org/archive/rsync/attachments/20011205/625d2184/attachment.bin

On  5 Dec 2001, Jeremy Hansen <jeremy@xxedgexx.com> wrote:
> It's set to localhost because this is going over an stunnel.  Yes, I
did
> try it without the stunnel and same results.  How can I debug this.  This 
> is 2.4.6 on both sides because 2.5.0 just fails completely for uploading 
> and downloading.
Please try 2.5.1pre3 if have time.  It should work properly in daemon
mode and also fix some other bugs that may affect you later.

--
Martin