Cyrus IMAP Murder and (SUN)Solaris Cluster

somehow or another. 3. Some other solution we haven't thought of yet If anyone out there has though this kind of thing through or has experience of implementing Cyrus IMAP in a SUN Cluster environment, we'd love to hear from you, regards, Gavin. -- Gavin Gray Edinburgh University I

upgrading a 2.2.12 murder to 2.3.14

long to complete as the xfer. Does anyone have any experience of migrating to a replicating environment? many thanks, Gavin Gray -- Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (0)131 650 5987 email gavin.g...@ed.ac.uk -- The

Re: upgrading a 2.2.12 murder to 2.3.14

d we do an initial replication of all users by running sync_client manually with a list of users? -- Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (0)131 650 5987 email gavin.g...@ed.ac.uk -- The University of Edinburgh is a ch

Re: Synchronisation two cyrus-imapd servers

debug the problem, but had no success. Does anyone have any ideas? regards, Gavin Gray Quoting Alexander Demin : > Hello. > > I have problem with synchronisation two cyrus-imapd servers. > > *** Start "Replica" host configuration *** > OS: FreeBSD 7.2-STA

Re: Synchronisation two cyrus-imapd servers

mu.edu/show_bug.cgi?id=3170 > > Regards, > Stephan > > Original-Nachricht >> Datum: Thu, 08 Oct 2009 14:04:57 +0100 >> Von: Gavin Gray >> An: info-cyrus@lists.andrew.cmu.edu >> Betreff: Re: Synchronisation two cyrus-imapd servers >

intermittent problems with kick_mupdate

operation The error on the new backend receiving the error is: kick_mupdate: can't connect to target: No such file or directory the underlying OS of the new backend is openSolaris any thoughts? -- Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburg

Re: intermittent problems with kick_mupdate

user Quoting Gavin Gray : > Hi there, > > We are busy migrating lots of users to new backends in our cyrus > murder using xfer. > > The existing backends (and the rest of the murder) are cyrus 2.2 where > as the new backend machines are cyrus 2.3.15. > > Mostly everything wo

Re: intermittent problems with kick_mupdate

Yes, all that you're saying makes sense in terms of what we're experiencing, Quoting Wesley Craig : > On 03 Jun 2010, at 09:24, Gavin Gray wrote: >> imap[29289]: [ID 886451 local6.error] Could not trigger remote push to >> mupdate serverduring move of user... >

imapd dumping core due to SEGV

ffdbb0, 0x8047878), at 0x8062e9e [10] main(0x1, 0x8047e34, 0x8047e3c), at 0x8061fde Is there any known issues with 2.3.15? Also when this happens the cyrus master process kills all other active imapd processes and restarts, is there a reason for this? regards, Gavin Gray -- Gavin Gray Edi

Re: imapd dumping core due to SEGV

010 18:36:59 +0100, Wesley Craig wrote: > On 05 Jul 2010, at 10:56, Gavin Gray wrote: >> Two of them have had imapd processes crash and leave core dumps in >> the past couple of days. Looking at the core dumps with dbx we see > > I'm not aware of bug fixes in those code pa

Replication sync-server and Delayed Delete

licant as we would expect however the folder on the replicant goes into the DELETED heirarchy on a different partition(the default partition as specified in cyrus.conf). Is this normal? many thanks, Gavin Gray name : Cyrus IMAPD version: v2.3.15 2009/09/09 12:35:48 vendor :

Re: Replication sync-server and Delayed Delete

when it runs to do a purge. Could you suggest a safe alternative to cyr_expire in order to purge these misplace deleted folders? regards, Gavin Gray On Wed, 15 Sep 2010, Bron Gondwana wrote: > On Wed, Sep 15, 2010 at 12:29:18PM +0100, Gavin Gray wrote: >> Hi there, >> >&

Re: Replication sync-server and Delayed Delete

afe alternative to cyr_expire in order to purge these > misplace deleted folders? > > regards, > > Gavin Gray > > > On Wed, 15 Sep 2010, Bron Gondwana wrote: > >> On Wed, Sep 15, 2010 at 12:29:18PM +0100, Gavin Gray wrote: >>> Hi there, >>> >&g

lmtpd processes 'hanging'

3000 imapd processes per backend and normally deliver a few hundred messages per minute. We have three identical backend servers. One of them has become buisier in terms of active users ie larger mail store, larger deliverdb. We use berkley db for the cyrus databases. regards, Gavin Gray Edin

problem with xfer from 2.3.15 to 2.4.17

E UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE LISTEXT LIST-SUBSCRIBED X-NETSCAPE URLAUTH Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (0)13

xfer problems between 2.3.15 and 2.4.17

rks perfectly. does anyone have any ideas what could be causing this and if there might be a solution? many thanks, Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (0)131 650 5987 email gavin.g...@ed.ac.uk -- The University of Edinb

Re: xfer problems between 2.3.15 and 2.4.17

all the messages back to flaggged as new etc. We have tried various tests, but we can't discover the cause of the corruption of the cyrus.index files. regards, Gavin Gray On Wed, 7 May 2014, gavin.g...@ed.ac.uk wrote: > I have been testing xfer of accounts within a cyrus murder fro

Re: xfer problems between 2.3.15 and 2.4.17

he xfer process. Obviously there are some major changes from cyrus 2.3.15 to 2.4.17, but then mostly folders are migrated and 'upgraded' correctly. cheers, Gavin Gray On Thu, 15 May 2014, Ken Murchison wrote: > Hi Gavin, > > Have you tried running reconstruct with the -G and/or -R

Re: xfer problems between 2.3.15 and 2.4.17

ok to see if they can identify a problem and possibly find a solution then we would be very grateful. Gavin Gray On Thu, 15 May 2014, gavin.g...@ed.ac.uk wrote: Any help with this would be much appreciated. We keep coming across folders that once they have been migrated seem to have corrupt c

xfer problems between 2.3.15 and 2.4.17

, otherwise the config is identical to our 2.3.15 frontends. Is there any other config changes we should be aware of? any ideas greatly appreciated... Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (0)131 650 5987 email gavin.g...@e

Re: xfer problems between 2.3.15 and 2.4.17

7;t recall exactly when I upgraded our mupdate server, > but I don't think it matters.  I don't believe anything changed in > mupdate protocol or in the mailbox.db format between 2.3 and 2.4. > > Have you tried grabbing telemetry on the 2.4 server when the > subscription fails?  Is

Re: xfer problems between 2.3.15 and 2.4.17

entical to our 2.3.15 >> frontends. Is there any other config changes we should be aware of? > > I used the following when I upgraded from 2.3 to 2.4: > >   suppress_capabilities: ESEARCH LIST-EXTENDED QRESYNC WITHIN XLIST > ENABLE SORT=DISPLAY > > There was a thread I

Re: xfer problems between 2.3.15 and 2.4.17

gs from the mupdate master indicating when the various > folder state changes happen, when the various frontends receive that > information, etc. > > :wes > > Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (0)131 6

Re: xfer problems between 2.3.15 and 2.4.17

th this issue. On Sat, 7 Jun 2014, Wesley Craig wrote: > On 07 Jun 2014, at 14:49, Gavin Gray wrote: > > yes it looks like for some reason the mupdate procedure that happens > > within the murder upon folder creation is getting held up for some > > reason with regard to the

Re: xfer problems between 2.3.15 and 2.4.17

> folder state. It's one of the reasons we feel so in the dark with this > > issue. > > > > On Sat, 7 Jun 2014, Wesley Craig wrote: > > > > > On 07 Jun 2014, at 14:49, Gavin Gray wrote: > > > > yes it looks like for some reason the mupdate

Re: xfer problems between 2.3.15 and 2.4.17

on the frontends is > that when an expected mailbox isn't there, the frontend will specifically ask > the mupdate master about it using a kick_mupdate(). > > :wes > Gavin Gray Edinburgh University Information Services Rm 2013 JCMB Kings Buildings Edinburgh EH9 3JZ UK tel +44 (

Re: xfer problems between 2.3.15 and 2.4.17

oxes *or* the normal streaming of state > change events from the mupdate master to the frontends. Obviously, there can > be timing issues, but the typical paradigm implemented on the frontends is > that when an expected mailbox isn't there, the frontend will specifically ask > t

Re: xfer problems between 2.3.15 and 2.4.17

y user listed in this will be allowed to login for any >other user: use with >caution. In a standard murder this option should ONLY be set on >backends. DO NOT SET > on frontends or things won't work properly. > > Let us know if removing proxyserve

possible problems with deduplication database

: 24053 id: to: user. at: 1412075354 uid: 24055 these are quite isolated incidents, but surely this shouldn't happen at all? I suppose I'm asking if there are any known reasons why the deduplication process might behave in this way? We run cyr_expire -E 1 every night

deduplication issue

id: to: user. at: 1412075354 uid: 24055 these are quite isolated incidents, but surely this shouldn't happen at all? I suppose I'm asking if there are any known reasons why the deduplication process might behave in this way? We run cyr_expire -E 1 every night Gavin Gray Edinburgh Un

Re: delete and expunge delayed and delprune on replica?

guration option expunge_days: 7 affects cyr_expire I'd also like to know what the details of the difference between running cyr_expire with and without the -a option actually are. If anyone can helpt to clarify all this then i@m dure many would appreciate it, thanks, Gavin Gray On Thu