https://bugzilla.samba.org/show_bug.cgi?id=10035
--- Comment #6 from Nestor Urquiza <nestor.urqu...@gmail.com> 2013-07-25 17:23:06 UTC --- I set my script which uses rsync to run every hour. Last night I logged a snoop result (tcp sniffer) but also a netstat result every minute. It failed two ties: 00:15 RSYNC hags for the first time. rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (56207 bytes received so far) [generator] rsync error: timeout in data send/receive (code 30) at io.c(605) [generator=3.0.9] At this point from netstat we can see the same connection for as long as one complete hour: 192.168.5.124.22 client.46480 49640 0 49640 0 ESTABLISHED It is not until the next hour when that connection disappears and the new connection from the new rsync instance shows up. Why the rsync timeout does not work I do not know but it should have closed that connection 30 minutes after it started: 192.168.5.124.22 client.47122 46720 5319 49640 0 ESTABLISHED >From snoop we see first a lot of PUSH: 0:17:44.19207 client -> server TCP D=22 S=45088 Ack=2803790001 Seq=3254408116 Len=0 Win=45260 0:17:44.21747 server -> client TCP D=45088 S=22 Push Ack=3254408212 Seq=2803900013 Len=1208 Win=49640 0:17:49.14072 server -> client TCP D=45088 S=22 Ack=3254418532 Seq=2819000581 Len=1460 Win=49640 0:17:52.58905 server -> client TCP D=45088 S=22 Ack=3254425348 Seq=2829000925 Len=1460 Win=49640 0:17:52.58923 client -> server TCP D=22 S=45088 Ack=2829000925 Seq=3254425348 Len=0 Win=46720 0:17:55.51377 client -> server TCP D=22 S=45088 Ack=2837490005 Seq=3254431156 Len=0 Win=49640 0:17:55.51401 server -> client TCP D=45088 S=22 Ack=3254431156 Seq=2837490005 Len=1460 Win=49640 0:17:55.65287 server -> client TCP D=45088 S=22 Ack=3254431396 Seq=2837900009 Len=1460 Win=49640 0:17:56.03237 server -> client TCP D=45088 S=22 Ack=3254432164 Seq=2839000357 Len=1460 Win=49640 0:17:56.43671 server -> client TCP D=45088 S=22 Ack=3254432980 Seq=2840190009 Len=1460 Win=49640 0:17:56.43685 client -> server TCP D=22 S=45088 Ack=2840190009 Seq=3254432980 Len=0 Win=48180 0:17:59.34139 server -> client TCP D=45088 S=22 Push Ack=3254438932 Seq=2848900045 Len=1208 Win=49640 0:17:59.37478 client -> server TCP D=22 S=45088 Ack=2849000373 Seq=3254438980 Len=0 Win=49640 0:17:59.38230 server -> client TCP D=45088 S=22 Ack=3254438980 Seq=2849000373 Len=1460 Win=49640 0:17:59.94439 server -> client TCP D=45088 S=22 Ack=3254440132 Seq=2850690005 Len=1460 Win=49640 0:17:59.94445 client -> server TCP D=22 S=45088 Ack=2850690005 Seq=3254440132 Len=0 Win=49640 0:18:0.37861 client -> server TCP D=22 S=45088 Ack=2851990005 Seq=3254441044 Len=0 Win=49640 0:18:0.38616 server -> client TCP D=45088 S=22 Ack=3254441044 Seq=2851990005 Len=1460 Win=49640 0:18:1.01774 server -> client TCP D=45088 S=22 Ack=3254442340 Seq=2853890009 Len=1460 Win=49640 0:18:1.01798 client -> server TCP D=22 S=45088 Ack=2853890009 Seq=3254442340 Len=0 Win=48180 0:18:2.72033 server -> client TCP D=45088 S=22 Push Ack=3254445796 Seq=2859000285 Len=1224 Win=49640 0:18:2.72057 client -> server TCP D=22 S=45088 Ack=2859000285 Seq=3254445796 Len=0 Win=46720 0:18:3.01461 server -> client TCP D=45088 S=22 Ack=3254446420 Seq=2859900029 Len=1460 Win=49640 0:18:3.01479 client -> server TCP D=22 S=45088 Ack=2859900029 Seq=3254446420 Len=0 Win=46720 0:18:6.63878 server -> client TCP D=45088 S=22 Ack=3254454772 Seq=2872190005 Len=1460 Win=49640 0:18:7.93095 server -> client TCP D=45088 S=22 Push Ack=3254457364 Seq=2875900093 Len=1224 Win=49640 0:18:8.88357 server -> client TCP D=45088 S=22 Ack=3254459476 Seq=2879000797 Len=1460 Win=49640 Then we see the server sending Syn but the client replies RST aborting such connection attempt: 0:31:26.82366 server -> client TCP D=9000 S=65013 Syn Seq=2618246633 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:31:26.82390 client -> server TCP D=65013 S=9000 Rst Ack=2618246634 Win=0 0:32:27.31389 server -> client TCP D=9000 S=65027 Syn Seq=2634946872 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:32:27.31414 client -> server TCP D=65027 S=9000 Rst Ack=2634946873 Win=0 0:33:27.44815 server -> client TCP D=9000 S=65040 Syn Seq=2651282487 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:33:27.44839 client -> server TCP D=65040 S=9000 Rst Ack=2651282488 Win=0 0:34:27.60344 server -> client TCP D=9000 S=65053 Syn Seq=2667734624 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:34:27.60369 client -> server TCP D=65053 S=9000 Rst Ack=2667734625 Win=0 0:35:27.74829 server -> client TCP D=9000 S=65066 Syn Seq=2684174414 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:35:27.74849 client -> server TCP D=65066 S=9000 Rst Ack=2684174415 Win=0 0:36:27.89816 server -> client TCP D=9000 S=65079 Syn Seq=2700669927 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:36:27.89839 client -> server TCP D=65079 S=9000 Rst Ack=2700669928 Win=0 0:37:28.03938 server -> client TCP D=9000 S=65092 Syn Seq=2717056785 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:37:28.03960 client -> server TCP D=65092 S=9000 Rst Ack=2717056786 Win=0 0:38:28.17940 server -> client TCP D=9000 S=65105 Syn Seq=2733472760 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:38:28.17964 client -> server TCP D=65105 S=9000 Rst Ack=2733472761 Win=0 0:39:28.31650 server -> client TCP D=9000 S=65118 Syn Seq=2749919254 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK> 0:39:28.31672 client -> server 04:15 RSYNC issue. Nothing in netstat so I assume there was never a connection established: deleting ckp.9000.20130724.0/segment.107/segment.10727.portfolio.VELOCITY.19 deleting ckp.9000.20130724.0/segment.107/segment.10726.portfolio.GOLDFINCH.33 rsync error: timeout in data send/receive (code 30) at io.c(137) [sender=3.0.9] rsync: connection unexpectedly closed (206402787 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] Snoop shows exactly what I wrote above -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
