Re: 3.0 to 3.2 sync error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Quoting ellie timoney <ellie@xxxxxxxxxxxx>:

Hi,

On Sun, 29 Aug 2021, at 8:28 PM, Lists Nethead wrote:
29392: write(6,"S2 SYNCAPPLY MAILBOX %(UNIQUEID
6uxzsiuvofrhrf69dfs1uqxq MBOXNAME user.ppgw SYNC_CRC 2538953411
SYNC_CRC_ANNOT 307862686 LAST_UI"...,4096) = 4096 (0x1000)
29392: write(6,"ATIONS (%(ENTRY /vendor/cmu/cyrus-imapd/thrid USERID
NIL VALUE 87f494ec1d410ff7))) %(UID 18 MODSEQ 194 LAST_UPDATED
1620897300 F"...,4096) = 4096 (0x1000)
29392: write(6,"12 LAST_UPDATED 1620897300 FLAGS () INTERNALDATE
1608458977 SIZE 58108 GUID 03fd1fb95a2083a702fcf679a0e62182698ea1f8
ANNOTATIONS"...,1984) = 1984 (0x7c0)

It's hard to see what it might be complaining about, since the "S2 SYNCAPPLY ..." command it's trying to send is 4096+4096+1984 bytes long, and is heavily abbreviated in the strace output.

You can log what's actually going over the wire by enabling telemetry for the user: https://www.cyrusimap.org/imap/reference/faqs/o-telemetry.html

In this case, you would want to set up telemetry on your replica server, for the user named by "sync_authname" on your main server. This will make the replica log all the replication traffic it receives.

If you can reproduce the bad protocol error by replicating just one test folder for one test user, then that's probably the least-noisy way to proceed, and without worry about exposing anyone's mail contents.

But if you can't reproduce it with a test folder in a test account, then it might be something specific to the user or mailbox that's causing the problem, which will be harder to figure out...


Some more. I ran cvt_xlist_specialuse and afterwards sync_server with the -u option completes without syncing due to mailbox does not exist.
With the -m option, a full sync is start:

1630319017>S2 OK success
<1630319017<S3 SYNCAPPLY MAILBOX %(UNIQUEID 6uxzsiuvofrhrf69dfs1uqxq
[lots of output]
ANNOTATIONS (%(ENTRY /vendor/cmu/cyrus-imapd/thrid USERID NIL VALUE 2de14fdc44df6e6f)))))
1630319017>S3 NO IMAP_PROTOCOL_ERROR Protocol error
<1630319017<Q01 LOGOUT

So now it is S3 rather than S2, whatever that means.

Thanks,
Per


------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Te28e46bb80b596a6-Md9b5c090536aa22e5e5ac4e3
Delivery options: https://cyrus.topicbox.com/groups/info/subscription




[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux