On Mon, Sep 11, 2006 at 01:31:00PM +0200, rsync-mail-gateway@nasbackup.com wrote:> rsync: read error: Connection reset by peer (104)This means the socket closed. Does rsync even get started on the remote system? That would be the first thing to investigate. If it is getting run, does the remote process crash or die? If you are connecting with a daemon process, you can look at the logs to figure that out. If you're using the CVS version of rsync, you can use the new --log-file option on the remote rsync to ask it to log what is going on (it requires using the --rsync-path option, as mentioned in the latest man page). Or, you can enable system-call tracing, as detailed on the Issues and Debugging webpage of the rsync website. ..wayne..
hello, 1) ssh is the default protocol of rsync since 2.6.0, so if you are using a new version you should not have to worry about it. 2) check that you used the command as following: rsync <flags> -e ssh <user>@<server>:~<rsync_user>/ that should do the trick (worked for me) -------------------- m2f -------------------- Sent using Mail2Forum (http://www.mail2forum.com). Read this topic online here: http://forums.nasbackup.com/viewtopic.php?p=3837#3837 -------------------- m2f -------------------- -------------- next part -------------- HTML attachment scrubbed and removed
i got the reply through mailing list and saw that not all came through... so again: 1) ssh is the default protocol of rsync since 2.6.0, so if you are using a new version you should not have to worry about it. 2) check that you used the command as following: rsync flags -e ssh local_dir user@server:~rsync_user/ that should do the trick (worked for me) -------------------- m2f -------------------- Sent using Mail2Forum (http://www.mail2forum.com). Read this topic online here: http://forums.nasbackup.com/viewtopic.php?p=3838#3838 -------------------- m2f -------------------- -------------- next part -------------- HTML attachment scrubbed and removed