On Mon, Oct 31, 2022 at 03:43:28PM +0000, Edd Barrett wrote:
On Fri, Oct 28, 2022 at 05:04:10PM +0200, Oswald Buddenhagen wrote:
i need the full log. in fact, of two consecutive runs, as this is an
inter-run problem. you can limit it on the command line to the affected
mailbox, and send me the log in private.
so, after not even two years after i received the logs (:'-D), i finally
analyzed them. posting for posterity.
Socket error on imap.gmail.com (142.251.5.109:993): timeout.
for unclear reasons, mbsync was pushing out the entire 25 meg message
within a second, while of course it takes a while to actually upload it
and get a response from the server. i suppose the problem was buffer
bloat on the network.
just raising Timeout to something generally considered unreasonable
would be a suitable workaround.
Warning: lost track of 104 pulled message(s)
Warning: lost track of 1 pushed message(s)
Searching the internet, lots of other people have enountered this, and
as far as I can see, the general advice is "don't worry about it".
Problem is, the message doesn't go away when you re-run mbsync.
that's because the sync never finished due to the timeout, and so the
journal was replayed each time and the (non-)problem reported again.
anyway, these messages are gone since commit 254d2be9.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
