On Sun, 10 Jun 2007, Rob Mueller wrote:
I can try and keep an eye on bailouts some more, and see if I can get
some more details. It would be nice if there was some more logging about
why the bail out code path was actually called!
It typically means that something deep in libimap has thrown
I suspect that the problem is with mailbox renames, which are not atomic
and can take some time to complete with very large mailboxes.
I think there's some other issues as well. For instance we still see
skiplist seen state databases get corrupted every now and then. It seems
certain
does the IMAP spec specify how large a UUID can be?
UUIDs aren't part of the IMAP spec. It's an addition to cyrus to help
replication. By default, there's no way to access UUIDs via IMAP at all
since they're not part of the IMAP spec.
The UUID size chosen was done by David Carter when he
On Sat, 9 Jun 2007, Rob Mueller wrote:
I run it directly, outside of master. That way when it crashes, it
can be easily restarted. I have a script that checks that it's
running, that the log file isn't too big, and that there are no log-
PID files that are too old. If anything like that
Michael Menge wrote:
Hi,
after the problem with the wiki was solved, i added a summery about
CyrusCluster
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster .
Could you, please, describe more detailed problems with replication:
CyrusReplication: ... The replication is asynchrony
Hi,
i havent used the replication my selfe, so the information is only based on
what i have read on this list.
The sync_client discovers all changes on the mailboxes queues them and send
them to the server. In case of a system crash ther might be changes
that are still queued and not send to
Michael Menge wrote:
Hi,
i havent used the replication my selfe, so the information is only
based on
what i have read on this list.
The sync_client discovers all changes on the mailboxes queues them and
send
them to the server. In case of a system crash ther might be changes
that are
Hi,
Dmitriy Kirhlarov wrote:
Michael Menge wrote:
after the problem with the wiki was solved, i added a summery about
CyrusCluster
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster .
Could you, please, describe more detailed problems with replication:
Dmitriy Kirhlarov wrote:
Michael Menge wrote:
i havent used the replication my selfe, so the information is only
based on
what i have read on this list.
The sync_client discovers all changes on the mailboxes queues them and
send
them to the server. In case of a system crash ther
On Jun 8, 2007, at 11:36 AM, Paul Dekkers wrote:
Dmitriy Kirhlarov wrote:
Which reminds me... isn't it strange that an unfinished logfile is
removed when the cyrus master (or was it the sync_client -r) is
restarted? Would make sense to me if the file is renamed / stored for
later running
Hi, list.
Nik Conwell wrote:
Do people run sync_client in the SERVICES section rather than START?
The install-replication docs indicate to put it in START. If my
replica goes away for a little while, sync_client exits and then I
have to restart it manually and then process any pending
On 08 Jun 2007, at 06:52, Paul Dekkers wrote:
* I'm still not fully using make_md5 myself. Still need to write a
script, that walks through the files, and only compares the messages
that are in both folders. If I run make_md5, it's never working on a
folder on both servers at the same time, so
I run it directly, outside of master. That way when it crashes, it
can be easily restarted. I have a script that checks that it's
running, that the log file isn't too big, and that there are no log-
PID files that are too old. If anything like that happens, it pages
someone.
:wes
On 08
I don't have something to consume make_md5 data, yet, either. My
plan is to note the difference between the replica and the primary.
On a subsequent run, if those differences aren't gone, then they
would be included in a report.
Rather than make_md5, check the MD5 UUIDs patch below. Using
I run it directly, outside of master. That way when it crashes, it
can be easily restarted. I have a script that checks that it's
running, that the log file isn't too big, and that there are no log-
PID files that are too old. If anything like that happens, it pages
someone.
Ditto, we do
On Sat, 9 Jun 2007, Rob Mueller wrote:
So - added is a new option uuidmode in imapd.conf. Set it to md5 and you
will get UUIDs of the form: 02(first 11 bytes of the MD5 value for the
message) which takes up the same space, but allows pretty good integrity
checking.
Is it safe? - we
Hi,
after the problem with the wiki was solved, i added a summery about
CyrusCluster http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster .
Please feel free to add infos about your experience with NFS
Quoting Paul Dekkers [EMAIL PROTECTED]:
Hi,
Took me a while before I found the
Hi,
Michael Menge wrote:
after the problem with the wiki was solved, i added a summery about
CyrusCluster
http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/CyrusCluster .
Please feel free to add infos about your experience with NFS
Good suggestion. I will do some more testing, for now: I did
Hi,
Took me a while before I found the time to try the meta-partitions and
NFS backed (data-)partitions, but:
Dmitriy Kirhlarov wrote:
On Thu, May 03, 2007 at 05:08:52PM +0200, Paul Dekkers wrote:
I recently tried to use NFS (on a RedHat client, both to a NetApp filer
as well as a RedHat
On Thu, May 03, 2007 at 05:08:52PM +0200, Paul Dekkers wrote:
I recently tried to use NFS (on a RedHat client, both to a NetApp filer
as well as a RedHat NFS server) and I'll share my experiences:
Michael Menge wrote:
Cyrus has 2 problems with NFS.
1. Cyrus depends on filesystem
I testing cyrus with a NFS storage by two *identical* cyrus + postfix
servers
Both /var/spool/imap and /var/imap are mounted by both servers ( the
socket directory is moved out of the mount)
Everything seems working fine but I find sometimes dupelim doesnt work.
I tried to debug , I get
Hi,
Cyrus has 2 problems with NFS.
1. Cyrus depends on filesystem locking. NFS-4 should have solved this problem
but i have not tested it.
2. BerkleyDB uses shared Memory which does not work accros multiple servers.
You can try to convert all your databases to skipplist and run with
NFS-4
22 matches
Mail list logo
