Sirs; I have read your web site page current issues and debugging and I am interested in how to debug a rsync issue which ends with the following message: io timeout after 60 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(181) I have compiled rsync on a hpux 11.11 server and I am using rsync-2.6.4. The remote machine is running rsync as a deamon in inetd. The included line is: rsync stream tcp nowait root /usr/local/bin/rsync rsyncd --daemon The remote server ends with the following messages in /var/adm/syslog/syslog.log Jul 21 14:01:10 aux2 rsyncd[16546]: rsync error: timeout in data send/receive (code 30) at io.c(181) Jul 21 14:01:10 aux2 rsyncd[16546]: rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(984) Jul 21 14:01:44 aux2 rsyncd[16546]: rsync: writefd_unbuffered failed to write 69 bytes: phase "unknown" [generator]: Broken pipe (32) Jul 21 14:01:44 aux2 rsyncd[16546]: rsync error: error in rsync protocol data stream (code 12) at io.c(1080) Jul 21 14:01:10 aux2 rsyncd[16546]: rsync error: timeout in data send/receive (code 30) at io.c(181) The command I issued to start rsync on the local machine is: /usr/local/bin/rsync -avvWP --inplace --delete --exclude-from /exclude.files --timeout=60 --bwlimit=500 / aux2_sync::sftp This works but not reliably. It stops. Even though you include examples in the web page on how to debug this issue it is not clear to me what I need to do. Sincerely Alvin Dobrowski SysAdmin St. Edward's University
On Thu, Jul 21, 2005 at 02:23:14PM -0500, Alvin Dobrowski wrote:> io timeout after 60 seconds -- exitingThis is not a hang, this is an abort due to inactivity.> I have compiled rsync on a hpux 11.11 server and I am using rsync-2.6.4. > The remote machine is running rsync as a deamon in inetd.Is the server also running 2.6.4 or 2.6.5? If it's running something older, any pause in the transferred data (such as the generator taking over 60 seconds to find a changed file or the receiver taking over 60 seconds to receive the checksum data from the generator) will cause the connection to fail. If it's running 2.6.4, the latter problem can still cause a timeout (since keep-alive code was only added for that scenario in 2.6.5). So, I'd recommend upgrading both ends of the connection with 2.6.5 and trying again. ..wayne..