<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div>hello,<br></div><br>trying to understand why a rsync client hangs during a transfer. Hopefully someone can advise.<br><br></div>client = rsync 3.0.6, server = rsync 3.1.1 , transfer is done to a rsync module with such a command:<br></div></div></div><div>rsync -rtxvvv my_data
<a class="" href="mailto:rsync://test@rsync.resif.fr/INCOMING_TEST/">rsync://test@my.rsync.server/INCOMING/</a><br><br></div>the client starts to transfer data (a few Mb) then hangs, then manually interrupted (CTRL+C)<br>a few minutes after. strace output on the client side is:<br></div><br>(...)<br>4251 17:14:30 select(4, NULL, [3], [3], {60, 0}) = 1 (out [3], left {59, 999998})<br>14251 17:14:30 write(3, "\374\17\0\7", 4) = 4<br>14251 17:14:30 select(4, NULL, [3], [3], {60, 0}) = 1 (out [3], left {59, 999998})<br>14251 17:14:30 write(3, "\337\364(\374\3567\t\361=\373\25@\0'+\00 (...)<br>14251 17:14:30 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:15:30 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:16:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:17:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:18:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:19:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:20:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:21:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:22:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:23:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:24:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:25:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:26:31 select(4, NULL, [3], [3], {60, 0}) = 0 (Timeout)<br>14251 17:27:31 select(4, NULL, [3], [3], {60, 0}) = ? ERESTARTNOHAND (To be restarted)<br>14251 17:28:10 --- SIGINT (Interrupt) @ 0 (0) ---<br>4251 17:28:10 select(0, NULL, NULL, NULL, {0, 400000}) = 0 (Timeout)<br>14251 17:28:10 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 0x371a432920}, NULL, 8) = 0<br>14251 17:28:10 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 0x371a432920}, NULL, 8) = 0<br>14251 17:28:10 write(2, "rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [sender=3.0.6]", 89) = 89<br>14251 17:28:10 write(2, "\n", 1) = 1<br>14251 17:28:10 write(1, "_exit_cleanup(code=20, file=rsync.c, line=544): about to call exit(20)\n", 71) = 71<br>14251 17:28:10 exit_group(20) = ?<br><br></div>Send-Q ont the client side looks like:<br><br> <font face="Calibri"><span style="font-size:11pt"><div><font face="Courier New">Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name</font></div>
<div><font face="Courier New">tcp 41 62844 132.xxx.xxx.xx:41397 152.xx.xx.xx:873 ESTABLISHED 3387/rsync</font></div></span></font><br></div>On the server side, rsync daemon log says :<br><br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: [generator] receiving flist for dir 10<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: recv_file_name(sds_extract/2015/RD/LOR/BHN.D/RD.LOR..BHN.D.2015.055)<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: received 1 names<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: recv_file_list done<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: recv_generator(sds_extract/2015/RD/LOR/BHN.D,19)<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: set modtime of sds_extract/2015/RD/LOR/BHN.D to (1424884220) Wed Feb 25 17:10:20 2015<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: sds_extract/2015/RD/LOR/BHN.D/<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: recv_generator(sds_extract/2015/RD/LOR/BHN.D/RD.LOR..BHN.D.2015.055,20)<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: [generator] receiving flist for dir 11<br>Feb 25 17:14:25 resif-vm13 rsyncd[2403]: recv_file_name(sds_extract/2015/RD/LOR/BHZ.D/RD.LOR..BHZ.D.2015.055)<br>Feb 25 17:35:07 resif-vm13 rsyncd[2403]: rsync: connection unexpectedly closed (12005 bytes received so far) [generator]<br>Feb 25 17:35:07 resif-vm13 rsyncd[2403]: rsync error: error in rsync protocol data stream (code 12) at io.c(226) [generator=3.1.1]<br>Feb 25 17:35:07 resif-vm13 rsyncd[2403]: [generator] _exit_cleanup(code=12, file=io.c, line=226): about to call exit(12)<br><br></div>please note : clocks on server and client are maybe not exactly the same. I don't have easy console access to client (remote customer's).<br></div>Does someone have an idea of why it hangs ? Seems like the client side is hanging on a select() call, which would mean<br></div>that one the file selected for transfer is locked for reading (true/false?) ? <br></div><br></div>any suggestion welcome<br></div>Tom<br></div>