Replication problem with user defined imap flag

[Christian Dröge]

Hi,

I have encountered a problem with the replication on cyrus 2.4.16. On
one day the master had problems to replicate the changes of one mailbox
to the replica server via sync_client with the following log entries:

Master log:
ep 27 13:12:50 trisol cyrus/sync_client[19699]: MAILBOX received NO
response: System I/O error
Sep 27 13:12:50 trisol cyrus/sync_client[19699]: do_folders(): update
failed: user.$user 'The remote Server(s) denied the operation'
Sep 27 13:12:50 trisol cyrus/sync_client[19699]: IOERROR: The remote
Server(s) denied the operation
Sep 27 13:12:50 trisol cyrus/sync_client[19699]: Error in do_sync():
bailing out! The remote Server(s) denied the operation
Sep 27 13:12:50 master cyrus/sync_client[19699]: Processing sync log
file /var/spool/imap-metadata/configs/sync/log-19699 failed: The remote
Server(s) denied the operation

Replica log:
Sep 27 13:04:42 replica cyrus/syncserver[25541]: seen_db: user $user
opened /var/spool/imap-metadata/configs/user/R/$user.seen
Sep 27 13:04:45 replica cyrus/syncserver[25541]: Unable to record user
flag: $flag
Sep 27 13:04:45 replica cyrus/syncserver[25541]: Failed to parse
uploaded record


There is nothing strange about the user flag. It only contains lowercase
characters from the alphabet.

I looked at the source code of cyrus, because the errors were not really
helpful and I suppose that the user reached the MAX_USER_FLAGS limit,
because the cyrus.header file on the replica server contains 128 user
flags. On the master server there are only 14 now. Maybe sync_client
first tries to add another user flag that the user added and after that
it would remove the removed user flags, if it did not bail out, and so
the commands are in the wrong order?

Should I file a bug for this problem? It would be good, if there is a
better error message for this case, so that the cause of this problem can
be found easier.

Also I need a fix for this problem. Probably I can delete the mailbox on
the replica and then resync it with "sync_client -u $user" or is there
an easier way to fix this?

Best regards,
Christian Dröge