Re: 3.0 to 3.2 sync error

Lists Nethead <lists@xxxxxxxxxx> · Mon, 30 Aug 2021 08:29:19 +0200

 Hi Andrew,

Thank you for responding but this has nothing to do with  
connectivity,&nbsp; the setup worked nicely before with 3.0 to 3.0 sync.

Per

Quoting AndrewHardy via Info <info@xxxxxxxxxxxxxxxxxx>:

Good Morning,    &nbsp;
  Reference below:
  &nbsp;
  https://www.cyrusimap.org/3.4/imap/reference/admin/sop/replication.html
  &nbsp;
  Pre-3.0 used dedicated csync transport over tcp 2005. From 3.0  
onwards, uses IMAP protocol.
  &nbsp;
  May be worth while confirming imap connectivity is possible  
between the 3.0 and 3.2 node (telnet testing etc). Also try force a  
sync and monitor the 3.2 node to see if traffic is reaching the node  
or if it’s failing on the 3.0 node before traffics sent.
  &nbsp;
  Would be worth while reviewing your replication configuration on  
the client and server. Do you have TLS configured or just using  
standard IMAP over TCP 143?
  &nbsp;
  Regards
  Andrew

On 29/08/2021, at 22:34, Lists Nethead <lists@xxxxxxxxxx> wrote:
&nbsp;
Hello,

In testing 3.0 (latest) to 3.2 (latest) migration, sync always  
fails here on all mailboxes:

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)
29392: sigprocmask(SIG_BLOCK,{  
SIGINT|SIGQUIT|SIGALRM|SIGTERM|SIGCHLD },{ }) = 0 (0x0)
29392:  
pselect(0x7,0x7fffffffe390,0x0,0x0,0x7fffffffe2d0,0x7fffffffe2e0) =  
1 (0x1)
29392: sigprocmask(SIG_SETMASK,{ },0x0)  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= 0 (0x0)
29392: read(6,"S2 NO IMAP_PROTOCOL_ERROR Protocol error\r\n",4096)  
= 42 (0x2a)
29392: getpid()  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= 29392  
(0x72d0)
29392: sendto(7,"<179>Aug 29 12:17:47 sync_client[29392]: MAILBOX  
received NO response: IMAP_PROTOCOL_ERROR Protocol  
error",105,0,NULL,0) = 105 (0x69)
29392: getpid()  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= 29392  
(0x72d0)
29392: sendto(7,"<179>Aug 29 12:17:47 sync_client[29392]:  
do_folders(): update failed: user.ppgw 'Bad protocol'",94,0,NULL,0)  
= 94 (0x5e)
Error from sync_do_mailboxes(): bailing out!

So it is a IMAP_PROTOCOL_ERROR, but how do I find out which
protocol is failing? And more importantly, how do I get rid of the
error?

Thank you in advance,
Per

  CYRUS[1] / Info / see discussions[2] + participants[3] +  
delivery&nbsp;options[4] Permalink[5]

Links:
------
[1] https://cyrus.topicbox.com/latest
[2] https://cyrus.topicbox.com/groups/info
[3] https://cyrus.topicbox.com/groups/info/members
[4] https://cyrus.topicbox.com/groups/info/subscription
[5]  
https://cyrus.topicbox.com/groups/info/Te28e46bb80b596a6-M46f669b7bd2058712293c26a

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