On Wed, Aug 04, 2021 at 08:22:33AM +0200, Uwe Kleine-König wrote:
from time to time I experience mbsync (from the 1.3.0-2.2 Debian
package) saying:
the debian package is orphaned. it's better to build v1.4 from source.
Aug 04 07:31:13 taurus syncmail-work[1553327]: Warning: lost track of
460840 pulled message(s)
that's supposed to happen only for messages that were "in flight" when a
sync run was interrupted.
but the way you describe it (and the sheer number of messages) suggests
that this happens out of the blue for messages that should have been
committed long ago.
Aug 04 07:31:14 taurus syncmail-work[1553327]: Socket error: secure
write to tunnel 'ssh -W imap:143 ptz.ptx': Broken pipe
that's after the above message, so while it's already trying to resync,
and it should abort due to that. that means that you must have run
mbsync again to observe this:
which results into mbsync taking several hours to resync [...]
that makes me wonder what other minor details you missed/omitted. ;)
one that would matter: after the resync, are the messages duplicated? on
the client? the server?
My .mbsyncrc looks as follows:
nothing obviously wrong with it, afaics.
Tunnel "ssh -W imap:143 ptz.ptx"
SSLType STARTTLS
that's a weird combo. going around a firewall?
Any hint how to debug that?
first verify that mbsync actually exits cleanly. otherwise the sync
journal would grow indefinitely, which might in principle cause a
ridiculous number of messages being reported as lost (though it would
require an additional problem somewhere).
then, have a look at the actual folders, specifically the .mbsyncstate*
files. there should be no .*.lock, .*.new or .*.journal files.
the way to do "real" debugging is to run with -D and save the logs. but
given the number of messages involved and the fact that this happens
only occasionally is likely to make this painful.
have "fun" ...
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
