Re: Replicate to more than one replica?

On 06 Jun 2006, at 16:04, David Korpiewski wrote: When we bring the master back up we make sure cyrus is turned off. Then we do a full mailstore diff on the original master and the silent replica. This will give us a list of the email that was not propagated when the master went down. Thi

Re: Replicate to more than one replica?

On 07 Jun 2006, at 15:10, David Korpiewski wrote: I am unable to apply the left behind transaction logs of the sync_client. Perhaps I'm just not sure how to do it. You ought to be able to do it with sync_client -r -f /path/to/log. My main concern is what applying these left overs to the ru

Re: Does anyone else see skiplist recovery errors?

On 15 Jun 2006, at 01:23, Robert Mueller wrote: I'm trying to find out if anyone else sees intermittent skiplist recovery problems as sometimes we do, usually after a cyrus restart. ... So I was hoping people who also see this could report their cyrus version and OS + hardware config. We'

Re: defeated about Murder.....

We have patches to lmtpproxyd to refer to the local mailboxes.db, which greatly improves performance. :wes On 18 Jun 2006, at 09:18, [EMAIL PROTECTED] wrote: You have lmtpproxyd set up to query the murder master server for each message that comes in. You're options are to 1. Have lmtpproxyd

Re: defeated about Murder.....

On 18 Jun 2006, at 16:07, Andrzej Kwiatkowski wrote: could you send Your patch, please ? Sure. Look here: http://cvs.itd.umich.edu/cgi-bin/cvsweb.cgi/lfs/cyrus-imap23/ lmtpproxyd.diff?rev=1.1 These are actually against Cyrus IMAP 2.2.x, tho I'm in the process of moving them forward to 2

Re: defeated about Murder.....

On 18 Jun 2006, at 16:45, Andrzej Kwiatkowski wrote: Could you write for what are the others patches ? There are a couple of bug fixes. Several are additional logging, particularly of message delivery and message deletion. These two are serious improvements: http://cvs.itd.umich.edu/cgi

Re: defeated about Murder.....

On 19 Jun 2006, at 15:31, Ken Murchison wrote: Ah, right. This has been fixed in CVS for a while. The two obvious references to anonymous CVS for Cyrus seem to be dead links: http://cyrusimap.web.cmu.edu/anoncvs.html https://asg.web.cmu.edu/cyrus/download/anoncvs.html Also

Re: How to backup cyrus-imapd without stopping service

On 22 Jun 2006, at 23:53, Daniel O'Connor wrote: On Friday 23 June 2006 12:17, Seiichirou Hiraoka wrote: So I want to know the better (or recommend) way to backup Cyrus-IMAPD /var/imap files to other host without stop service. AFAIK the only way to do it properly is to use snapshots on the f

Re: How to backup cyrus-imapd without stopping service

On 23 Jun 2006, at 20:58, Seiichirou Hiraoka wrote: How about to use rsync and reconstruct (on backup) without using snapshot? Depending on how tolerant you are of inconsistency between the contents of /var/spool/imap and /var/imap, that will work. :wes Cyrus Home Page: http://asg.web.

Re: Master and frontend database sync problem

What SASL version are you using? :wes On 29 Jun 2006, at 04:17, Snezhana Bekova wrote: We have 3 backends with Cyrus 2.2.13, 1 MTA with Postfix and Cyrus Frontend 2.2.13, and 1 Cyrus Master Mupdate with 2.2.13. The frontend database is not always synchronizing when mupdate database change

Re: Mailstore filesystem

On 03 Jul 2006, at 11:35, Daniel Eckl wrote: At this time I didn't change the scheduler. In fact, I actually learned about it a few days ago... So it was SuSE 9.3 default (might be vanilla default, don't know) I think "anticipatory" is the default IO scheduler for SuSE 9.3 (from Google).

Re: Mailstore filesystem

On 03 Jul 2006, at 12:11, Daniel Eckl wrote: I cannot identify the triggering client and/or the action it starts I have a set of patches to 2.2.x that adds per-user CPU logging. I'm busying porting them forward to 2.3.x as we speak. Sadly, Linux doesn't support getrusage(2) of more i

Re: Mailstore filesystem

On 05 Jul 2006, at 10:07, John Madden wrote: True, but I do expect to reach this number on this machine in the next couple of years. ...And reiserfs has been just fine so far. Then again, I didn't even consider using ext3 at the time. While I've not had performance problems with reiser3, I ha

Re: Mapping users (either KerberosV or TLS certs)

On 05 Jul 2006, at 20:02, Phil Pennock wrote: can anyone please explain how to configure Cyrus so that a KerberosV /admin principal can be treated as a Cyrus admin user? I've tried inserting various entries into sasldb to back this up, putting things into /etc/krb5.equiv as well as various value

Re: Replication is broken with modseq issue in 2.3.6

I was tracking a very similar issue with xfer between 2.2 and 2.3.6. xfer'ing vanilla 2.2.12 mailboxes to 2.3.6 seems to work fine, and xfer'ing a 2.3.6 mailbox to 2.2.12 also more or less works (permissions are broken since 2.3.6 blindly uses rfc 4314 ACLs rather than paying attention to

Re: Replication is broken with modseq issue in 2.3.6

Looks like that changes the replication protocol incompatibly, so deployments need to update both replicas and primaries at the same time. :wes On 06 Jul 2006, at 17:17, David S. Madole wrote: I submitted a patch that does actually replicate the modseq value, although unfortunately my first e

Re: "struct et_list" declared inside parameter list - possible cleanup?

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

Re: 2.3.7 replication - sync mail (#2)

On 17 Jul 2006, at 01:28, Patrick T. Tsang wrote: Will I have to sync (ie. imapsync) all the mails from the client to the replica at the first run? Is there any way to "replicate" (NOT sync) actively all the emails to the newly added replica? On the primary, run sync_client -u with a list of

Re: Good book on Cyrus?

On 17 Jul 2006, at 09:59, Forrest Aldrich wrote: Short answer, there are no good books. Managing IMAP is minimally useful - in a basic sense. The one salient chapter happens to be online: http://www.oreilly.com/catalog/mimap/chapter/ch09.html if that helps. However, I contacted O'

Re: Cyrus IMAPd 2.3.7 Released

On 18 Jul 2006, at 09:34, Ken Murchison wrote: If a version of the autocreate patch is posted that works in all modes (altnamespace, unixhierarchysep, virtdomains, Murder), then we will most likely accept. If someone is interested in getting autcreate accepted, I would encourage them to po

Re: Cyrus-Imap 8-bit Header Patch

On 20 Jul 2006, at 09:57, Holm Kapschitzki wrote: i have installed a debin sarge package cyrus21-imapd_2.1.18-1 +sarge2_i386.deb and a problem with "x" in the subject cause of german "ä". Its the 7-bit Header Poblem. Now i just looking for a patch, but cant find it. Is there anybody who have

Re: trashed databases after disk full situation

On 21 Jul 2006, at 07:20, Daniel Eckl wrote: The link below every mail http://asg.web.cmu.edu/cyrus/mailing- list.html just gives 404. The web/http links on http://cyrusimap.web.cmu.edu/ lists.html#archives gives 404 either. This list is here: http://lists.andrew.cmu.edu/pipermail/inf

Re: Performance and cheap storage

On 23 Jul 2006, at 11:00, Robert Banz wrote: The second thing to consider is that the performance on modern SATA drives, if you're using a driver for the SATA interface that supports advanced features such as command queueing, are going to show you performance akin to SCSI drives -- even mor

Re: Replication woes with a specific mailbox...

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 -> user.XXX.Uni). Remov

Re: High availability email server...

On 02 Aug 2006, at 03:24, Daniel Eckl wrote: Well, as far as I know, the mailboxes.db and other databases are only opened and modified by the master process. That's not the case. :; grep -lw mboxlist_open *[ch] arbitron.c chk_cyrus.c ctl_cyrusdb.c ctl_mboxlist.c cyr_expire.c cyrdump.c fud.c i

Re: XFER ACL issue

ntil we can propose fixes. :wes On 02 Aug 2006, at 11:19, Ken Murchison wrote: Wesley Craig wrote: I was tracking a very similar issue with xfer between 2.2 and 2.3.6. xfer'ing vanilla 2.2.12 mailboxes to 2.3.6 seems to work fine, and xfer'ing a 2.3.6 mailbox to 2.2.12 also more

Re: XFER ACL issue

On 02 Aug 2006, at 21:03, Wesley Craig wrote: It also includes: ... a reduction in the unnecessarily large amount of memory that sync_server allocates for per-message pathnames; I didn't make clear what the memory issue above is. For very large mailboxes (>150K messages), the unnec

Re: cyrus UIDL - POP double download problem

On 08 Aug 2006, at 14:15, Vincent Fox wrote: How does Cyrus derive the UIDL? Cyrus derives POP UIDL from IMAP UID or a combination of UIDVALIDITY and UID. :wes Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.w

Re: Simultaneous database access

On 16 Aug 2006, at 14:52, David Korpiewski wrote: My director had us go back to using our Macs to try to build a failover cluster. We were able to set up two mail servers sharing the same backend XSAN. We put our database for cyrus on the XSAN and had both mail servers use _the same_ dat

Re: unexpunge broken?

Paul already mentioned that unexpunge uses internal (dot) syntax, not unix (slash) syntax. Also, your delprune command will also expunge all your mail, so your expunge command doesn't really do much. You need to combine the two statements: delpruneandexpunge cmd="cyr_

Re: unexpunge broken?

On 22 Aug 2006, at 02:36, C.K wrote: it still doesn't work, can't lock null... "Can't lock null" in this case means that unexpunge didn't find the mailbox in question in mailboxes.db. :wes Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu Lis

Re: unexpunge broken?

yntax that you'd using. I don't use the virtual domain code myself, so I can't help you with that, but if you can find the name of the mailbox as listed with ctl_mboxlist -d, then you should be able to give that name to unexpunge -l. :wes Den Ti, 2006-08-22, 16:06 skrev W

Re: unexpunge broken?

Sounds like this inconsistency is a good candidate for a bug report and/or a patch. :wes On 22 Aug 2006, at 13:13, Tuan Van wrote: I am not the OP but interested in unexpunge as well so I tried . You are right. su -s /bin/sh cyrus -c '/path/to/unexpunge -lv domain.tld!user.username.folder'

Re: mailboxes.db unreadable, recovery procedure?

What error are you getting that indicates that mailboxes.db is unreadable? I suspect that the backups will also be unreadable, due to the way they are made. If they *are* readable, as the cyrus user: ctl_mboxlist -d -f db.backup1/mailboxes.db > somefile.txt You'll want to examine "

Re: mailboxes.db unreadable, recovery procedure?

On 25 Aug 2006, at 15:53, !jeff!{InterVerse} wrote: sudo -u cyrus /usr/local/cyrus/bin/reconstruct -r -f user fatal error: can't read mailboxes file OK, so that doesn't work. Now what can I do? If you need a list of mailboxes, you can probably get a pretty complete one with "strings mailbox

Re: sync_client stalls the rest of cyrus while 'no route to host'

On 26 Aug 2006, at 16:22, Paul Dekkers wrote: I don't know if this is a known issue: as soon as I enable replication and the sync_client gets a "No route to host" from the replica, the rest of the cyrus startup seems to stall: no imap, no lmtp... just because a replica is unreachable. (In th

Re: Guidance on Use of Reconstruct

On 26 Aug 2006, at 14:04, Jim Brett wrote: Is it overkill to run reconstruct (and quota) after every failover (which so far has never been due to cyrus being corrupted). I think so, yes. It's much more effective to note in the logs that particular mailboxes aren't working, and reconstruct t

Re: failover scenario's for replication

On 26 Aug 2006, at 16:09, Paul Dekkers wrote: Right now, it looks tricky to me to enable replication after failover, or the replicated machine itself if you're not sure that the replica is identical and the sync-processes finished completely: if a message- file is in place on machine A (say "7

Re: sync_client stalls the rest of cyrus while 'no route to host'

On 26 Aug 2006, at 21:42, Bron Gondwana wrote: Though it is dying less as we discover bugs and patch them. See my post last night (au time) about the "three MAILBOX -> USER promotions and you're out" issue. That's the first thing that has killed sync_client in a while. I have a (shrinking, ye

Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run

On 29 Aug 2006, at 04:35, David Carter wrote: My original code (which we are still running: I'm not in any hurry to upgrade to 2.3) sorts mailbox actions by user. If a single mailbox action associated with a user fails the rest are discarded and a USER event is generated. If the USER event f

Re: sync_client stalls the rest of cyrus while 'no route to host'

On 28 Aug 2006, at 20:33, Bron Gondwana wrote: What else do you have that will kill it? 4) xfer onto a replicating backend causes sync_client to exit 8) renaming users causes sync_client to exit In both of these, size and other load matters. We agree on the design-flaws front

Re: failover scenario's for replication

On 29 Aug 2006, at 04:11, Paul Dekkers wrote: I haven't tried this; but does it hurt defining sync_server, imapd and friends processes in the replicas cyrus.conf and by that have it identical as the master? If you tell the replica where mupdate is, sync_server behaves incorrectly. I'd also a

Re: deliver.db conversion to skiplist

On 29 Aug 2006, at 11:22, Shelley Waltz wrote: My question is - should I convert the deliver.db to skiplist? If I simply move it elsewhere and change the imapd.conf to use a deliver.db in skiplist and restart, what is lost? Surely this huge db contains information necessary and useful to th

Re: sync_client stalls the rest of cyrus while 'no route to host'

On 29 Aug 2006, at 18:38, Bron Gondwana wrote: I fail to see the difference between this and a single big log file where each replica keeps track of where it's up to in the log file and then seeks to that spot, reads up to say 10,000 lines and processes that, then stores the new location so

Re: 2.2 vs. 2.3?

On 31 Aug 2006, at 12:44, Karl Boyken wrote: We're running 2.2.12 in production here, but my impression from traffic on this list is that at least a few people are using 2.3, even though 2.3 is a testing distribution. Is that accurate? Is 2.3 stable enough to use on a production mail serve

Re: ssl "dyld: Library not loaded" with either cyrus-imap v2.3.7 *or* cvs-head

On 06 Sep 2006, at 21:55, OpenMacNews wrote: i've been fighting this for awhile; i've posted b4, with no 'bites'. I've seen other reports on the list, including solutions. One common one was to use the instructions here: http://cyrus-imapd.darwinports.com/ As I recall, another was

Re: ssl "dyld: Library not loaded" with either cyrus-imap v2.3.7 *or* cvs-head

On 06 Sep 2006, at 23:00, OpenMacNews wrote: that said, every other app i've built that links/uses 'my' ssl libs is problem-free. OK, now I'm frustrated. I knew I'd seen a problem that sounded similar reported on the list before. Here's the reference: http://www.mail-archive.com/info-cy

Re: sync_server "memory leak" with giant new mailbox first sync

I saw this problem the first time I enabled replication on a machine hosting all the IT support staff the University of Michigan. Plenty of large mailboxes there! My solution (such as it is) was to reduce the wasteful amount of space sync_server was allocating per message: --- cyrus-imap

Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run

ape backups only for the case where users inadvertently delete folders. :wes -Original Message- From: "Wesley Craig" <[EMAIL PROTECTED]> To: "David Carter" <[EMAIL PROTECTED]> Cc: "Bron Gondwana" <[EMAIL PROTECTED]>; "Ken Murchison&

Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run

On 12 Sep 2006, at 16:51, Kjetil Torgrim Homme wrote: interesting. is one of the replicas off-site? you don't worry about EMP or stuff like that? for how long do you keep the expunged messages? I think turning off tape backup would be a very tough sell around here... In our test runs, res

Re: Design of Cyrus IMAP

On 14 Sep 2006, at 10:23, <[EMAIL PROTECTED]> wrote: Can you please tell me where can I find the architecture and design of Cyrus IMAP server. Is there any documentation available for it? Actually, I want to analyze the internal working and flow of Cyrus. Can I find any pointers for it? In the

Re: experience report / upgrading to cyrus-imapd 2.3

On 14 Sep 2006, at 11:45, Andreas S. Kerber wrote: - deletion of messages via imap does not work through the old frontends, possibly due to the new ACL code in 2.3 which offers separate rights for message delete, mailbox delete, and expunge. The only way to fix this seems upgrading the fronten

Re: reconstruct

On 22 Sep 2006, at 11:08, Craig White wrote: The man page on reconstruct doesn't suggest that it is necessary to shut down cyrus so I don't. From the interlock code in reconstruct and the rest of Cyrus, it's intended that the two can be run at the same time. Reconstruct can, for instance

Re: Commerical Cyrus IMAPD support?

I can do this sort of thing for you. I work half-time for the University of Michigan, supporting their Cyrus IMAP servers among other things. :wes On 26 Sep 2006, at 21:58, Jay Levitt wrote: I've been wrestling with IMAPD/SASL problems for a few days, trying to get a formerly-working sasl

Re: Mupdate vs lmtp...

On 06 Oct 2006, at 07:16, Brasseur Valéry wrote: Why does the lmtpproxyd directly connect to the master when other process connect to slave ? You want to know why? I think the idea may have been to be extra sure that the location of the mailbox was correct before bouncing a message. I do

Re: sync_(client|server) problem

Looks like the syslog messages probably cover why sync_client is having problems. However, I think common wisdom is that sync_client should be started separately from cyrus master, because the sync_client process dies. Since it dies, you should plan on restarting it, monitoring whether it

Re: Deferred email with remote protocol error in reply

On 27 Oct 2006, at 05:08, Libor Pechacek wrote: MAIL FROM:<[EMAIL PROTECTED] > SIZE=15311 RCPT TO:<[EMAIL PROTECTED] > DATA < 250 2.1.0 ok < 250 2.1.5 ok < 354 go ahead . < 7 lockers In this case the obvious reason for the error is the

Re: Deferred email with remote protocol error in reply

On 27 Oct 2006, at 15:33, Henrique de Moraes Holschuh wrote: Cyrus master has issues with FDs 0,1 and 2 since ancient times. If anything in the code, anywhere, closes them and don't reopen them immediately, something like syslog() or another offender will promptly take them over and cause a

Re: Deferred email with remote protocol error in reply

On 27 Oct 2006, at 16:00, Henrique de Moraes Holschuh wrote: That said, just moving off 0,1,2 is not difficult. ... The ideal fix would be to have them be dynamic. Ideally, 0, 1, and 2 should be reserved for stdin, stdout, and stderr. In an environment where std* don't make sense, i.e.,

Re: GSSAPI: A token had an invalid MIC

On 27 Oct 2006, at 22:35, Phil Pennock wrote: New server: OS/Arch: FreeBSD 6.1 / amd64 Cyrus IMAPd: 2.3.7 Cyrus SASL 2.1.22 OpenSSL: 0.9.7i Heimdal: 0.7.2 (OS port rev _1) Anyone any ideas or pointers, please? Given the versions of things, I'd suspect one or both of these two problems:

Re: Cyrus, clusters, GFS - HA yet again

On 27 Oct 2006, at 03:35, Janne Peltonen wrote: Or should I just give up and start considering Murder? Before you decide on whether to give up on clustering, you should thoroughly consider Murder. At a minimum, it provides the location independence that you'd like. With replication, you h

Re: Cyrus IMAP and MySQL mailboxes (Building load-balancing cluster)

On 22 Nov 2006, at 19:10, Sarah Walters wrote: Only a single machine can have write privileges to the mailboxes database at a time. Actually, only a single process can be writing to a mailboxes database at a time. Then, assuming the database is closed between changes (can a developer ple

Re: 2.6 Kernel and POP issues

On 27 Nov 2006, at 18:20, Robert T. Covell wrote: Other articles I have read reference how to set it up. My setup seems to be similar to what I have seen. From the below article it is possible that I need to fill up the entropy pool. Are their other ways to do this aside from running find /.

Re: Sharing Murder?

On 29 Nov 2006, at 10:46, Janne Peltonen wrote: The part '... all "replicated" servers can serve the same mailboxes from a shared filesystem' attracted my attention. Is this the LB that is reported not to work with current murder/replication? Or is this something else? In the "replicated" m

Re: Sharing Murder?

On 30 Nov 2006, at 11:48, Janne Peltonen wrote: ...or is it? If the traditional config delivers to the correct backend by looking the correct backend up in the mailboxes db (from mupdate master), then it can use the sieve scripts and duplicate delivery dbs in there. But what about this kind of

Re: cyrus replication question

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

Re: cyrus replication question

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

Re: cyrus replication question

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.

Re: cyrus replication question

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

Re: reconstruction problems

Just to be clear, the problem is that reconstruct inappropriately deleted folders after an error? Or, reconstruct is giving errors for folders that were deleted (by the user) so you feel the errors are inappropriate? :wes On 15 Dec 2006, at 09:14, stas khromoy wrote: while working on rep

Re: reconstruction problems

reconstruct -r just reads the DB, so yes the DB must be out of sync with the filesystem (not really "corruption" per se). reconstruct -r -f reads the DB *and* the filesystem, but would still probably be subject to the DB problem you're experiencing. When reconstruct finds mailboxes in the

Re: Some timing info on populating mailboxes

Sorry, that's backwards: int one = 1; if (( proto = getprotobyname( "tcp" )) == NULL ) { syslog( LOG_ERR, "getprotobyname: %m" ); return( -1 ); } if ( setsockopt( socket_fd, proto->p_proto, TCP_NODELAY, &one, sizeof( one )) != 0 ) {

Re: Some timing info on populating mailboxes

On 17 Dec 2006, at 02:22, Ross Boylan wrote: An earlier report on this list said sysctl -w net.inet.tcp.delayed_ack=0 worked wonders. There does not seem to be such a setting in my Linux 2.6.18 kernel. I don't recall if Linux has ever had that sysctl. Mac OS X does. This option globally di

Re: Some timing info on populating mailboxes

On 17 Dec 2006, at 14:12, Ross Boylan wrote: Is it enough to set this on the listening IMAP socket, or does it need to be set on the sockets that get opened up as the dialogue progresses? Put differently, can I write a little independent program to set the socket options, or do I need to modify

Re: cyr_expire error

I've seen this behavior (and resolution) as well. Not sure what the cause is. :wes On 18 Dec 2006, at 12:06, Joseph Brennan wrote: Earlier I wrote: cyr_expire has started failing with this error: cyr_expire[4729]: IOERROR: bboard zero index/expunge record 4/1591 D'oh. I did "reconstru

Re: More timings populating a mailbox

These are interesting results. I encourage you to make an entry in the Cyrus Wiki about the work you've been doing. As an additional filesystem option, we've found that IMAP on reiser improves significantly with the notail option. Good work. :wes Cyrus Home Page: http://cyrusimap.we

Re: Patches used at FastMail.FM

On 08 Jan 2007, at 11:23, Ken Murchison wrote: We found a few small buglets in the IMAP proxy code that we didn't expect. Either nobody else has a 2.3 Murder running, or they didn't notice the random (infrequent) core dumps. We're (UMich) continuing to run 2.3 replicated backends with 2.2

Re: Murder slave question ...

On 17 Jan 2007, at 03:10, Brasseur Valéry wrote: Is it normal staht slave ALWAYS disconnect after receiving some command update of the master ? And retry a full update 20sec later ? The replica shouldn't be talking to the mupdate master. Remove the mupdate_server config option from the repl

Re: Replication and failover

On 18 Jan 2007, at 05:41, Janne Peltonen wrote: Is there documentation abt replication failover scenarios anywhere? I can, of course, conjure up a thing or two, but I'd like to see how other people have resolved 'corrupted mailspool -> services to the replica -> maintenance -> resync master -

Re: Delayed expunge / undeleting messages

A bunch of people already pointed out unexpunge, so I'll point out that the delayed expunge / unexpunge functionality doesn't help if the user deletes a whole folder. See: https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2871 for the problem report and a patch for a proposed solution

Re: Can murder be used for IMAP server migration?

On 18 Jan 2007, at 20:16, Gary Mills wrote: Is there any documentation on how to configure and manage a unified Murder? See the man page for imapd.conf: mupdate_config: standard The configuration of the mupdate servers in the Cyrus Murder. The "standard" confi

Re: Delayed expunge / undeleting messages

On 19 Jan 2007, at 05:50, Rob Mueller wrote: I know David Carter implemented a patch for this in 2.2. I'm not sure if Wesley's patch is related to it or a completely separate implementation. Completely separate, tho my is based on comment from David suggesting how he would do it if he were

Re: Clustering and replication

On Jan 26, 2007, at 3:07 AM, Tom Samplonius wrote: - Janne Peltonen <[EMAIL PROTECTED]> wrote: As a part of our clustering Cyrus system, we are considering using replication to prevent a catastrophe in case the volume used by the cluster gets corrupted. (We'll have n nodes each accessing the

Re: replication stalled (in 2.3.8)

I've seen this before. I'm not sure (yet) of the cause. :wes On 15 Feb 2007, at 10:46, Paul Dekkers wrote: Normally the synchronization continues as usual after that restart, this time I needed a restart of the sync_server on the replica (I just restarted the cyrus-master on the replica, act

Re: vacation programs

On 20 Mar 2007, at 11:24, Gene Rackow wrote: My current vacation program is based on the Unix vacation rules. Only respond to mail that you are listed on the To: or cc: lines. No response to mailing lists, precedence: bulk or junk, some black-listed addresses, etc. The only thing I'd add is t

Re: cyrus replication validation

On 06 Apr 2007, at 17:52, John Capo wrote: Quick mailboxes.db check. ctl_mboxlist -d | md5 on server1 ctl_mboxlist -d | md5 on server2 Both hashes should be identical. Or diff the ctl_mboxlist -d outputs. The provided Cyrus tool "make_md5" is for validating replication. It would, for

Re: Recomendations for a 15000 Cyrus Mailboxes

On 10 Apr 2007, at 11:16, John Madden wrote: Please specify those weaknesses. 250,000 mailboxes on reiserfs right now, always open to options. The main problem I'm aware of is that in the event of a "problem", reiserfsck 1) can take a long time (like weeks) to complete, 2) doesn't necessar

Re: Recomendations for a 15000 Cyrus Mailboxes

On 10 Apr 2007, at 12:40, John Madden wrote: Indeed, I've seen reiserfs do some very long fsck's, but I've seen the same out of ext3. But for a filesystem of 35 million mail files, I figure it's got to beat ext3 on performance, at least. ...But there don't seem to be any stats at this scale to

Re: syncserver[4715]: Fatal error: Virtual memory exhausted

You probably encountered a single very large mailbox. This patch: --- cyrus-imapd-2.3.8/imap/sync_support.c 2006-11-30 12:11:20.0 -0500 +++ cyrus-imapd-2.3.8p3/imap/sync_support.c 2007-04-12 13:27:49.0 -0400 @@ -914,9 +914,9 @@ result = xzmalloc(sizeof(struct sync_messa

Re: extremely poor performance with many maiboxes for 'list "" *'

I've seen problem like that, but I identified issues in the auth_canonify() code for kerberos. You don't appear to be using kerberos, so your situation is likely to be different. On the other hand, I can speculate that LIST is much slower than grep because imapd needs to determine whether

Re: cyrus 2.3.x and thunderbird 2.x delete issue

What is "deleteright" set to on this server? You problem description suggests that it's not set. :wes On 20 Apr 2007, at 05:50, Wolfgang Breyha wrote: I don't know;-) Most of the mailboxes here have "lrswipkxtea" set. And searching the source I found code in cmd_myrights, which adds "c" an

Re: syncserver[4715]: Fatal error: Virtual memory exhausted

On 18 Apr 2007, at 01:27, Simon Matter wrote: I'm still wondering why the code is there, can anybody comment on this? The buffer in question is dynamically sized. I gather that an earlier version of the code pre-allocated 5 paths. A later version allowed an arbitrary number, adjusting th

Re: syncserver[4715]: Fatal error: Virtual memory exhausted

Yeah, that's a good point. I use sync_batch_size of 100,000. Regarding the original question, there are other operations that will exhaust memory as well. We've had two recent reports of Thunderbird users who unexpectedly developed extremely large cyrus.* files in their trash. Since cyru

Re: Replication speeds?

Obviously looking at more iostat information would give a better idea, but I'd estimate that you are NOT I/O bound. Sorry I can't give you absolute numbers from UM, but I can share a patch that we wrote that we believe has increase sync throughput substantially, as evidenced by the lack of

Re: Replication speeds?

On 10 May 2007, at 06:45, Nik Conwell wrote: Thanks for the info & patch. I applied it to the 2.3.7 test system but no appreciable speed increase. Did it help you with both large replications (I'm doing a single 1.1G user to test) and the rolling replication? ttcp shows the nets can do about

Re: Cyrus 'cluster' general upgrade strategy?

You'll need to upgrade primary and replica backends together for a 2.3.7 to 2.3.8 upgrade. Other than that, you can upgrade just one backend pair in a 2.3.7 cluster, no problem. Once you have confidence in the correctness of 2.3.8, upgrade the rest of the backends. It's also pretty commo

Re: Moving mailboxes

On 24 May 2007, at 07:15, Sebastian Hagedorn wrote: Well, I experimented with one account and found that you get errors if you try to actually access the mailbox while it's being moved: May 24 13:10:42 lvr13 imap[16707]: IOERROR: stating header for user.xxx: No such file or directory But I su

Re: Cyrus with a NFS storage. random DBERROR

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,

Re: Cyrus with a NFS storage. random DBERROR

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

Re: Remote mailbox creation error / unified murder

On 02 Jul 2007, at 06:53, Janne Peltonen wrote: > But when try to imapsync the old server's data to the new one, with > only > one multi-threading mupdate master process, I keep getting 'connection > to the master timed out' errors from the mupdate slaves. During your imapsync process, I might d

<    1   2   3   4   >