Kenneth Porter wrote at about 01:51:53 -0800 on Sunday, January 23, 2022: > On 1/22/2022 11:45 PM, backu...@kosowsky.org wrote: > > #1 0x000055555543fc43 in perform_io (needed=2, flags=2) at io.c:742 > > This smells like a deadlock. This code is waiting for 2 bytes in the > socket output buffer so it can write the file's next block checksum. > Perhaps the other side is failing to drain the socket for some reason. > Interesting... 1. If the problem is the other side failing to drain the socket, why would it work for native rsync (same version 3.1.2)? I am struggling to understand what is different at this level between native rsync and rsync-bpc. Does rsync-bpc force some settings or protocol levels under the hood that would cause such a difference?
2. What can I do to troubleshoot this further? BTW thanks for the help so far... it seems like you really understand the rsync code... :) _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
