On Fri, Jan 04, 2019 at 09:58:38AM -0700, Benjamin Slade wrote: > On 2019-01-04T03:24:26-0700, Oswald Buddenhagen <oswald.buddenha...@gmx.de> > wrote: > > the network activity prior to this would be interesting. with > > timestamps, so pipe the output through ts '%.T'. > > Here is a pastebin of the output, with ellipsis of certain long, > repetitive sections which seemed of no real interest: > > https://paste.ubuntu.com/p/wfWpkBMbd5/ > > Also, I have other machines which pull from the exact same remote > mailboxes and they are not experiencing any such issue, so it is > something local to this machine. > yes, it clearly gets upset when uploading the first message, which has a whopping 9.3 megs, which you presumably don't have in the other clones.
the default timeout of 20 secs is a bit tight, so you may just increase it, and at some point it will work. the underlying issue is that mbsync resets the timeout only when it receives data from the server, which it doesn't do while it uploads lots of stuff to the server over a connection that isn't blazingly fast. a way to get around that would be relying on the kernel's knowledge of TCP ACK packets during the upload, which can be apparently achieved with setsockopt(fd, SOL_TCP, TCP_USER_TIMEOUT, &timeout_ms, sizeof(timeout_ms)) in as far the option is available. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
