Il 02/07/2014 17:23, Les Mikesell ha scritto:
> That is correct, but it doesn't block on other platforms unless the 
> remote stops sending.. But first the server-side ssh has to launch 
> rsync on the remote side, so you could see if you are getting at least 
> that far. It is also possible that it is working but just extremely 
> slow at handling compression, and thus hitting the timeout. 
Got your point and tested.
The rsync process at the client side does nothing (no CPU nor mem 
activity). It is idle (blocked).

The output of the BackupPC_dump program is (only significant lines):

Running: /usr/bin/ssh -q -x -l root caronte /usr/bin/rsync -v --server --sender 
--numeric-ids --perms --owner --group -D --links --hard-links --times 
--block-size=2048 --recursive . /
Xfer PIDs are now 7567
xferPids 7567
Got remote protocol 1869506377
Fatal error (bad version): Ignoring unknown parameter "conn log"

I guess it is stuck because the two sides cannot agree about a protocol 
version or pheraphs the perl library cannot handle correctly this case. 
I don't know...





------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/