| Hi all :) :), First of all, thanks a lot for your time :) . At present moment… I’m slightly confused due to all the tests done, attempts to reproduce the issue and all the Cyrus code read... I’ll tell all the history although I think some parts are not relevant but in an attempt to not omit something useful : We were running Cyrus 2.3.18. We moved then to 2.4 as an intermediate version (it converted databases on the fly and so… and although this caused us to work more at nights due to the high load we preferred to do it this way) , in order to be able to finally replicate to a 3.0.8 version. From 2.3 to 2.4 we used sync_client and sync_server and from 2.4 to 3.0 too (if I remember correctly too) because I think Imap replication was not working between 2.4 and 3.0.8. Finally in 3.0.8, we set up another slave for having a couple in 3.0.8 replicating in rolling mode through imap. The first thing we noticed was that in 3.0.8 (when setting this version as master, giving the service), some accounts had the folders not subscribed and the sieve script didn’t exist (created by each user from Roundcube plugin). As when we were in the intermediate phase between 2.4 and 3.0 (a couple of days) some issues appeared (for instance, in some migrations, while we were using 2.4 for the service and replicating with sync_client in user mode to 3.0.8 some Cyrus database locks happened and so…) we though it was due to that version difference. We finally wrote some scripts for copying manually the Sieve scripts manually. We created too another one for massive folder subscription for those customers telling us they were not seeing the folders. We didn’t worry more then, due to the version difference as commented. If all that happened were that, we would be relaxed, but…. New problems come again (from 3.0.8 to 3.0.8)…. We needed to say, that we setup new slaves by just syncing with sync_client in user mode…. Finally run in rolling replication mode with a last user mode replication… Here they are : - When failing over from a 3.0.8 to another 3.0.8 (master-slave change) we saw again the subscription issue mainly (perhaps the Sieve issue could still be there). - When setting up new slaves (for moving vm from storage for instance, we created a new slave) with sync_client in user mode… we didn’t appreciate the Sieve issue (although it could exist), but yes, the subscriptions one…. I started checking what could be happening and I saw some examples as the one described in the mail below. Later, I think I found something more concrete. Please take a look : % ls -al total 104 drwx------ 2 cyrus cyrus 512 Jul 14 03:12 . drwx------ 7 cyrus cyrus 512 Feb 11 14:52 .. -rw------- 1 cyrus cyrus 77072 Jul 15 04:36 a.saizar.conversations -rw------- 1 cyrus cyrus 88 Jul 3 10:00 a.saizar.counters -rw------- 1 cyrus cyrus 36 Mar 15 05:47 a.saizar.sub -rw------- 1 cyrus cyrus 12 Jul 14 03:12 a.saizar.xapianactive -rw------- 1 cyrus cyrus 944 Feb 11 00:41 a^saizar.seen -rw------- 1 cyrus cyrus 203 Feb 11 00:41 a^saizar.sub % pwd /expert/correo/imap/domain/l/xxxxxxxxxxxxx/user/a It seems, that (at least some) of the mailboxes that had a dot in their name, the subscriptions, sieve (I’m pretty sure too) and seen were created in the slave (sync destination) with the Cyrus mailbox internal name (replacing dots with ^)… instead with just a dot, as it’s seen it works normally. It seems, sync_client in user mode was creating the file with the ^ instead the dot. Then when Cyrus was trying to find the file, with the dots (as it was expected) it didn’t find them. So creates new one and then as that new subs database is empty, it’s the same effect as if subscriptions were “not copied” with sync_client. I think, although it’s a theory that all the meta files (quota, sieve, seen, subs) are created the same way, all of them with ‘^’ when only quota file has to have that name format. So, for summarizing I think I have observed two important issues : 1 - When you replicate from a 3.0.8 master to 3.0.8 slave sometimes subscriptions (at least, I assume to seen and probably Sieve) are not copied properly (are copied with the dot) and then as the file is not present when Cyrus tries to access with the proper name… creates a new database for subscriptions and considers it’s, just empty… no subscriptions…. I’d say the problem affects just to users who have a dot in the username part (without the domain) of the email. Happens in user mode replication. 2 - Seen a lot at differences of subscribed folders in a master in a slave (both in 3.0.8 and in rolling replication) I saw some differences in some enumerated accounts of some customers : Jul 12 10:13:26 mx13c imap[53014]: conversations_rename_folder: renamed xxxxxxx.com!user.gl-p^expooort.Sent.OFERTAS.AGENTES VENDA.Gabana Logistics to xxxxxxx.com!user.gl-p^expooort.Sent.OFERTAS.Gabana Logistics Jul 12 10:13:26 mx13c imap[53014]: Rename: xxxxxxx.com!user.gl-p^expooort.Sent.OFERTAS.AGENTES VENDA.Gabana Logistics -> xxxxxxx.com!user.gl-p^expooort.Sent.OFERTAS.Gabana Logistics Jul 12 10:13:26 mx13c imap[53014]: Deleted mailbox xxxxxxx.com!user.gl-p^expooort.Sent.OFERTAS.AGENTES VENDA.Gabana Logistics Gabana Logistics (xxxxxxx.com!user.gl-p^expooort.Sent.OFERTAS.AGENTES VENDA.Gabana Logistics) is still subscribed in the actual slave (and in the slave in that moment). My suspects are : - For the first commented issue (number 1), sync_client when populating dlists, seems to perform an incorrect name conversion (conversion to internal name when shouldn’t) and then when creating quota, sieve, seen and subs, quota is created properly but not he other ones… - For the second commented one (number 2)… I’d say a mboxlist_changesub is missing if RFC says the behavior of the mua is correct. I do attach the files of a master and slave in Cyrus 3.0.8. If you needed a cyrus.conf file too please tell me. I’m at your disposal for whatever you needed for fixing this. Best regards, |
Attachment:
master-file
Description: Binary data
Attachment:
slave-file
Description: Binary data
|
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
