On 11/15/18 2:16 AM, Zorg wrote:
I ve one cyrus imap server I want to create a replicated one
I have read the documentation but nothing explain how two start the
first replication
If my slave master is empty how can i synchronise them the first time
Once you've got replication configured,
Hello
I ve one cyrus imap server I want to create a replicated one
I have read the documentation but nothing explain how two start the
first replication
If my slave master is empty how can i synchronise them the first time
Thanks
Cyrus Home Page: http://www.cyrusimap.org/
List Archive
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
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 this server was previously built with source RPMs, and the
upgrade was a b
A couple weeks back I asked about combining multiple stores into a
single one and someone recommended replication. So I started playing
around with it to populate a new store from an existing. This seems to
be working fine. I still have a little more testing to do though.
My question is about t
On Fri, Jun 15, 2007 at 08:56:53AM +0100, David Carter wrote:
> On Thu, 14 Jun 2007, Nels Lindquist wrote:
>
> > I'm setting up a high-availability mail server setup with two boxes that
> > will essentially be mirrors of each other.
> >
> > If both are configured for local delivery, can I have the
On Thu, 14 Jun 2007, Nels Lindquist wrote:
> I'm setting up a high-availability mail server setup with two boxes that
> will essentially be mirrors of each other.
>
> If both are configured for local delivery, can I have them replicate
> each other if I utilize UUIDs?
No. IMAP is not well suited
Hi, folks.
I'm setting up a high-availability mail server setup with two boxes that
will essentially be mirrors of each other.
If both are configured for local delivery, can I have them replicate
each other if I utilize UUIDs?
The idea would be to have identical copies of each mailbox on each
ma
On 14 Dec 2006, at 13:43, stas khromoy wrote:
i looked at the size of my imap/user folder on replica (1.9gb)
and size of the same folder on master (2.4gb)
First, I'd try to fix the "bailing out" problem you're having. Or,
if you want to just get things closer to correct, invoke:
sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thanks for all your help, wesley
i'll try this as soon as i can
there is one question that is till puzzling me thou
when it replicates, it ignores inactive folders
for some reason
i looked at the size of my imap/user folder on replica (1.9gb)
and s
On 14 Dec 2006, at 09:41, stas khromoy wrote:
i've noticed that for only one
of the users
i get the following error
Error from do_user(-l): bailing out!
in the list archives i found some one with a similar issue
(at least is sounded like it)
That's the error that you'd get from sync_client.
still battling with replication :)
i've noticed that for only one
of the users
i get the following error
Error from do_user(-l): bailing out!
in the list archives i found some one with a similar issue
(at least is sounded like it)
the advice was to to reconstruct the mailbox
but on which mac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
still battling with replication :)
i've noticed that for only one
of the users
i get the following error
Error from do_user(-l): bailing out!
in the list archives i found some one with a similar issue
(at least is sounded like it)
the advice was to
did as you advised
now i see folder fro all the users on replica machine
but the size of the /imap/users has not changed.
basically whatever is inactive
be it a full mailbox or an active mailbox's subfolder
is not being replicated.
Wesley Craig wrote:
> Like this:
>
> sync_client -l -v -u
Like this:
sync_client -l -v -u userA userB userC ...
Most Unix commands function this way.
:wes
On 12 Dec 2006, at 21:56, [EMAIL PROTECTED] wrote:
do thay have to be separated (user names i mean) by space or coma or
something else ??
Cyrus Home Page: http://cyrusimap.web.cmu.ed
do thay have to be separated (user names i mean) by space or coma or
something else ??
i am getting these
Dec 12 21:48:34 mars syncserver[313]: can not unlink
/var/imap/user/l/lenny,.seen: No such file or directory
Dec 12 21:48:34 mars syncserver[313]: can not unlink
/var/imap/user/l/lenny,.mboxke
On 12 Dec 2006, at 21:08, [EMAIL PROTECTED] wrote:
but why is it replicating only active mailboxes/subfolders ??
If you're enabling replication on an already in-production server,
you'll probably want to run something like:
sync_client -l -v -u
That will cause all existing mailbox
i did as you've said
this is now the output of synctest
S: * STARTTLS
S: * OK mars.edpausa.com Cyrus sync server v2.3.7
Authentication failed. generic failure
Security strength factor: 0
/var/log/messages shows :
Dec 12 20:56:21 mars syncserver[489]: login: [192.168.0.201] cyrus
PLAIN+TLS User
On Mon, Dec 11, 2006 at 04:36:38PM -0500, [EMAIL PROTECTED] wrote:
>
> another question :
>
> do i need to create mailboxes
> on the replica server or will they be created by the replication
> process ?
You don't need create mailboxes manually.
WBR
--
Dmitriy Kirhlarov
OILspace, 26 Leninskaya
On Mon, Dec 11, 2006 at 04:35:24PM -0500, [EMAIL PROTECTED] wrote:
>
> i started looking around
> for one i found that for whatever reason
> both sync and some other default process was using 2005/tcp port
> (in /etc/services )
> after taking care of that
>
> i kicked off on sync_client on master
i started looking around
for one i found that for whatever reason
both sync and some other default process was using 2005/tcp port
(in /etc/services )
after taking care of that
i kicked off on sync_client on master server
(after logging in as cyrus)
on master server i get
can not connect to serve
another question :
do i need to create mailboxes
on the replica server or will they be created by the replication
process ?
> while trying to setup cyrus replication
> i am getting the following error
> on the secondary server ( the one that is getting a copy of everything)
>
> Dec 9 12:35:34
while trying to setup cyrus replication
i am getting the following error
on the secondary server ( the one that is getting a copy of everything)
Dec 9 12:35:34 mars master[7701]: about to exec
/usr/local/cyrus/bin/sync_server
Dec 9 12:35:34 mars syncserver[7701]: executed
Dec 9 12:35:34 mars
On Thu, 13 Jul 2006, Robert Mueller wrote:
I think that should do it. There might be another option as well to make
this easier. From the top:
1. Server A is master (sync_client) replicating to Server B (sync_server)
2. Server A dies/is stopped
3. Restart Server B after adding this to the imap
Robert Mueller wrote:
> 1. Server A is master (sync_client) replicating to Server B (sync_server)
I'd like to add replication to my server as well. Is this replication
possible in Cyrus 2.2.13? Is this [1] what you are talking about (merged
into Cyrus 2.3 as stated in that page)? Or are you using
>Sent: Wednesday, July 12, 2006 5:59 PM
>To: former03 | Baltasar Cevc; Esh, Thomas D (Tom);
>info-cyrus@lists.andrew.cmu.edu
>Subject: Re: Cyrus 2.3.7 Replication Question
>
>
>> It won't. Cyrus currently only supports unidirectional replication.
>
>You can make i
Interesting. This process also implies you want to stop incoming mail
for a period of time to both servers. Sound right?
I would say the process for "failover" is:
1. Server A is master (sync_client) replicating to Server B (sync_server)
2. Server A dies/is stopped
3. All IMAP/POP/LMTP connec
Can you detail this A <-> B replication setup more? I've been trying to
figure out how to make use of the new 2.3.7 replication features outside
of a murder. The thing I can't wrap my head around is the following
situation:
1) Server A dies
2) Users are sent to Server B via DNS redirects
3)
Robert Mueller wrote:
1) Server A dies
2) Users are sent to Server B via DNS redirects
3) Server A is restored
4) Mailboxes on Server B are now more 'current' than mailboxes on
Server A
In other words, the failover is easy(ish) but the failback has me
scratching my head. I Think two way repli
Robert Mueller wrote:
You can make it work (we do), but you need 2 separate instances of
cyrus on each machine, which basically means 2 start/stop scripts, 2
different ports/ips for each service, 2 imapd.confs, 2 cyrus.confs,
and lots of -C command line params to everything so it uses the right
You can make it work (we do), but you need 2 separate instances of cyrus
on
each machine, which basically means 2 start/stop scripts, 2 different
ports/ips for each service, 2 imapd.confs, 2 cyrus.confs, and lots of -C
command line params to everything so it uses the right conf file.
to avoid a
On Thu, 2006-07-13 at 07:58 +1000, Robert Mueller wrote:
> > It won't. Cyrus currently only supports unidirectional replication.
>
> You can make it work (we do), but you need 2 separate instances of cyrus on
> each machine, which basically means 2 start/stop scripts, 2 different
> ports/ips for
It won't. Cyrus currently only supports unidirectional replication.
You can make it work (we do), but you need 2 separate instances of cyrus on
each machine, which basically means 2 start/stop scripts, 2 different
ports/ips for each service, 2 imapd.confs, 2 cyrus.confs, and lots of -C
comm
I would like to set up replication between two Cyrus servers A and B.
Server A will replicate to server B and Server B will replicate to
server A.
> [...]
Will this work in Cyrus 2.3.7?
It won't. Cyrus currently only supports unidirectional replication.
Baltasar
_ former 03 gmbh
_
Title: Cyrus 2.3.7 Replication Question
I would like to set up replication between two Cyrus servers A and B.
Server A will replicate to server B and Server B will replicate to server A.
For half of the subscribers we have the proxy point to server A, the other half of
the subscribers
> On Wed, May 17, 2006 at 03:40:17PM -0400, Patrick Radtke wrote:
>> when we switch we comment out the sync_server line on the replica to
>> make sure it won't listen.
>
> We have a "as master" config and an "as slave" config - and switch them
> via symlinks. Similar basic concept though - or at l
On Wed, May 17, 2006 at 03:40:17PM -0400, Patrick Radtke wrote:
> when we switch we comment out the sync_server line on the replica to
> make sure it won't listen.
We have a "as master" config and an "as slave" config - and switch them
via symlinks. Similar basic concept though - or at least it
when we switch we comment out the sync_server line on the replica to
make sure it won't listen.
When it comes to get the master up to speed, then we reverse the roles.
We also generate a file with all our usernames in it and feed it to
sync_client on the replica and that way it will go throu
One last question that I don't see answered on the 'net:
Say the master fails and we push all of our users to the replica, what
is the method to get the changes back from the replica to the master
once we are operational again? Simply reverse the roles? I'd imagine
that bringing the master
39 matches
Mail list logo
