We have two (2) servers on a LAN, backup [A] and tjg1 [B]. We want to PUSH file synchronization from [B] to [A]. We are repeatedly this error: rsync error: timeout in data send/receive (code 30) at io.c(181) Google has not been kind; nor have the archives to this list. Perhaps, I am ignorant of the appropriate search criteria? There are other interesting facts: [1] There are ~74 GB of files to be regularly synchronized. [2] This is on an internal LAN; and we have elected to forgo security processes (e.g., ssh). rsyncd is dynamically started via inetd; and this problem is repeatable with a minimal rsyncd.conf, such as: log file = /var/log/rsyncd.log syslog facility = daemon pid file = /var/run/rsyncd.pid [data] comment = DATA volume archive path = /usr/local/backup/archive/DATA/ [3] Historically, these files resided on a netware server; and another process (NOT rsync) has been successfully backing up these files to [A]. Now, we want to serve these files from [B]. So, the first thing was to rsync these files from [A] to [B]. [4] PULLING from [A] to [B] repeatedly succeeds. [5] PULLING from [B] to [A] repeatedly succeeds. [6] Notice that this problem chronically manifests itself when one side to this process begins EMPTY. [7] The problem repeatedly manifests itself _after_ PUSHING ~2 GB of files. [8] Obviously, in production, there will NOT be an empty side to this; but, until we understand the cause to these failures, our confidence in this process will be less than ideal ;> What do you think? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.samba.org/archive/rsync/attachments/20060515/5d18a141/attachment.bin
We have two (2) servers on a LAN, backup [A] and tjg1 [B]. We want to PUSH file synchronization from [B] to [A]. We are repeatedly this error: rsync error: timeout in data send/receive (code 30) at io.c(181) Google has not been kind; nor have the archives to this list. Perhaps, I am ignorant of the appropriate search criteria? There are other interesting facts: [1] There are ~74 GB of files to be regularly synchronized. [2] This is on an internal LAN; and we have elected to forgo security processes (e.g., ssh). rsyncd is dynamically started via inetd; and this problem is repeatable with a minimal rsyncd.conf, such as: log file = /var/log/rsyncd.log syslog facility = daemon pid file = /var/run/rsyncd.pid [data] comment = DATA volume archive path = /usr/local/backup/archive/DATA/ [3] Historically, these files resided on a netware server; and another process (NOT rsync) has been successfully backing up these files to [A]. Now, we want to serve these files from [B]. So, the first thing was to rsync these files from [A] to [B]. [4] PULLING from [A] to [B] repeatedly succeeds. [5] PULLING from [B] to [A] repeatedly succeeds. [6] Notice that this problem chronically manifests itself when one side to this process begins EMPTY. [7] The problem repeatedly manifests itself _after_ PUSHING ~2 GB of files. [8] Obviously, in production, there will NOT be an empty side to this; but, until we understand the cause to these failures, our confidence in this process will be less than ideal ;> What do you think? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.samba.org/archive/rsync/attachments/20060515/62caa2f4/attachment.bin
Possibly Parallel Threads
- filter/exclude confusion ???
- DO NOT REPLY [Bug 4232] New: rsync error: timeout in data send/receive (code 30) at io.c(165) [sender=3.0.0cvs]
- Receive more information about transfer problems in server log?
- Connection Timeout
- Rsyncing huge file, timeout on rsyncd