Bug 4232 - rsync error: timeout in data send/receive (code 30) at io.c(165) [sender=3.0.0cvs]
rsync error: timeout in data send/receive (code 30) at io.c(165) [sender=3.0....
Status: RESOLVED FIXED
Product: rsync
Classification: Unclassified
Component: core
3.1.0
x86 Linux
: P3 minor
: ---
Assigned To: Wayne Davison
Rsync QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-15 15:00 UTC by william mcinnis
Modified: 2010-08-21 13:12 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description william mcinnis 2006-11-15 15:00:07 UTC
ok this applys to all versions of rsync

just at certin times i will get 

rsync error: timeout in data send/receive (code 30) at io.c(165) 
[sender=2.6.9]
and then thats it 

this is a local network i ran netstat when it does this and they say

client:
tcp        1      0 192.168.10.25:43186         fpserv.dulug.duke.edu:http  
CLOSE_WAIT
tcp        1      0 192.168.10.25:55703         fpserv.dulug.duke.edu:http  
CLOSE_WAIT
tcp        0 188104 192.168.0.99:53651          clients:rsync               
ESTABLISHED
tcp        0      0 ::ffff:192.168.10.25:ssh    ::ffff:192.168.10.50:36001  
ESTABLISHED
tcp        0      0 ::ffff:192.168.10.25:ssh    ::ffff:192.168.10.50:52663  
ESTABLISHED


servera:
tcp    72300  63800 192.168.0.57:rsync          192.168.0.99:53651          
ESTABLISHED

iam backing up about 25 to 50 gigs of stuff per computer 
/etc
/var/log
/var/www

and it will just thow the error at random spots i have changed switches sata cards motherboards all still have the same issue and i also change network cards 
i have installed build 28 build 29 and build 30 all give me the same error except the version line tag is different per version
Comment 1 Wayne Davison 2006-11-15 19:00:46 UTC
You haven't explained how this is not due to your configuring the timeout wrong.  You should also mention what options you're using.  For instance, using --delete-during is much better when using a timeout than using --delete (which defaults to --delete-before, and results in a lot of dead time on the socket).
Comment 2 william mcinnis 2006-11-16 00:33:45 UTC
ok here is my config as per the email i sent you 
[wmcinnis@clients ~]$ sudo cat /etc/rsyncd.conf 

ignore nonreadable = yes

log file = /var/log/rsyncd.log

log format = %o %h [%a] %m (%u) %f %l %b %c

transfer logging = true

read only = true

lock file = /var/run/rsyncd.lock

hosts allow = 192.168.0.99,192.168.10.25,69.0.162.149,192.168.10.100,192.168.10.101,192.168.0.253,68.16.216.73,192.168.0.56,192.168.0.50,192.168.0.51,66.132.135.26

max connections = 5

uid = root

gid = root

auth users = root

secrets file = /etc/rsyncd.secrets

[www]

        list = true

        path = /var/www

        comment = Comment : var/www

[root]

        list = true

        path = /

        comment = comment : / partition

[shared]

        list = true

        path = /home/shared

        comment = Comment : programmers shared

[logs]

        list = true

        path = /var/log

        comment = Comment : Logs

[etc]

        list= true

        path= /etc

        comment = Comment : etc

 

 

 

 

and personal backup says 

 

full backup started for directory www
Connected to clients:873, remote version 30
Negotiated protocol version 28
Connected to module www
Sending args: --server --sender --numeric-ids --perms --owner --group -D --links --times --recursive --ignore-times . .
 

i have added timeout = 600 on both the client and server and same issue
Comment 3 william mcinnis 2006-11-16 00:37:42 UTC
and just now i have tried timeout = 0 on both ends
Comment 4 william mcinnis 2006-11-16 00:46:22 UTC
same results
Comment 5 Rudy 2007-05-25 05:44:59 UTC
I was able to replicate this error.
I use rsync to mirror "Project Gutenberg" from "ibiblio.org". That is about 245GB of data in about 358'000 files. Since about one week i got the following error:
"timeout in data send/receive (code 30) at io.c(165)" 
It also indicated that i used version 2.6.8 and ibiblio used 2.6.9. 
 - Upgraded to 2.6.9
 - Still the same error.
I used "rsync -avHS --delete --progress remote.place local.place"
started reading the FAQ and then this bug list
The option "--delete-during" solved the problem!
Comment 6 Wayne Davison 2010-08-21 13:12:05 UTC
The timeout code in 3.1.0dev is much improved over 2.x and 3.0.x.  Hopefully this will fix the issue you were seeing.