Le 28 sept. 2010 à 08:50, Tomasz Chmielewski a écrit :
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: Program version
4.2 doesn't match environment version
Are you sure on each node the _SAME_ Cyrus version linked to the _SAME_ bdb
libs is running?
And - just a little side
On Monday 27 September 2010 17:30:01 Mark Nipper wrote:
On 27 Sep 2010, J. Roeleveld wrote:
I wasn't able to find a specific howto for this during a brief
Google-search.
I recalled that the Debian package for Cyrus had some
decent instructions on this. You can see them at:
---
--On 28. September 2010 08:50:00 +0200 Tomasz Chmielewski man...@wpkg.org
wrote:
How do you manage your Cyrus installations highly-available?
Check the archives. There have been many discussions regarding this.
I though a minimal example could be like below:
internet
|
On 28.09.2010 09:13, Pascal Gienger wrote:
Le 28 sept. 2010 à 08:50, Tomasz Chmielewski a écrit :
Sep 28 01:10:10 omega cyrus/ctl_cyrusdb[21728]: DBERROR db4: Program version
4.2 doesn't match environment version
Are you sure on each node the _SAME_ Cyrus version linked to the _SAME_ bdb
Hi,
reject8bit is no :
reject8bit: no
rfc_ignore_8bit: yes
munge_8bit: no
I've checked that when I got the error, no progress :-/
Thanks for tips.
J.K.
Cituji Patrick Goetz pgo...@mail.utexas.edu:
On 09/27/2010 05:39 AM, Josef Karliak wrote:
What is going on ? On cyrus 2.2.12
Quoting Tomasz Chmielewski man...@wpkg.org:
How do you manage your Cyrus installations highly-available?
I though a minimal example could be like below:
internet
|
server1 - server2
There would be Heartbeat/Pacemaker running on both servers. Its role
would be:
-
On 28.09.2010 10:56, Michael Menge wrote:
Cyrus depends on locks and mmap, so your fs must support them.
I had written a summery of the diskussions about Cyrus and HA in the
old wiki. But the wiki was replaced by the new wiki. I will have a look
if I have a copy.
I would be grateful.
If
Quoting Tomasz Chmielewski man...@wpkg.org:
On 28.09.2010 10:56, Michael Menge wrote:
Cyrus depends on locks and mmap, so your fs must support them.
I had written a summery of the diskussions about Cyrus and HA in the
old wiki. But the wiki was replaced by the new wiki. I will have a look
if
On 28.09.2010 11:55, Michael Menge wrote:
Replication was introduced in 2.3.x. There are other features in 2.3.x
I don't want to live with out (e.g. delayed expunge). There was a
diskussion on the lists about that Debian wants to upgrade cyrus.
The main problem is the upgrade path (update of
On Tue, Sep 28, 2010 at 12:13:14PM +0200, Tomasz Chmielewski wrote:
On 28.09.2010 11:55, Michael Menge wrote:
Replication was introduced in 2.3.x. There are other features in 2.3.x
I don't want to live with out (e.g. delayed expunge). There was a
diskussion on the lists about that Debian
On Mon, Sep 27, 2010 at 09:38:08AM -0400, Jeff Eaton wrote:
Better to just use an internal DB codebase (like skiplists) that has
nothing to do with Sleepycat. But then someone has to write and maintain
this code.
I think the best compromise I've heard yet is to use something like
Hi,
reject8bit is no :
reject8bit: no
I think the following option is not a standard Cyrus option:
rfc_ignore_8bit: yes
and this one is wrong, in standard Cyrus it's called munge8bit:
munge_8bit: no
You may check if they really have this name and if your Cyrus version is
patched
On Monday 27 September 2010 17:30:01 Mark Nipper wrote:
On 27 Sep 2010, J. Roeleveld wrote:
I wasn't able to find a specific howto for this during a brief
Google-search.
I recalled that the Debian package for Cyrus had some
decent instructions on this. You can see them at:
---
Still, we need to have Cyrus database, mail storage accessible for
both servers. I though using glusterfs for it would be a good idea
(assuming Cyrus only runs on one of the servers at a given time).
IMO, don't use glusterfs for this. I found it to not even be sufficient
for a PHP session
On Mon, Sep 27, 2010 at 09:38:08AM -0400, Jeff Eaton wrote:
Better to just use an internal DB codebase (like skiplists) that has
nothing to do with Sleepycat. But then someone has to write and
maintain
this code.
I think the best compromise I've heard yet is to use something like
On 28.09.2010 15:01, John Madden wrote:
Still, we need to have Cyrus database, mail storage accessible for
both servers. I though using glusterfs for it would be a good idea
(assuming Cyrus only runs on one of the servers at a given time).
IMO, don't use glusterfs for this. I found it to not
Any other suggestions? There is an alternatives like Ceph[1], but it is
just too new (and potentially can have some edge cases).
DRBD + GFS/OCFS2 just seem too complex for such setup.
If you're doing failover, you don't need a cluster filesystem. You can
use just plain DRDB+ext4 if you
Quoting Tomasz Chmielewski man...@wpkg.org:
On 28.09.2010 15:01, John Madden wrote:
Still, we need to have Cyrus database, mail storage accessible for
both servers. I though using glusterfs for it would be a good idea
(assuming Cyrus only runs on one of the servers at a given time).
IMO,
Am Dienstag 28 September 2010, 13:09:02 schrieb Simon Matter:
Hi,
reject8bit is no :
reject8bit: no
I think the following option is not a standard Cyrus option:
rfc_ignore_8bit: yes
and this one is wrong, in standard Cyrus it's called munge8bit:
munge_8bit: no
You may
Yes,
I see, where did I got that ??? Nor cyrus didn't complain for unknown
config options ...
Thanks for kick :)
J.K.
Cituji Ralf Haferkamp rha...@suse.de:
Am Dienstag 28 September 2010, 13:09:02 schrieb Simon Matter:
Hi,
reject8bit is no :
reject8bit: no
I think the
Hello
AFAIK, cyrus needs posix file locks and mmap support.
GlusterFS needs FUSE and it only supports writable mmap files after kernel
2.6.26 or so.
Therefore, you need recent kernel and recent fuse.
Further, you need to extremely fine tune your configuration, as the most robust
clustered
On 28 Sep 2010, Simon Matter wrote:
Are these Debian specific? Or is there something missing from my
installation?
Or do these only exist when Cyrus is not running? (Which I would find
strange)
I don't know the Debian packages but I'm quite sure it's Debian specific.
Looks like their
On Tue, Sep 28, 2010 at 05:47:35PM +0200, Josef Karliak wrote:
Yes,
I see, where did I got that ??? Nor cyrus didn't complain for
unknown config options ...
Thanks for kick :)
J.K.
Yeah, Cyrus doesn't complain about unknown options for a couple
of reasons:
a) because you can prefix any
Bron Gondwana wrote:
On Tue, Sep 28, 2010 at 05:47:35PM +0200, Josef Karliak wrote:
Yes,
I see, where did I got that ??? Nor cyrus didn't complain for
unknown config options ...
Thanks for kick :)
J.K.
Yeah, Cyrus doesn't complain about unknown options for a couple
of reasons:
a)
Hey Rob - got another little Cyrus job if we run out of work for the
new people :)
3) cyr_config tool. It needs at least the following capabilities:
a) a mode which dumps ALL configuration options, either set by you or
the default
b) a mode which dumps only the options which are non-default
On Tue, Sep 28, 2010 at 05:47:35PM +0200, Josef Karliak wrote:
Yes,
I see, where did I got that ??? Nor cyrus didn't complain for
unknown config options ...
Thanks for kick :)
J.K.
Yeah, Cyrus doesn't complain about unknown options for a couple
of reasons:
a) because you can prefix
On 28 Sep 2010, at 18:04, Simon Matter wrote:
While we are at it, I know about this prefixing but is it documented
somewhere? I just checked the imapd.conf man page but couldn't find it
there.
There's a bugzilla or two related to the lack of documentation of the prefixing.
:wes
Cyrus
On 28.09.2010 12:55, Bron Gondwana wrote:
On Tue, Sep 28, 2010 at 12:13:14PM +0200, Tomasz Chmielewski wrote:
On 28.09.2010 11:55, Michael Menge wrote:
Replication was introduced in 2.3.x. There are other features in 2.3.x
I don't want to live with out (e.g. delayed expunge). There was a
Hello!
Is it safe to relocate mailboxes from one partition or backend (in case
of murder) to another while listening to lmtp or lmtp proxy? Is there a
chance that relocation can fail or e-mail messages can be lost?
--
Dmitry S. Ivanov
ICQ: 52537478
Visual Trading Systems, LLC
29 matches
Mail list logo
