Re: Replication : IMAP_PROTOCOL_ERROR Protocol error

Jean Charles Delépine écrivait (wrote) : > Jean Charles Delépine écrivait (wrote) : > > > Hello, > > > > I'm on the way to migrate one quite big murder config with Cyrus IMAP > > 3.0.8-Debian-3.0.8-6+deb10u4 > > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1. > > > > My plan is to replicate 3.0.8

Re: Replication : IMAP_PROTOCOL_ERROR Protocol error

ellie timoney écrivait (wrote) : > On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote: > > Is this a known problem corrected after 3.0.9 ? > > Off the top of my head I no longer remember, but the current release in the > 3.0 series is 3.0.14. I'd suggest, if you haven't already, that

Re: Replication : IMAP_PROTOCOL_ERROR Protocol error

On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote: > Is this a known problem corrected after 3.0.9 ? Off the top of my head I no longer remember, but the current release in the 3.0 series is 3.0.14. I'd suggest, if you haven't already, that you look in the release notes from 3.0.8-3.

Re: Replication : IMAP_PROTOCOL_ERROR Protocol error

Jean Charles Delépine écrivait (wrote) : > Hello, > > I'm on the way to migrate one quite big murder config with Cyrus IMAP > 3.0.8-Debian-3.0.8-6+deb10u4 > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1. > > My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work > before for 2.

Re: Replication and Deleted Files

On Thu 04 Jun 2020 at 18:57:37, Michael Menge (michael.me...@zdv.uni-tuebingen.de) wrote: > you also need to run cyr_expire on the "new_server" to remove the old expunged mails and deleted folders. Obvious when you try it!    Thanks so much.   Expired 23 and expunged 7617 out of 289060 me

Re: Replication and Deleted Files

Hi, Quoting Ian Batten via Info-cyrus : Hi, long-time Cyrus user (25 years, I think), but stumped on this one… I have an ancient Cyrus 2.5.11 on Solaris 11 installation I am trying to migrate off.  The strategy is to run rolling replication onto the new server (3.0.8-6+deb10u4 on Debian 10

Re: Replication failed 3.0.5 -> 3.0.13

On 2020-04-29 16:47, Andrzej Kwiatkowski wrote: Ok. I was asking because of problem with low entropy on VM-s causing performance issues with big installations. I didn't have this issue, however as I said, my installation is really small. If I needed more entropy I would think of using a hardw

Re: Replication failed 3.0.5 -> 3.0.13

W dniu 22.04.2020 o 10:19, Olaf Frączyk pisze: > On 2020-04-22 09:16, Andrzej Kwiatkowski wrote: >> W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze: >>> Hi, >>> >>> I'm running 3.0.5. >>> >>> I want to migrate to a new machine. I set up cyrus-imapd 3.0.13. >>> >>> The replication started but it didn'

Re: Replication failed 3.0.5 -> 3.0.13

On 2020-04-22 09:16, Andrzej Kwiatkowski wrote: W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze: Hi, I'm running 3.0.5. I want to migrate to a new machine. I set up cyrus-imapd 3.0.13. The replication started but it didn't transfer all mails. The store isn't big 44GB, transferred was about 24

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Yes, Michael was right - it works properly now. (I hope ;). OK. I'll put it in the DAEMON section - this way I have only one point where all stuff related to imap is started. Thank you for explanation. Regards, Olaf On 2020-04-22 02:36, ellie timoney wrote: I think Michael's got this pretty

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

On 2020-04-21 20:40, Michael Menge wrote: Quoting Olaf Frączyk : Yes, at the beginning I was also thinking if initial sync is necessary, but there was nothing in docs about it, something started replicating and I simply assumed it does initial resync. I'll try it this evening. :) Since y

Re: Replication failed 3.0.5 -> 3.0.13

W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze: > Hi, > > I'm running 3.0.5. > > I want to migrate to a new machine. I set up cyrus-imapd 3.0.13. > > The replication started but it didn't transfer all mails. > > The store isn't big 44GB, transferred was about 24 GB. > > In the logs I see: > Ol

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

I think Michael's got this pretty much covered -- you need to disable the rolling replication for now, and then use sync_client -u (or if you're brave, sync_client -A) to get an initial sync of everything. These two options work entire-user-at-a-time, so they should detect and fix the problems

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Quoting Olaf Frączyk : Yes, at the beginning I was also thinking if initial sync is necessary, but there was nothing in docs about it, something started replicating and I simply assumed it does initial resync. I'll try it this evening. :) Since you use replication - are sieve scripts r

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

On 2020-04-21 16:00, Michael Menge wrote: Hi, Quoting Olaf Frączyk : I managed to get strace on both sides, however it doesn't make me wiser - there is nothing obvious for me. Additionally I see that replication works more or less for new messages, but older are not processed. I have sev

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Hi, Quoting Olaf Frączyk : I managed to get strace on both sides, however it doesn't make me wiser - there is nothing obvious for me. Additionally I see that replication works more or less for new messages, but older are not processed. I have several subfolders in my mailbox, some of the

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

I managed to get strace on both sides, however it doesn't make me wiser - there is nothing obvious for me. Additionally I see that replication works more or less for new messages, but older are not processed. I have several subfolders in my mailbox, some of them unreplicated. If I change any

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Quoting Olaf Frączyk : Thank you for the telemetry hint :) I don't use the syncserver - the replication is done via IMAP port on the replica side. I have no idea how to have strace spawned by cyrus master process. When I attach later to imapd using strace -p I'm afraid some info already

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Thank you for the telemetry hint :) I don't use the syncserver - the replication is done via IMAP port on the replica side. I have no idea how to have strace spawned by cyrus master process. When I attach later to imapd using strace -p I'm afraid some info already will be lost. The syncserve

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Hi, Quoting Olaf Frączyk : The current situation is: 1. Replica: stopped and started the replica no activity on replica - iotop and top show nothing the only messages on replica is incoming connection from master 2. Master: when I run sync_client -r I still get: Apr 21 12:38:36 ifs sync_

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

The current situation is: 1. Replica: stopped and started the replica no activity on replica - iotop and top show nothing the only messages on replica is incoming connection from master 2. Master: when I run sync_client -r I still get: Apr 21 12:38:36 ifs sync_client[29518]: Reprocessing sy

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

I also found out that when I see on master: Apr 21 11:12:38 ifs sync_client[27996]: IOERROR: zero length response to MAILBOXES (idle for too long) Apr 21 11:12:38 ifs sync_client[27996]: IOERROR: zero length response to RESTART (idle for too long) Apr 21 11:12:38 ifs sync_client[27996]: Error i

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Hi, When I run sync_client -r on the master I see the following on the replica: Apr 21 10:56:15 skink1 imap[5775]: mailbox: longlock navi.pl!user.olaf for 1.7 seconds Apr 21 10:56:20 skink1 imap[5775]: mailbox: longlock navi.pl!user.piotr for 2.0 seconds Apr 21 10:56:23 skink1 imap[5775]: mail

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Hi Olaf Quoting Olaf Frączyk : Hi, I upgraded to 3.0.13 but it didn't help. This time it copied about 18GB in the logs I still see: 1 - inefficient replication 2 - IOERROR: zero length response to MAILBOXES (idle for too long) IOERROR: zero length response to RESTART (idle for too long) E

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

Hi, I upgraded to 3.0.13 but it didn't help. This time it copied about 18GB in the logs I still see: 1 - inefficient replication 2 - IOERROR: zero length response to MAILBOXES (idle for too long) IOERROR: zero length response to RESTART (idle for too long) Error in do_sync(): bailing out! Bad

Re: Replication - current status and how to do failover

On Sun, Apr 5, 2020, at 00:45, Olaf Frączyk wrote: > Hello, > > 1. Is currently master-master replication possible (maybe 3.2) Is it OK > to sync them two-way? No, not really. It'll mostly be fine, but it doesn't (yet) handle folder create/rename/delete safely. > If yes - how to set up such

Re: Replication failing - IMAP_SYNC_CHECKSUM Checksum Failure

Sounds like you have been fiddling mailboxes.db entries and/or didn't clean it up properly? I would recommend sync_reset on the user on the replica for a better cleanup than delete. Oh yeah, don't create the mailbox on the replica before replicating it in, that's crazy talk - you'll get a new

Re: Replication failing - IMAP_SYNC_CHECKSUM Checksum Failure

I resorted to deleting the mailbox on the replication slave and trying to start from scratch, but I get nowhere. On slave: cyrus@cyrus2c:~> cyradm --user mailadmin `hostname` cyrus2c.mail.rice.edu> dm user/lamemm7 cyrus2c.mail.rice.edu> cm --partition cyrus2g user/lamemm7 cyrus2c.mail.ric

Re: Replication failing - IMAP_SYNC_CHECKSUM Checksum Failure

What do you see in syslog? (both for the reconstruct and later when the sync_client runs) On Tue, 23 Aug 2016, at 03:49, Tod A. Sandman via Info-cyrus wrote: > I'm using rolling replication with cyrus-imapd-2.5.9. sync_client died and I > am not able to get replication working again. I've nar

Re: Replication CRC error

Master has: commit 6ef874319ecd98700e682ef30fcad5245ddfdb32 Author: Bron Gondwana Date:   Wed Oct 22 14:51:24 2014 -0400 sync_client: do ALL mailboxes, not just all users, for -A flag It should be pretty cherry-pickable back to 2.5 I would imagine. Bron. On Thu, Mar 3, 2016, at 09:17, Artyom

Re: Replication CRC error

Hi, When using the “-A” flag (sync all users) no non-user mailboxes are synced. As the man page imapd.conf(5) notes, ”... this could be considered a bug and maybe it should do those mailboxes independently.” Source: https://cyrusimap.org/imap/admin/sop/replication.html But how in this case restor

Re: Replication problem do_folders(): failed to rename

Am Montag, den 14.12.2015, 07:31 -0400 schrieb Patrick Boutilier via Info-cyrus: > On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: > > Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via > > Info-cyrus: > >> Hi, > >> > >> I have a problem with a single mailbox. The user'

Re: Replication problem do_folders(): failed to rename

Hi, Am Montag, den 14.12.2015, 12:53 +0100 schrieb Michael Menge via Info-cyrus: > Hi, > > > Quoting Patrick Boutilier via Info-cyrus : > > > On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: > >> Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via > >> Info-cyrus: > >

Re: Replication problem do_folders(): failed to rename

Hi, Quoting Patrick Boutilier via Info-cyrus : On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: Hi, I have a problem with a single mailbox. The user's Outlook crashed and since then the sync_client is

Re: Replication problem do_folders(): failed to rename

On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: Hi, I have a problem with a single mailbox. The user's Outlook crashed and since then the sync_client is running wild on this user account and produces hig

Re: Replication problem do_folders(): failed to rename

Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: > Hi, > > I have a problem with a single mailbox. The user's Outlook crashed and > since then the sync_client is running wild on this user account and > produces high load on the master. I stopped sync_client on master

Re: Replication problem do_folders(): failed to rename

Hi, forgot the cyrus version: 2.4.12 on Ubuntu 12.04 LTS Ciao! 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

Re: replication: sync_client on master stops after restarting the replica

Am Donnerstag, den 16.10.2014, 14:57 +0200 schrieb Rudy Gevaert: > On Tue, Oct 14, 2014 at 10:28:24PM +0200, Marcus Schopen wrote: > > > > Thanks, what a great idea. > > > > Is it this script? > > > > https://github.com/rgevaert/cyrus-ugent/blob/master/src/cyrus-synccheck > > > > Hi, yes it is

Re: replication: sync_client on master stops after restarting the replica

Hi Rudy, Am Montag, den 13.10.2014, 10:41 +0200 schrieb Rudy Gevaert: > > > On 09/27/14 10:59, Marcus Schopen wrote: > > Hi, > > > > always when I have to reboot the replica or its cyrus the > > synchronization on master side stops, /var/lib/cyrus/sync/log fills up > > and I don't see a "/usr/li

Re: replication: sync_client on master stops after restarting the replica

On 09/27/14 10:59, Marcus Schopen wrote: > Hi, > > always when I have to reboot the replica or its cyrus the > synchronization on master side stops, /var/lib/cyrus/sync/log fills up > and I don't see a "/usr/lib/cyrus/bin/sync_client -r" process anymore. > > /var/log/mail.err on master when rest

Re: replication: sync_client on master stops after restarting the replica

On 10/10/2014 09:31 AM, Marcus Schopen wrote: Hi Patrick, Am Freitag, den 10.10.2014, 09:13 -0300 schrieb Patrick Boutilier: On 10/10/2014 09:09 AM, Marcus Schopen wrote: Am Samstag, den 27.09.2014, 10:59 +0200 schrieb Marcus Schopen: Hi, always when I have to reboot the replica or its cyrus

Re: replication: sync_client on master stops after restarting the replica

Hi Patrick, Am Freitag, den 10.10.2014, 09:13 -0300 schrieb Patrick Boutilier: > On 10/10/2014 09:09 AM, Marcus Schopen wrote: > > Am Samstag, den 27.09.2014, 10:59 +0200 schrieb Marcus Schopen: > >> Hi, > >> > >> always when I have to reboot the replica or its cyrus the > >> synchronization on ma

Re: replication: sync_client on master stops after restarting the replica

On 10/10/2014 09:09 AM, Marcus Schopen wrote: Am Samstag, den 27.09.2014, 10:59 +0200 schrieb Marcus Schopen: Hi, always when I have to reboot the replica or its cyrus the synchronization on master side stops, /var/lib/cyrus/sync/log fills up and I don't see a "/usr/lib/cyrus/bin/sync_client -r

Re: replication: sync_client on master stops after restarting the replica

Am Samstag, den 27.09.2014, 10:59 +0200 schrieb Marcus Schopen: > Hi, > > always when I have to reboot the replica or its cyrus the > synchronization on master side stops, /var/lib/cyrus/sync/log fills up > and I don't see a "/usr/lib/cyrus/bin/sync_client -r" process anymore. > > /var/log/mail.e

Re: replication

On Mon, 2014-04-21 at 22:34 +0600, Eugene M. Zheganin wrote: > If I'm using replication, and master goes offline for a moment, and I > have some mail delivered on replica (from SMTP, beacuse I kinda have > SMTP configured to deliver on localhost, and IMAP master is also a CARP > master), how do

Re: replication does not work

Hi Andrew, Am Freitag, den 21.02.2014, 11:21 -0800 schrieb Andrew Morgan: > On Fri, 21 Feb 2014, Marcus Schopen wrote: > > > Hi, > > > > Am Freitag, den 21.02.2014, 17:23 +0100 schrieb Willy Offermans: > > [...] > >> > >> > >> I can answer my own question. I was indeed missing the authentication

Re: replication does not work

On Fri, 21 Feb 2014, Marcus Schopen wrote: > Hi, > > Am Freitag, den 21.02.2014, 17:23 +0100 schrieb Willy Offermans: > [...] >> >> >> I can answer my own question. I was indeed missing the authentication >> mechanism. I added to imapd.conf on the >> back-end server and the replication worked. >>

Re: replication does not work

Hi, Am Freitag, den 21.02.2014, 17:23 +0100 schrieb Willy Offermans: [...] > > > I can answer my own question. I was indeed missing the authentication > mechanism. I added to imapd.conf on the > back-end server and the replication worked. > > So I wonder how I can tell sync_client which authen

Re: replication does not work

Dear cyrus friends, On Fri, Feb 21, 2014 at 03:48:20PM +0100, Willy Offermans wrote: > Dear cyrus friends, > > I like to use the replication feature of cyrus. > > On the backend I changed the cyrus.conf file. I added: > > to the SERVICES. > > On the client side I changed the imapd.conf file an

Re: replication deleting files on slave and sync_client -u

On Thu, Feb 20, 2014, at 10:03 AM, Marcus Schopen wrote: > Hi, > > just a understanding question: for some testing I connected via imap to > the slave an deleted some messages there. After that I started a > > /usr/lib/cyrus/bin/sync_client -u mailboxname > > on the master to sync master and s

Re: replication questions - best practice?

On Thu, Feb 20, 2014, at 03:01 AM, Marcus Schopen wrote: > I'm running a single standalone master and a replica slave. What is best > failover practice for this setup? How do I make a replication slave to > master if the standalone master is down? Just remove syncserver from > SERVICE section on sl

Re: Replication and INBOX rename in 2.4.12

Um, sorry, folks, I hit "send" before I had a look at the "To" header. This should have gone to our local list only. --Janne / Univ. of Helsinki On Thu, Aug 30, 2012 at 04:34:13PM +0300, Janne Peltonen wrote: > Tämä siis tiedoksi teillekin. Toki INBOX renamesta seuraavat jumitukset saa > jatkoss

Re: Replication and INBOX rename in 2.4.12

Tämä siis tiedoksi teillekin. Toki INBOX renamesta seuraavat jumitukset saa jatkossakin korjatuksi, seuraavaan USER-operaatioon asti... :( --Janne On Thu, Aug 30, 2012 at 04:33:18PM +0300, Janne Peltonen wrote: > On Wed, Jan 18, 2012 at 01:25:08PM +0200, Janne Peltonen wrote: > > On Wed, Jan 18,

Re: Replication and INBOX rename in 2.4.12

On Wed, Jan 18, 2012 at 01:25:08PM +0200, Janne Peltonen wrote: > On Wed, Jan 18, 2012 at 12:19:57PM +0200, Janne Peltonen wrote: > > What to do, how to circumvent this problem in the current version? I'd > > really > > like to be able to be able to start replicating a user's mailbox and > > meta

Re: replication features for remote server locations

On Wed, Feb 01, 2012 at 05:59:09PM +0100, Matteo Cazzador wrote: > Hello' i've a question about cyrus replication system, > i need to syncronize "real time" 3 imap servers (mailbox and > relative mail flags etc etc) in different geographic locations. > Every server have the same users. > Is it po

Re: Replication and deleted & really removed folders in Cyrus 2.4.12

Hi! On Thu, Jan 19, 2012 at 12:54:26PM +0100, Bron Gondwana wrote: > Yeah - ok. So the DELETED item is still in the mailboxes.db, but the files on > disk have been deleted. Can you send your imapd.conf(s) - and any syslog from > the time that the folders got deleted? > > I wonder if cyr_expire

Re: Replication and deleted & really removed folders in Cyrus 2.4.12

On Thu, Jan 19, 2012, at 11:09 AM, Janne Peltonen wrote: > Hi! > > Today, I ran into a totally new kind of trouble with replication. Apparently, > in some situation, when a user has some folders in the DELETED hieararchy, and > the folders get actually removed from the disk, and there is a USER

Re: Replication and deleted & really removed folders in Cyrus 2.4.12

On Thu, Jan 19, 2012 at 11:19:27AM +0200, Janne Peltonen wrote: > ...sorry, apparently, there is something even more weird going on. The mailbox > does not exist on the Murder frontend, but some traces of it appear to exist > on > the backend: > > i16.mappi.helsinki.fi> info "DELETED.user..BIOMED

Re: Replication and deleted & really removed folders in Cyrus 2.4.12

...sorry, apparently, there is something even more weird going on. The mailbox does not exist on the Murder frontend, but some traces of it appear to exist on the backend: i16.mappi.helsinki.fi> info "DELETED.user..BIOMEDICUM.Matkat 2012.06-20.Untitled Folder.4F17D602" {DELETED.user..BIOMEDICUM.M

Re: Replication and INBOX rename in 2.4.12

On Wed, Jan 18, 2012, at 10:52 AM, David Carter wrote: > On Wed, 18 Jan 2012, Janne Peltonen wrote: > > > I recently upgraded Cyrus from version 2.3.16 to 2.4.12 (using the > > wonderful RPMs from INVOCA). Now, I ran into a bit of a problem with > > replication. From time to time, a user think

Re: Replication and INBOX rename in 2.4.12

On Wed, Jan 18, 2012 at 12:19:57PM +0200, Janne Peltonen wrote: > What to do, how to circumvent this problem in the current version? I'd really > like to be able to be able to start replicating a user's mailbox and metadata > again, even if they have renamed their INBOX sometime in the past. Well,

Re: Replication and INBOX rename in 2.4.12

On Wed, 18 Jan 2012, Janne Peltonen wrote: > I recently upgraded Cyrus from version 2.3.16 to 2.4.12 (using the > wonderful RPMs from INVOCA). Now, I ran into a bit of a problem with > replication. From time to time, a user thinks it a great idea to rename > their INBOX in order to save time in

Re: Replication of delayed deletes/expunges

Hi, On 19 October 2011 17:38, Bron Gondwana wrote: > On Wed, Oct 19, 2011 at 04:58:35PM +0100, Guy wrote: >> I've just started playing around with Cyrus replication and I've got a >> set up with chained replication working nicely. I haven't tested >> delayed expunges yet, but delayed deletes don'

Re: Replication of delayed deletes/expunges

On Wed, Oct 19, 2011 at 04:58:35PM +0100, Guy wrote: > I've just started playing around with Cyrus replication and I've got a > set up with chained replication working nicely. I haven't tested > delayed expunges yet, but delayed deletes don't appear to work on the > replicas. The master server does

Re: Replication Log File !!

Quoting Shashi Yash : I'm trying to understand how replication works in cyrus. What kind of data is written to the replication log file etc. According to the documentation the sync log file is located in (configdirectory)/sync/log. But I'm unable to find this file. If you have started rollin

Re: Replication double check

On Fri, Jun 03, 2011 at 03:01:14PM -0500, Blake Hudson wrote: > Bron, I appreciate the info. I can certainly use this as a base. Though > I must admit that without a working example, I'm not able to quickly > modify the code and get it to run. > > Have you thought about making a generic version an

Re: Replication double check

ssage Subject: Re: Replication double check From: Bron Gondwana To: Blake Hudson Cc: info-cyrus@lists.andrew.cmu.edu Date: Friday, May 27, 2011 5:27:36 PM > On Fri, May 27, 2011 at 01:07:27PM -0500, Blake Hudson wrote: >> I'm looking to create a tool that will doubl

Re: Replication double check

On Fri, May 27, 2011 at 01:07:27PM -0500, Blake Hudson wrote: > I'm looking to create a tool that will double check replication, > backups, and migrations to ensure that they are working correctly and no > corruption has crept in. > > The tool MUST: > 1) Work via IMAP > 2) Compare a single

Re: replication catch up after stop

On Fri, Mar 11, 2011 at 05:20:47PM +, Oszkar Nagy wrote: > Hi Guys, > > I am kind a faceing the same issue. I have installed the master replica > set-up. But when I start up the sync-client on a master I get loots of > errors on a > > replica : > syncserver[1720]: [ID 532436 local6.error] I

Re: Replication from 2.3.16 to 2.4.6

On Fri, Feb 18, 2011 at 12:55:41PM +0100, Enrico Scholz wrote: > Hi, > > is the replication between a 2.3.16 master and a 2.4.6 slave supported? > Here, sync_client fails always with 'Error from send_lock(): bailing > out!'. Network trace shows > > | > LOCK > | < BAD IMAP_PROTOCOL_ERROR Unrecogn

Re: Replication & CONDSTORE [Documentation bug?]

On Tue, Feb 15, 2011 at 11:03:40AM -0500, Adam Tauno Williams wrote: > The page > states > > > Note that the replication protocol currently does not have the facility > to support the IMAP CONDSTORE extension (modification sequences).

Re: Replication and backups

On 03 Feb 2011, at 14:02, Patrick Goetz wrote: > On 02/03/2011 12:56 PM, Wesley Craig wrote: >> I wonder, tho, why use DRBD rather than cyrus replication. > > Perhaps because I don't know anything about cyrus replication? <:) > > RTFM the cyrus wiki? Oh, I think DRBD is a perfectly valid choice

Re: Replication and backups

On 02/03/2011 12:56 PM, Wesley Craig wrote: > I wonder, tho, why use DRBD rather than cyrus replication. > Perhaps because I don't know anything about cyrus replication? <:) RTFM the cyrus wiki? -- Patrick Goetz Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.

Re: Replication and backups

On 03 Feb 2011, at 13:45, Patrick Goetz wrote: > On further thought, it seems like this would be a solution: > > -- -- > | Server 1 | ---DRBD--> | Server 2 | > -- -- > > Step 1: Stop cyrus on Server 1. > Step 2: Turn off repli

Re: Replication and backups

On further thought, it seems like this would be a solution: -- -- | Server 1 | ---DRBD--> | Server 2 | -- -- Step 1: Stop cyrus on Server 1. Step 2: Turn off replication on Server 2. Step 3: Restart cyrus on Serve

RE: Replication errors in 2.3.16-8 (do_user bailing out)

I've re-run the replication tests using the same mailstore data on a Cyrus 2.3.7 (CentOS/RHEL package) replica pair and the same type of errors occurred. I then pulled another mailstore data from a Cyrus system in one of our QA environments (i.e. production, but non-customer data, as opposed to

Re: replication

Quoting Shuvam Misra : Quoting Bron Gondwana : > > It's getting better, but it's still not 100% reliable to have > master/master replication between two servers with interactions > going to both sides. > > It SHOULD be safe now to have a single master/master setup with > individual users on one

Re: replication

> Quoting Bron Gondwana : > > > > It's getting better, but it's still not 100% reliable to have > > master/master replication between two servers with interactions > > going to both sides. > > > > It SHOULD be safe now to have a single master/master setup with > > individual users on one side or th

Re: replication

On 11/12/2010 03:02 PM, Ron Vachiyer wrote: > Hello, > > I am currently investigating the possibility of adding a second cyrus > server, the goal being to entirely duplicate the mailspool/userbase and > have users POP in some sort of balanced means, either DNS load balancing > or otherwise. We have

Re: replication

Hello, Quoting Bron Gondwana : On Fri, Nov 12, 2010 at 02:02:01PM -0500, Ron Vachiyer wrote: Hello, I am currently investigating the possibility of adding a second cyrus server, the goal being to entirely duplicate the mailspool/userbase and have users POP in some sort of balanced m

Re: replication

On Fri, Nov 12, 2010 at 02:02:01PM -0500, Ron Vachiyer wrote: > > > > > Hello, > > I am currently investigating the possibility of adding a second cyrus server, > the goal being to entirely duplicate the mailspool/userbase and have users > POP in some sort of balanced means, either DNS load

Re: Replication question

On Tue, Oct 19, 2010 at 04:55:48PM -0400, Michael D. Sofka wrote: > I have a new 2.3.16 back-end server and a replication server. (For > those following my saga, I decided to upgrade the to-be-retired 2.2.12 > rsync backup server to 2.3.16. I did this so I could test replication. > Turns out t

Re: Replication sync-server and Delayed Delete

Actually, I was talking rubbish cyr_expire does find the deleted folders older than x days, I just got my dates wrong when looking into it. apologies, Gavin. On Thu, 16 Sep 2010, gavin.g...@ed.ac.uk wrote: > Hi there, > So is the side effect of deleted folders ending up on the default

Re: Replication sync-server and Delayed Delete

Hi there, So is the side effect of deleted folders ending up on the default partition when delayed delete is switched on on a replicant machine a known issue for sync_server? A knock on effect of this seems to be that cyr_expire on the replicant doesn't find these DELETED folders when it

Re: Replication sync-server and Delayed Delete

On Wed, Sep 15, 2010 at 12:29:18PM +0100, Gavin Gray wrote: > Hi there, > > We have a cyrus murder using replication and we have a few questions > about the behaviour we are seeing on our system. > > 1. cyr_expire on the master doesn't cause any replication to happen. > Is that 'correct'? In othe

Re: Replication rolling or cron?

Bron Gondwana wrote: > On Fri, Feb 20, 2009 at 10:21:38PM -0500, Wesley Craig wrote: >> On 20 Feb 2009, at 12:00, Shelley Waltz wrote: >>> I can get things working with a reboot, however, this is disruptive. >>> Question is - should I abandon rolling and just force a replication >>> via a >>> c

Re: Replication rolling or cron?

On Mon, Feb 23, 2009 at 09:43:08AM +, Ian Batten wrote: >> >> (at FastMail we start it from cyrus.conf, but also have a job that >> runs from cron and checks that there's a sync_client running every 10 >> minutes. > > It also works well with SMF if you're a Solaris site. > > $ svcs -x sync_clie

Re: Replication rolling or cron?

> > (at FastMail we start it from cyrus.conf, but also have a job that > runs from cron and checks that there's a sync_client running every 10 > minutes. It also works well with SMF if you're a Solaris site. $ svcs -x sync_client svc:/network/sync_client:default (?) State: online since Thu Feb

Re: Replication rolling or cron?

On Fri, Feb 20, 2009 at 10:21:38PM -0500, Wesley Craig wrote: > On 20 Feb 2009, at 12:00, Shelley Waltz wrote: > > I can get things working with a reboot, however, this is disruptive. > > Question is - should I abandon rolling and just force a replication > > via a > > cron job every 10 min? I h

Re: Replication rolling or cron?

On 20 Feb 2009, at 12:00, Shelley Waltz wrote: > I can get things working with a reboot, however, this is disruptive. > Question is - should I abandon rolling and just force a replication > via a > cron job every 10 min? I have low volume and only 200 accounts. > > Does anyone have a monitoring

Re: Replication errors: missing subscription

Hi It's posible to see your checkreplication script ??? I'm searching for valuable solution of checking the replication and there is no documented solution , how to verify "in sync" state and workaround for misstates ... Thanks Kleo On Tue, 2

Re: Replication verification

On Fri, 27 Jun 2008, David Carter wrote: > On Fri, 27 Jun 2008, Vladimir Klejch wrote: > >> I searchig for a posibility to use both server's in production as >> master-master. > > Afraid that replication in Cyrus doesn't support full master-master, only > master/slave. UIDs in IMAP make full ma

Re: Replication verification

On Fri, 27 Jun 2008, Vladimir Klejch wrote: > I searchig for a posibility to use both server's in production as > master-master. Afraid that replication in Cyrus doesn't support full master-master, only master/slave. UIDs in IMAP make full master-master rather involved. It is possible to run

Re: replication fails after 2.3.9 -> 2.3.11

Hi, Paul Dekkers wrote: > Simon Matter wrote: >>> Paul Dekkers wrote: >>> I finally found a moment for upgrading my 2.3.9 install (using Simon's RPMs on Red Hat 4.6, 64-bit) to 2.3.11-3 (leaving the config files untouched), after which it seems that replication isn't working properl

Re: replication fails after 2.3.9 -> 2.3.11

Hi, Simon Matter wrote: >> Paul Dekkers wrote: >> >>> I finally found a moment for upgrading my 2.3.9 install (using Simon's >>> RPMs on Red Hat 4.6, 64-bit) to 2.3.11-3 (leaving the config files >>> untouched), after which it seems that replication isn't working properly >>> anymore. >> While it

Re: replication fails after 2.3.9 -> 2.3.11

> Hi, > > Paul Dekkers wrote: > >> I finally found a moment for upgrading my 2.3.9 install (using Simon's >> RPMs on Red Hat 4.6, 64-bit) to 2.3.11-3 (leaving the config files >> untouched), after which it seems that replication isn't working properly >> anymore. > > While it seems to be only repli

Re: replication fails after 2.3.9 -> 2.3.11

Hi, Paul Dekkers wrote: > I finally found a moment for upgrading my 2.3.9 install (using Simon's > RPMs on Red Hat 4.6, 64-bit) to 2.3.11-3 (leaving the config files > untouched), after which it seems that replication isn't working properly > anymore. While it seems to be only replication for no

Re: Replication error

On Wed, Dec 05, 2007 at 11:34:10AM +, David Carter wrote: > RFC 3501, section 6.3.5: > >Renaming INBOX is permitted, and has special behavior. It moves >all messages in INBOX to a new mailbox with the given name, >leaving INBOX empty. If the server implementation supports >in

Re: Replication error

On Wed, 5 Dec 2007, Gabor Gombas wrote: > Hmm, can a regular user rename his own INBOX? I'm pretty sure no admin > actions were performed. RFC 3501, section 6.3.5: Renaming INBOX is permitted, and has special behavior. It moves all messages in INBOX to a new mailbox with the given name,

Re: Replication error

On Tue, Dec 04, 2007 at 10:06:23PM -0500, Wesley Craig wrote: > The internal Cyrus "mailbox ID" ought to be unique, but it's not. On the > sub folder, remove the cyrus.header file and reconstruct. This will assign > a new, unique mailbox ID. Thanks, that did the trick. > Any ideal how they e

  1   2   3   >