arguellodw
2008-May-08 15:59 UTC
rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
We are rsync'ing from an xp box running cygwin to a redhat box, using a Perl script that fist calls for an ssh tunnel, then calls rsync through local host. ssh -P -f -L 8740:remote.host.ip:873 user@firewall.ip -p 22 sleep 25 rsync -vrtz -v --timeout=180 --exclude-from=exludefiles rsync://localhost:8740/<remote path> <target path> =========================================================This has worked for quite a while on a daily cron job. We can still open the ssh tunnel without any problem. After the tunnel is open and we run rsync, we get the following error messages: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153) rsync: connection unexpectedly closed (598306 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) rsync: connection unexpectedly closed (598306 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) =========================================================Then it returns to the command prompt. The number of 'bytes read so far' is not constant on the different times we've tried rsync'ing, but this number does stay around 590kB. Does anybody have any ideas? -- View this message in context: http://www.nabble.com/rsync-error%3A-timeout-in-data-send-receive-%28code-30%29-at--home-lapo-packaging-tmp-rsync-2.6.3-io.c%28153%29-tp17127523p17127523.html Sent from the Samba - rsync mailing list archive at Nabble.com.
arguellodw
2008-May-09 16:29 UTC
rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
As an update to this problem, it seems that rsync has no problem updating/transferring the directory tree (every day, new data is added in a date directory structure at the remote site). So when I rsync, I get the new folders, but the error message always pops up before data files are transferred over. -- View this message in context: http://www.nabble.com/rsync-error%3A-timeout-in-data-send-receive-%28code-30%29-at--home-lapo-packaging-tmp-rsync-2.6.3-io.c%28153%29-tp17127523p17151640.html Sent from the Samba - rsync mailing list archive at Nabble.com.
Wayne Davison
2008-May-10 15:22 UTC
rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
On Thu, May 08, 2008 at 08:59:41AM -0700, arguellodw wrote:> rsync error: timeout in data send/receive (code 30) at > /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)You are reaching your idle-time timeout. Either make it larger (e.g. --timeout=360) or upgrade to a newer rsync version that has support for keep-alive messages in the protocol and see if that helps. ..wayne..
Apparently Analagous Threads
- rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)
- Rsync / Cygwin : Cannot Allocate Memory
- Post-Win2k3 Upgrade rsync+ssh Permissions Problem
- scp bug? or is it intended?
- openssh-unix-dev digest, Vol 1 #505 - 15 msgs