Thanks. I figured if the single instance, bi-directional
replication didn't work, the two cyrus instances would
be the fallback position. It's good to hear that someone
else has it working.
Tom
>-Original Message-
>From: Robert Mueller [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, J
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
Ken Murchison schrieb:
> André Böhm wrote:
>> Hello,
>>
>> after upgrading from 2.2.13 to 2.3.7, I have a very worrying problem
>> with lmtp.
>>
>> When procmail tries to deliver mail via the "deliver" command, with
>> the "-a" option I get "master[96435]: process 99783 exited, signaled
>> to death
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
Unix systems should be run in GMT/UTC (almost the
same thing; GMT is _not_ British time").
You then use $TZ in the environment, or some OS-dependent
way of setting 'localtime' (eg, a symlink /etc/localtime,
or some other method) to let programs show the time in
the local zone. That's normally
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
André Böhm wrote:
Hello,
after upgrading from 2.2.13 to 2.3.7, I have a very worrying problem
with lmtp.
When procmail tries to deliver mail via the "deliver" command, with the
"-a" option I get "master[96435]: process 99783 exited, signaled to
death by 11".
This is only on murder master
Hello,
after upgrading from 2.2.13 to 2.3.7, I have a very worrying problem
with lmtp.
When procmail tries to deliver mail via the "deliver" command, with the
"-a" option I get "master[96435]: process 99783 exited, signaled to
death by 11".
This is only on murder master and murder frontend
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 poin
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:info-cyrus-
...
>
> On 12 Jul 2006, at 11:01, Rosenbaum, Larry M. wrote:
> > Would it be possible to eliminate the following compiler warnings?
> >
> > In file included from imapd.c:75:
> > imap_err.h:67: warning: "struct et_list" de
Gabor Gombas wrote:
>> Program terminated with signal 10, Bus error.
>> #0 0x000100011e04 in mailbox_write_index_header
>> (mailbox=0x7fff3f70) at mailbox.c:1319
>> 1319*((bit64 *)(buf+OFFSET_HIGHESTMODSEQ_64)) =
>> htonll(mailbox->highestmodseq);
>
> Could you do a "p &buf"
On Wed, 2006-07-12 at 11:48 -0400, Jason Englander wrote:
> Anyone know of a perl module or php function that will let the cyrus
> administrator-user subscribe a mailbox for a user without
> authenticating as that user and without using autocreate?
well, the Mail::IMAPClient module for Perl has
On Wednesday 12 July 2006 09:48, Jason Englander wrote:
> Anyone know of a perl module or php function that will let the cyrus
> administrator-user subscribe a mailbox for a user without
> authenticating as that user and without using autocreate?
The cyradm tool and something like expect should be
On 12 Jul 2006, at 11:01, Rosenbaum, Larry M. wrote:
Would it be possible to eliminate the following compiler warnings?
In file included from imapd.c:75:
imap_err.h:67: warning: "struct et_list" declared inside parameter
list
imap_err.h:67: warning: its scope is only this definition or
decla
Anyone know of a perl module or php function that will let the cyrus
administrator-user subscribe a mailbox for a user without
authenticating as that user and without using autocreate?
Would I break anything by modifying
/var/imap/user/X/joeschmo/joeschmo.sub?
The user would definitely not be
On Tuesday 11 July 2006 11:32, Jim John wrote:
> Thereis only 3 files in /etc/ssl/private
I would check your permissions. On Debian, that directory is 660 with
root:ssl-cert ownership. Maybe you could an ACL if I want other users to be
able to look in there like the following:
setfacl -m u:cyr
Would it be possible to eliminate the following
compiler warnings?
In file included from imapd.c:75:
imap_err.h:67: warning: "struct et_list"
declared inside parameter list
imap_err.h:67: warning: its scope is only this
definition or declaration, which is probably not what you want
you probably want to use '-d' instead of '&' to make master run in
the background.
After that you can look in log files for cyrus. The location of the
log file depends on your syslog.conf ( I think wherever local6.*
points to).
Any problems should be reported there.
On Jul 12, 2006, at 8
On Wed, Jul 12, 2006 at 05:02:10PM +0400, Дейтер Александр Валериевич wrote:
> Core was generated by
> `/home/devel/build/cyrus-imapd-2.3.7/imap/reconstruct -rf user.devel'.
> Program terminated with signal 10, Bus error.
> #0 0x000100011e04 in mailbox_write_index_header
> (mailbox=0x
(I posted this before with an incorrect subject line).
I'm having problems starting and connecting to imapd.
I type:
sudo /usr/cyrus/bin/master &
The following line gets returned to the screen:
[1] 190
Looking at the processes running with 'top' there is a process 'sudo'
with PID of 190 ru
Ken Murchison wtote:
>> I have removed #define HAVE_LONG_LONG_INT in config.h:
>>
>> --- cyrus-imapd-2.3.7/config.h.origWed Jul 12 13:54:00 2006
>> +++ cyrus-imapd-2.3.7/config.hWed Jul 12 11:24:17 2006
>> @@ -158,7 +158,7 @@
>> #define HAVE_LONG_FILE_NAMES 1
>>
>> /* Does the comp
Rosenbaum, Larry M. wrote:
After much experimenting, I decided there was something wrong with my
databases, especially since dropping back to v2.3.3 didn't fix it. So I
wiped everything out (fortunately it's a test system), recreated the
mailboxes and put messages in them, repeated the experimen
Hello,
I have seen that the folder sync. on my replica contains more than 1Go
of files.
can I delete all the content of it or I must keep the current day with
its cache file ?
I can do it with or without the replica stopped ?
I use the cyrus-imap 2.3.1
thanks in advance
Patrice
Cyr
After much experimenting, I decided there was something wrong with my
databases, especially since dropping back to v2.3.3 didn't fix it. So I
wiped everything out (fortunately it's a test system), recreated the
mailboxes and put messages in them, repeated the experiment with v2.3.3,
and everything
Дейтер Александр Валериевич wrote:
Ken Murchison wrote:
I am pleased to announce the release of Cyrus IMAPd 2.3.7. This release
should be considered late beta quality, reflecting that most large bugs
have been resolved, but some small buglets might still remain.
This release fixes problems wi
[EMAIL PROTECTED] wrote:
The director is going mad , because the staff are saying that they did
not delete the emails, so therefore it must be the software or the
hardware problem right?
I have checked the system , and neither the disk of the file system is
failing, nor is there any errors in
Ken Murchison wrote:
>>> I am pleased to announce the release of Cyrus IMAPd 2.3.7. This release
>>> should be considered late beta quality, reflecting that most large bugs
>>> have been resolved, but some small buglets might still remain.
>>> This release fixes problems with replication and vi
Hi ,
I currently have 2 email systems which utilize exactly the same
versions of Cyrus
which i currently have as 2.2.3, the systems are running on SLES9 in
2 different offices.
thru put is not that high, possibly several hundred emails a day &
user base is about 15 people. (small office
33 matches
Mail list logo
