Re: Out of ideas - migrating from 3.0

On 2026-05-11 17:35, Michael Menge wrote:
>=20
> Quoting Per olof Ljungmark <[email protected]>:
>=20
>> Hi Michael,
>>
>> On 2026-05-11 16:31, Michael Menge wrote:
>>> Hi,
>>>
>>> Quoting Per olof Ljungmark <[email protected]>:
>>>
>>>> On 2026-05-11 15:01, cyrus via Info wrote:
>>>>>>>
>>>>>>> The cyrus.annotations file is 76216 bytes, ALL others are 336 bytes.
>>>>>
>>>>> Also, as far as I know, the per-mailbox cyrus.annotations file was=20
>>>>> abandoned in 2.3 or 2.4, and the central annotations.db file has=20
>>>>> been standard since then.
>>>>>
>>>>> Mark
>>>> Removing the cyrus.annotations file + a recontruct fixed it, thank=20
>>>> you for pointing this out.
>>>>
>>>> Now replicating remaining 200G hoping for the best.
>>>
>>>
>>> did you see any sync errors in the log file.
>>>
>>> As you do have annotations it is most likely Issue 4967.
>>> which breaks replication between 3.0 and 3.2 if the mailbox has=20
>>> annotations
>>> https://github.com/cyrusimap/cyrus-imapd/=20
>>> issues/4967#issuecomment-2227594080
>>>
>> Yes, it must be that issue. Funny though that just one mailbox still=20
>> had it, I thought we got rid of them when moving to 3.0.
>>
>> The replication ended with:
>>
>> <1778496401<S22 NO IMAP_PROTOCOL_ERROR Protocol error
>> sync_client 31597 - - MAILBOX received NO response:=20
>> IMAP_PROTOCOL_ERROR Protocol error
>> sync_client 31597 - - do_folders(): update failed: user.pereri 'Bad=20
>> protocol'
>> sync_client 31597 - - IOERROR: do_user_main: Bad protocol for <user>=20
>> to [no channel] (123.456.789.123)
>> Error from sync_do_user(pereri): bailing out!
>> sync_client 31597 - - Error in sync_do_user(<user>): bailing out!
>>> 1778496401>Q01 LOGOUT
>>
>> I think the [no channel] was the hint?
>=20
> no that is a redhering. In earlier cyrus versions there was only one=20
> rolling logfile
> and no channel name was needed, now you can also use rolling logs search=
=20
> index and
> backups. To keep old configs compatible there is the "no channel" channel
>=20
> The IOERROR and the "bailing out" is the part where the real problem is.
> If i remember correctly i did use strace and gdb to find the real problem
>=20
>=20
>>
>> The replication is still rolling after fixing that single file.
>>
>=20
>=20
> What do you mean with "fixing that sinle file"? If i remember correctly=20
> fixing needed mulitple steps.
> 1. Remove the annotation from the mailbox.
> 2. Reset the replication for the user/remove the mailbox of user form=20
> the destination
> 3. use sync_client whith "-u <userid>" to sync the user again
>=20
I did exactly this.

Per

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T32de718f28fc5421-M94d9ef=
0a65728b5611f909b2
Delivery options: https://cyrus.topicbox.com/groups/info/subscription