In the course of setting up delayed expunge on our production server I
came across the following;
- With delayed_expunge on the master, messages that are expunged by a
user will be retained -X days on the master but immideately deleted on
the replica unless it has delayed_expunge too.
So if I
the 32 bit code on the old
server is going to need to play nicely with the 64 bit code on the other
servers, both front-end and back-end. We'd also like to get replication
into the mix here at some point, and may have the same split.
Everything will be running the same code, but it will
Hi!
It appears that my sieve scripts that I have in the global namespace and
that are annotated to certain Cyrus bulletin boards don't get
replicated. Apparently, only user sieve scripts ever get replicated
(when something generates a USER replication event). How do I
(rollingly) replicat
Hi Guys:
A few days ago called for help about settings in Cyrus Aggregator.
Now I've a big problem with replica server.
My configuration is 1 backend, 1 murder, 1 frontend and 1 replica server.
When the backend server is online the replica server get all the mails
that reach the backend server.
On 02/28/2010 02:52 PM, Thomas Vogt wrote:
> Hi
>
> I've to move a large cyrus entity from one facility to another with no
> or at least a little downtime.
>
> I thought I setup a second cyrus entity on my new data center and use
> cyrus replication to transfer all da
Hi,
Quoting Thomas Vogt :
Hi
I've to move a large cyrus entity from one facility to another with no
or at least a little downtime.
I thought I setup a second cyrus entity on my new data center and use
cyrus replication to transfer all data to this new cyrus slave. After
all mails are c
unknown mailbox
user.xxaabb
Where the mailbox is actually on a different server. I assume that this is an
issue with replication and will go away when all servers are on 2.3.16?
I looked at mupdate.c and this is a debugging level message. So I could
change my logging levels and the message
On Mon, Aug 09, 2010 at 08:15:36PM +0400, Dmitry Ivanov wrote:
> Hello!
> Folks, looking through maillist history i saw that many of you are
> running cyrus in rolling replication mode. I am interested in
> configuring cyrus replica to use as a standby imap server, where we c
ns for Cyrus mailbox replication (I
> believe this feature has been added in v2.3)?
>
> Whatever pointers I am getting from Google are to the old Cyrus IMAP
> Website at cmu.edu -- these URLs no longer work.
>
> Is there a manpage that'll tell me details?
>
>
tion on features and
>> installation/configuration instructions for Cyrus mailbox replication (I
>> believe this feature has been added in v2.3)?
>>
>> Whatever pointers I am getting from Google are to the old Cyrus IMAP
>> Website at cmu.edu -- these URLs no longer
On Mon, Sep 13, 2010 at 08:59:01AM +0530, Shuvam Misra wrote:
> Dear all,
>
> One more question about sync-server and sync-client. Suppose I have two
> active servers, A and B, which contain completely disjoint sets of
> mailboxes. Can both replicate simultaneously to a replica server C? I
> will
> > One more question about sync-server and sync-client. Suppose I have two
> > active servers, A and B, which contain completely disjoint sets of
> > mailboxes. Can both replicate simultaneously to a replica server C? I
> > will run sync-server only on C, and sync-client on A and B, pointing them
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.
gt; 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 other words if we want to delete folde
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
#x27;m going to describe that
boggles my mind and I can't seem to find a clear-cut answer whether what
I'm up to is even supposed to work.
Using cyrus-imapd 2.4.10, built from jmeeuwen's SRPM aka kolabsys SRPM.
Here's the basic replication scenario I've implemented.
I ha
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
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,
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. F
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 ser
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
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,
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
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
use the replication.
but I can't authenticate on my replica server:
here is the error in the log:
sync_client[26757]: couldn't authenticate to backend server: no mechanism
available
here is the result of the synctest:
S: * OK mailsrv Cyrus sync server v2.3.0
Authentication
Patrice wrote:
Hi,
I try to install the the new version of cyrus-imap to use the replication.
but I can't authenticate on my replica server:
here is the error in the log:
sync_client[26757]: couldn't authenticate to backend server: no
mechanism available
here is the res
try to install the the new version of cyrus-imap to use the replication.
but I can't authenticate on my replica server:
here is the error in the log:
sync_client[26757]: couldn't authenticate to backend server: no mechanism
available
here is the result of the synctest:
S: * OK mai
TLSv1 with cipher AES256-SHA (256/256 bits)
S: * SASL PLAIN
S: * OK mailsrv Cyrus sync server v2.3.0
Please enter your password:
C: AUTHENTICATE PLAIN Y3lydYMAY3LydXMBZ3Q0M2RpMTM=
S: OK Success (tls protection)
Authenticated.
Security strength factor: 256
now I will try to validate the replication
E PLAIN Y3lydYMAY3LydXMBZ3Q0M2RpMTM=
> S: OK Success (tls protection)
> Authenticated.
> Security strength factor: 256
>
>
> now I will try to validate the replication with cyrus.
>
> Thank you very much for your great help !!
>
> Patrice
>
> Patrick H Radtke
the replication and it works well !
Simon Matter wrote:
I have created my self signed certificate and now it works !!
Where did you put and how did you specify the self signed certificate?
Thanks,
Simon
synctest -u cyrus -a cyrus -m PLAIN -t "" mailsrv
S: * STARTTLS
S:
yesterday evening my replication was working on my test system.
I unplugged network and came back today , plugged it again.
I tried to send an email but this one wasn't replicated on the
replica. (I waited a few minutes and my sync_repeat_interval is 60)
I made a "ps aux" and s
that lets us know if sync_client dies, and
attempts to restart it for us.
-Patrick
On Tue, 20 Dec 2005, Patrice wrote:
Hi,
yesterday evening my replication was working on my test system.
I unplugged network and came back today , plugged it again.
I tried to send an email but this one wasn
ok, I understand better now, thank you !
what would be the best way to restart it ?
stop/start cyrus or another command ?
thanks
Patrice
Patrick H Radtke wrote:
If sync_client cannot contact the replica server (or if there is
some other error that it can't recover from) then it &#
former03 | Baltasar Cevc wrote:
Hi everybody,
thanx to everybody who contributed for this great piece of server
software (and the nice support on the mailing list); explicitly thanx to
Ken for everything and David for the replication code!
Two questions, as I'm not able to jump int
Balthasar Cevc wrote:
1. Is it possible to have a server be master and client at the same
time - with the effect of being able to use 2 servers at the same time
for IMAP connections?
Hi Balthasar,
the setup at David Carter's site uses two machines: one acting as master for
half of the users,
Hi Ken, hi Wolfgang,
thanx for your quick answers!
Baltasar
_ former 03 gmbh
_ infanteriestraße 19 haus 6 eg
_ 80797 muenchen
_ [EMAIL PROTECTED]
_ www.former03.de
_ fon 0941.206.6952
_ fax 089.322112.11
_ mobil 0176.232.20.822
Cyrus Home Page: http://asg.w
[EMAIL PROTECTED] wrote:
Balthasar Cevc wrote:
1. Is it possible to have a server be master and client at the same
time - with the effect of being able to use 2 servers at the same time
for IMAP connections?
Not at the moment. David's code (and proxy) are fairly simple because
they don't
On Thu, 23 Mar 2006, Roland Pope wrote:
Hi all,
I am in the process of testing the new 2.3.3 Replication code and it has
highlighted an issue which seems to relate to how I have been recovering
people's mailboxes.
I occasionally get a call from a user 'xxx' saying they woul
On Thu, 23 Mar 2006, Roland Pope wrote:
When I try to replicate a user which has such a 'Recovered' mailbox, the
replication client bails out because it seems to treat the
'user.xxx.Recovered' mailbox as the user.xxx INBOX and trys to do a
rename (which fails).
It soun
Patrick T. Tsang wrote:
> Hello all,
>
> What are the conditions to trigger the replication in ver.2.3.3?
>
> My testing platform shows me that only the TOUCHED imap folder and
> TOUCHED email (imap flag: SEEN state will not!) will do.
It is true that rolling replicati
On Apr 12, 2006, at 9:22 AM, Ken Murchison wrote:
Patrick T. Tsang wrote:
Hello all,
What are the conditions to trigger the replication in ver.2.3.3?
My testing platform shows me that only the TOUCHED imap folder and
TOUCHED email (imap flag: SEEN state will not!) will do.
It is true that
Patrick Radtke wrote:
On Apr 12, 2006, at 9:22 AM, Ken Murchison wrote:
Patrick T. Tsang wrote:
Hello all,
What are the conditions to trigger the replication in ver.2.3.3?
My testing platform shows me that only the TOUCHED imap folder and
TOUCHED email (imap flag: SEEN state will not
On Fri, 28 Jul 2006, Pascal Gienger wrote:
sync_client seems to try to RENAME the Inbox to the subfolder "Uni"
which is complete nonsense.
Do the mailboxes have the same UniqueID (see cyrus.header files)? The
replication engine expects UniqueID to be unique. Cyrus makes a bit of
David Carter <[EMAIL PROTECTED]> wrote:
Do the mailboxes have the same UniqueID (see cyrus.header files)? The
replication engine expects UniqueID to be unique. Cyrus makes a bit of a
hash of renaming user inboxes (user.XXX -> user.XXX.Uni). Removing the
cyrus.header file and running re
On 28 Jul 2006, at 05:48, Pascal Gienger wrote:
David Carter <[EMAIL PROTECTED]> wrote:
Do the mailboxes have the same UniqueID (see cyrus.header files)? The
replication engine expects UniqueID to be unique. Cyrus makes a
bit of a
hash of renaming user inboxes (user.XXX -> use
Hi,
I'm setting up replaction with 2.4.7 and it seems to work (hurray!).
I was wondering if it is possible to set up a read only cyrus
imap(s)/pop/ instance?
In my replication setup I removed all the imap/lmtp/pop services from
this cyrus.conf file. Replication seems to be working.
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
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
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
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
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:
> >
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'
Good morning,
After we upgraded to Cyrus 3.0.8, we saw that some users in the replicas didn't
have some folders (or all) subscribed the same way they had in previous env in
Cyrus 2.3. Same happened for some users with Sieve scripts. It seemed the
content itself was perfectly copied. It was lik
Hello,
I set up replication between two cyrus servers (master runs 2.5.10 and
slave 3.0.8) with plans to decommission the old server once everything is
working. I noticed that the mail spool takes 950GB instead of ~300GB on the
old server. I suspected the hardlinks for message deduplication
ot it all working fine with postfix, cheerfully trundling along. now I
want to use replication to have a master/slave relationship going with
another server.
Looked at the website
http://cyrusimap.web.cmu.edu/imapd/install-replication.html
All looks fine, easy and not taking too much work.T
Robert Mueller wrote:
Hi Ken
There's a bug with replication and renaming INBOX -> INBOX.blah.
From http://www.ietf.org/rfc/rfc3501.txt:
Renaming INBOX is permitted, and has special behavior. It moves
all messages in INBOX to a new mailbox with the given name,
leavi
s that it affects SEEN state generally, not just
replication.
Would that be correct? I'm thinking SEEN is the only thing actually likely to
be
affected.
It's a bit of a pain to find all copies referring to it as well, unfortunately.
I can see the logic in making the uniqueid go wit
f this is that it affects SEEN state generally, not just
replication.
Would that be correct? I'm thinking SEEN is the only thing actually likely to
be
affected.
Yes, \Seen state can eventually get screwed .
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mel
Janne Peltonen wrote:
> On Tue, Jan 30, 2007 at 11:01:03AM +0100, Simon Matter wrote:
>>> This might be a problem, since we have some users that really have 1
>>> messages in their INBOX. Although it seems that Cyrus itself cannot cope
>>> with this either... in our current, non-clustering se
- "Janne Peltonen" <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 30, 2007 at 11:01:03AM +0100, Simon Matter wrote:
> > > This might be a problem, since we have some users that really have
> 1
> > > messages in their INBOX. Although it seems that Cyrus itself
> cannot cope
> > > with this either
On Tue, Jan 30, 2007 at 11:22:55AM -0500, Joel Nimety wrote:
> Janne Peltonen wrote:
> > On Tue, Jan 30, 2007 at 11:01:03AM +0100, Simon Matter wrote:
> >>> This might be a problem, since we have some users that really have 1
> >>> messages in their INBOX. Although it seems that Cyrus itself ca
On Tue, Jan 30, 2007 at 02:27:24PM -0800, Tom Samplonius wrote:
> It could be filesystem and kernel related. ext2/3 has historically
> not been good at this, but is better now. ufs is actually pretty
> good, but mainly because BSD kernels cache so much vnode data, it
> does not matter if
Hello.
There is a question about REPLICATION in Cyrus-IMAP.
At first, can I manage Cyrus-IMAP with MASTER-MASTER constitution
with two servers when I use REPLICATION?
I searched a document and ML, but think that I have you teach it
because only a method to manage as MASTER-SLAVE seems to be
Edward Prendergast wrote:
> Hi,
>
>
>
> Managed to solve the previous problem of errors like this:
>
> USER received NO response
>
> by changing the slave’s imapd.conf thusly:
>
> virtdomains: yes
>
> to
>
> virtdomains: userid
>
>
>
> So I can now transfer users as follows:
>
>
>
Edward Prendergast wrote:
> Thanks for your response Rudy.
>
> Is this bug merely causing a cosmetic error or will this stop my transfers
> from working?
Not really. The only drawback is that created mailboxes on the master
won't be on the replica. As soon as it receives email it will be adde
er's mailbox on the filesystem, but I think this may
be a feature of normal behaviour.
-Original Message-
From: Rudy Gevaert [mailto:[EMAIL PROTECTED]
Sent: 26 October 2007 12:08
To: Edward Prendergast
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: replication - correct way to transfer
On Sat, Nov 10, 2007 at 07:51:15PM -0800, Rich Wales wrote:
> I'm using replication on a 2.3.9 system.
>
> I know that if changes happen on the master system, they are propagated
> automatically to the replica system.
>
> But what happens if I make a change on the repli
sync to the other server.
(4) Both servers would be running sync_server.
So, I would have replication set up going both directions between my
two servers, but the sets of users handled in each direction would be
disjoint. Each user would be assigned to one IMAP server (the master
for their mailb
; user is listed in the sync_client command line of only one server.
>
> (3) Each server is configured (via the sync_... lines in imapd.conf)
> to sync to the other server.
>
> (4) Both servers would be running sync_server.
>
> So, I would have replication set up going bo
ilboxes on the command
> line. Does this define (and limit) the set of mailboxes that are
> replicated? If a mailbox is listed in the command line, are sub-
> mailboxes replicated too?
It doesn't work like that. Rolling replication gets events from
actions on mailboxes (lmtp delive
Bron Gondwana wrote:
> It doesn't work like that. Rolling replication gets events from
> actions on mailboxes (lmtp deliver, imapd updates, etc) and logs
> them - then the sync_client process running in the background
> reads that log file and uses the actions to know what thin
On Mon, 12 Nov 2007 09:37:12 -0800, "Rich Wales" <[EMAIL PROTECTED]> said:
> Bron Gondwana wrote:
>
> > It doesn't work like that. Rolling replication gets events from
> > actions on mailboxes (lmtp deliver, imapd updates, etc) and logs
> > them
Bron Gondwana wrote:
> [A mailbox list on the sync_client command line] works fine as a
> one-off, but not for rolling, because rolling reads the log.
Understood.
> That said, only users who have had any actions on that server will
> create log entries.
Interesting. This actually suggests that
On Sun, 11 Nov 2007, Rich Wales wrote:
> So, I would have replication set up going both directions between my two
> servers, but the sets of users handled in each direction would be
> disjoint. Each user would be assigned to one IMAP server (the master
> for their mailbox collecti
Per olof Ljungmark wrote:
> In the course of setting up delayed expunge on our production server I
> came across the following;
>
> - With delayed_expunge on the master, messages that are expunged by a
> user will be retained -X days on the master but immideately deleted on
> the replica unless
On Tue, Jul 29, 2008 at 12:16:01PM +0200, Rudy Gevaert wrote:
> Per olof Ljungmark wrote:
> > In the course of setting up delayed expunge on our production server I
> > came across the following;
> >
> > - With delayed_expunge on the master, messages that are expunged by a
> > user will be retai
Bron Gondwana wrote:
> On Tue, Jul 29, 2008 at 12:16:01PM +0200, Rudy Gevaert wrote:
>> Per olof Ljungmark wrote:
>>> In the course of setting up delayed expunge on our production server I
>>> came across the following;
>>>
>>> - With delayed_expunge on the master, messages that are expunged by a
On 29 Jul 2008, at 11:09, Per olof Ljungmark wrote:
> Thanks for the info. I can't help wonder if this was a firm design
> decision? From a user perspective it should be easier if this followed
> the synchronization I believe.
No, I don't think it's firm. There's been some discussion of how
del
On Tue, Jul 29, 2008 at 05:09:05PM +0200, Per olof Ljungmark wrote:
> Bron Gondwana wrote:
>> On Tue, Jul 29, 2008 at 12:16:01PM +0200, Rudy Gevaert wrote:
>>> Per olof Ljungmark wrote:
In the course of setting up delayed expunge on our production
server I came across the following;
Bron Gondwana wrote:
> On Tue, Jul 29, 2008 at 05:09:05PM +0200, Per olof Ljungmark wrote:
>> Bron Gondwana wrote:
>>> On Tue, Jul 29, 2008 at 12:16:01PM +0200, Rudy Gevaert wrote:
Per olof Ljungmark wrote:
> In the course of setting up delayed expunge on our production
> server I cam
generates a USER replication event). How do I
> (rollingly) replicate the sieve scripts in the global namespace?
>
> Thanks for any advice.
I'd like to ask again this question. Is it possible to replicate the
global sieve scripts? How?
(It would make sense to start taking backups from
I'm running Cyrus 2.3.16 (with replication) between two Ubuntu servers.
What do I have to do to make the "sync_client" application invoke STARTTLS
when it connects to "sync_server" on the other host?
I can invoke TLS when I use the "synctest" program, but I ca
On 28 Mar 2010, at 20:04, karen turner wrote:
> Mar 26 15:38:28 zysv01 mupdate[31564]: attempt to delete unknown
> mailbox
> user.xxaabb
>
> Where the mailbox is actually on a different server. I assume that
> this is an
> issue with replication and will go away wh
be missing something
simple or fundamental.
Thanks in advance,
John
When the problem occurs, sync_client gives a "do_client(u...@example.com):
bailing out!" error and logs a message about failing to reset the replication
(cyrusadmin) account. This occurs both when running sync_client ag
nc log files can be left around and never actually
processed. It's this second one that is more of a problem. We have a
program called "monitorsync" at FastMail that watches replication. Other
big sites do similar tricks.
I would love to replace monitorsync with better logic
eepalives, the sync_client can
> be stuck waiting "forever" for the replica.
Didn't have tcp_keepalive: 1. Will note if changes anything.
> The second is that sync log files can be left around and never actually
> processed. It's this second one that is more of a
12:52:39 imapsite-master syncserver[18209]: accepted connection
Jul 11 12:52:39 imapsite-master syncserver[18209]: cmdloop(): startup
Replication doesn't succeed, obviously.
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
9 imapsite-master syncserver[18209]: cmdloop(): startup
> Jul 11 12:51:39 imapsite-master syncserver[18209]: accepted connection
> Jul 11 12:51:39 imapsite-master syncserver[18209]: cmdloop(): startup
> Jul 11 12:52:39 imapsite-master syncserver[18209]: accepted connection
> Jul 11 12:52:39 imaps
ent).
The only difference between our master and replica configs these days
is that sync_client only gets started on the master. Actually, we
don't start it from cyrus.conf any more, we bring up the master first,
and then run sync_client from the init script after the master is
fully running.
>
As a quick reply I've attached the configs that I use for both hosts
and strace output for synctest run on B switched to master. Hopefully
this will either demonstrate that the configuration is pretty much
okay, or perhaps give you an idea of where I got the replication setup
wrong.
Mean
On Mon, Jul 11, 2011 at 3:47 PM, Bron Gondwana wrote:
>> Jul 11 11:21:14 imapsite-master syncserver[14019]: SSL_accept() timed
>> out -> fail
>> Jul 11 11:21:14 imapsite-master syncserver[14019]: STARTTLS failed:
>> imapsite-replica [10.10.0.188]
>
> Sounds like broken authentication.
>
>> ===
One more bit of information as a follow-up:
[root@imapsite-master scripts]# imtest -s -a zxy -m login -p imap -v localhost
starting TLS engine
setting up TLS connection
SSL_connect:before/connect initialization
write to 587EA850 [587F90B0] (89 bytes => 89 (0x59))
16 03 01 00 54 01 00
Disregard the previous message with imtest output. I completely forgot
that imaps wasn't running. It works fine, actually.
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Below is strace output for cyrus-master during manual sync_client invocation:
/usr/lib/cyrus-imapd/sync_client -v -r
[root@imapsite-master scripts]# netstat -ntuap |grep cyru
tcp0 0 0.0.0.0:143 0.0.0.0:*
LISTEN 29795/cyrus-master
tcp0 0 0.0.0.0
Agh, the problem solved, finally!
What caused this really weird behavior was something that is I'm not
even sure of, but what I did to fix it was basically took and
duplicated the master host, reconfigured it to be a replica and after
that I could sync and swap the roles as many times as I liked.
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 slave. This is the log on the master:
-
Feb 19 23:51:19 maste
Hi,
At our site I'm going to set up several cyrus servers to store all the
email for staff and students. We now have only one cyrus server for the
staff. In the near future we are going to several backends running
cyrus for staff and students.
I'm looking into replication.
vers could use their NNTP
daemons to provide fairly robust asynchronous replication for user
mailboxes. A poor man's replication engine if you will. Aside from the
geographic redundancy this could provide, it would be handy for users who
travel among many branch offices so their email access i
tures with security updates in the 'stable'
line is bad for your blood pressure.
If you're running replication on any post 2.3.3 cyrus, your replica
contains indexes with '0' as the modseq value. This means that your
messages will not be fetchable until you either
ing pair):
--- imapd-master.conf2014-11-24 13:37:45.752639666 -0600
+++ imapd-replica.conf 2014-11-24 13:31:58.702611566 -0600
@@ -1,22 +1,14 @@
##
-# These configuration parameters are for the master server
-# in a replication set
-servername: master.example.com
+#
501 - 600 of 730 matches
Mail list logo
