rsync - Dec 2006 - _exit_cleanup(code=12, file=token.c, line=419): about to call exit(12)

Hy all,

I'm a new rsync user and my english may be poor.
I try to sync two folders between two machines using ssh and
2.6.9 rsync version on each.

My purpose is to sync only files called "*.lic" in each
subfolders.

On the source machine I want to sync :

/home/dps3/public/Lic/Lic
/home/dps3/public/Lic/Lic2
/home/dps3/public/Lic/Lic3

to 
/home/dps3/public/Lic/Lic9

On each subfolders there about 50 000 files and 25 000
.licence files of 512B size (really small files)

On the destination machine :
/home/Lic/ is the destination folder.
I want in it to be created subfolders such as :
/home/Lic/Lic
home/Lic/Lic2
..
..
..
/home/Lic/Lic9 

with in each subfolders only .licence files from the source
machine.

I launch it :

rsync -avvvztog -e ssh /home/dps3/public/Lic*
rsyncuser@192.168.100.5:/home/Lic/ --include='*/'
--include='*.lic' --exclude='*'

And every time i get an error such as :
 
recv_files(Lic/file020500101.lic)
recv_generator(Lic/file7250600401.lic,4419)
recv_files(Lic/file020599999.lic)
rsync: mkstemp "/home/Lic/Lic/.file020599999.lic.Z9L0Pw"
failed: Permission denied (13)
Lic/file7250600401.lic is uptodate
inflate returned -3 (271 bytes)
recv_generator(Lic/file7260600401.lic,4420)
rsync error: error in rsync protocol data stream (code 12) at
token.c(419) [receiver=2.6.9]
_exit_cleanup(code=12, file=token.c, line=419): about to call
exit(12)
Lic/file7260600401.lic is uptodate
rsync: connection unexpectedly closed (6502930 bytes received
so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at
io.c(453) [generator=2.6.9]
_exit_cleanup(code=12, file=io.c, line=453): about to call
exit(12)
rsync: connection unexpectedly closed (31588 bytes received so
far) [sender]
rsync error: error in rsync protocol data stream (code 12) at
io.c(462) [sender=2.6.9]
_exit_cleanup(code=12, file=io.c, line=462): about to call
exit(12)

This is the last lines of verbose.

I don't understand why i get "Permission Denied" error
destination folders is owned by nobody:nobody

Have you got an idea on how to solve my problem? 

Thanks a lot
Regards,
Jc.

Acc?dez au courrier ?lectronique de La Poste 
sur www.laposte.net ou sur 3615 LAPOSTENET (0,34? TTC /mn) 
1 Giga de stockage gratuit ? Antispam et antivirus int?gr?s

On Fri 15 Dec 2006, jc.duss59@laposte.net wrote:
> 
> I launch it :
> 
> rsync -avvvztog -e ssh /home/dps3/public/Lic*
> rsyncuser@192.168.100.5:/home/Lic/ --include='*/'
> --include='*.lic' --exclude='*'
With such small files, --whole-file may be useful, as looking for diffs
is pretty pointless with such small files. Also --inplace could be worth
trying, it can save a lot of renaming etc.
> And every time i get an error such as :
> 
> recv_files(Lic/file020500101.lic)
> recv_generator(Lic/file7250600401.lic,4419)
> recv_files(Lic/file020599999.lic)
> rsync: mkstemp "/home/Lic/Lic/.file020599999.lic.Z9L0Pw"
> failed: Permission denied (13)
> I don't understand why i get "Permission Denied" error
> destination folders is owned by nobody:nobody
You're running rsync as rsyncuser, not as nobody...


Paul Slootman

On 12/15/06, jc.duss59@laposte.net <jc.duss59@laposte.net>
wrote:
> rsync -avvvztog -e ssh /home/dps3/public/Lic*
> rsyncuser@192.168.100.5:/home/Lic/ --include='*/'
> --include='*.lic' --exclude='*'
> [...]
> inflate returned -3 (271 bytes)
> recv_generator(Lic/file7260600401.lic,4420)
> rsync error: error in rsync protocol data stream (code 12) at
> token.c(419) [receiver=2.6.9]
> [...]
> Have you got an idea on how to solve my problem?
The real problem is that, for some reason, the receiver fails to
decompress a compressed file chunk coming from the sender.  If you
have a certain file that triggers this error every time, there may be
a bug in rsync, and you could send the file to Wayne off-list for
further investigation.  You can work around the problem by not using
rsync-level compression (omit the -z option); if you like, you can use
ssh-level compression by passing -e "ssh -C".

Matt

On Fri 15 Dec 2006, Matt McCutchen wrote:
> The real problem is that, for some reason, the receiver fails to
> decompress a compressed file chunk coming from the sender.  If you
Are you sure? The receiver first gets an EPERM when trying to create the
tmp file, I could understand it then not bothering to decompress a
compressed file chunk... I could not, however, understand why the
failure to uncompress would result in an EPERM errno.


Paul Slootman

On 12/16/06, Paul Slootman <paul@debian.org>
wrote:
> On Fri 15 Dec 2006, Matt McCutchen wrote:
> > The real problem is that, for some reason, the receiver fails to
> > decompress a compressed file chunk coming from the sender.  If you
>
> Are you sure? The receiver first gets an EPERM when trying to create the
> tmp file, I could understand it then not bothering to decompress a
> compressed file chunk... I could not, however, understand why the
> failure to uncompress would result in an EPERM errno.
The receiver decompresses the incoming file data in exactly the same
way whether or not it succeeds in creating the temporary file; the
only difference is whether the receiver writes the data to the
temporary file or discards it.  So I think the "Permission denied"
error is unrelated to the decompression error.  Furthermore, the
message that rsync is exiting refers to line 419 of token.c, which is
reached when there is a decompression error.  Thus, I reason that the
decompression error is the real problem.

Note: "Permission denied" is EACCES, not EPERM.

Matt