Re: IMAP/LMTP/Quota locking problem
Hi, -- Scott Adkins [EMAIL PROTECTED] is rumored to have mumbled on Montag, 17. Mai 2004 11:03 Uhr -0400 regarding Re: IMAP/LMTP/Quota locking problem: I do know that as of 2.2.1, the problem still exists. I find it impossible to trigger the bug on my own in our test environment, and we won't be doing an upgrade to 2.2.3 (or whatever happens to be out) until the summer time frame. thanks for the info. The patch was definitely added *after* 2.2.1 ... hmm, now that I think about it: seems like it was even added after 2.2.3! Is bug 1270 really fixed in CVS only? Currently, we manage the problem by watching the sendmail syslog file for System I/O errors on the Cyrus mailer (grep for 'mailer=cyrus.*System.I.O') We don't get those. I wonder if we actually have separate problems. Or maybe not. However, in our case the sendmail processes get stuck as well, maybe due to our setting of DeliveryMode to interactive!? and when we see some, we run another script that tells us which cyrus proc has the write lock on their quota file and we kill that process. The problem occurs regularly, with some users more reliably triggering the problem than others. What does regularly mean? We've been running the server in prdouction since March, 1, but it happened for the first time a little more than a week ago ... Greetings, Sebastian -- Sebastian Hagedorn M.A. - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10 Zentrum für angewandte Informatik - Universitätsweiter Service RRZK Universität zu Köln / Cologne University - Tel. +49-221-478-5587 pgpy8iGPSF98R.pgp Description: PGP signature
Re: IMAP/LMTP/Quota locking problem
On Tue, 18 May 2004, Rob Siemborski wrote: This should be fixed in 2.2.3 (if it is indeed the APPEND/quota files issue). We're not backporting it, since the patch was somewhat extensive. Er, I just checked the logs, it appears this is only in CVS. But 2.2.4 should be out very shortly anyway. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyrus-imapd 2.2.1 beta - auth problem
On Fri, 25 Jul 2003, Simon Matter wrote: I have now straced the pid's on 2.1.14 and 2.2.1-BETA. I have also tested the 2.2.1-BETA with pwcheck using /etc/sasldb2 and it works well. Looks to me like there is something broken when using saslauthd. FYI, the 2.2.1-BETA test is against cyrus-sasl 2.1.10. I'd really be more intersted in tests against recent versions of Cyrus IMAP and SASL. Does testsaslauthd reveal anything? -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMAP/LMTP/Quota locking problem
On Mon, 17 May 2004, Sebastian Hagedorn wrote: It started here: May 14 09:04:59 lvr1 imapd[14301]: login: vpn82-4.vpn.Uni-Koeln.DE[134.95.82.4] s0283928 plaintext+TLS May 14 09:04:59 lvr1 imapd[14301]: seen_db: user s0283928 opened /var/lib/imap/user/B/s0283928.seen May 14 09:04:59 lvr1 imapd[14301]: open: user s0283928 opened Drafts As you can see a VPN dial-up connection was used. I think it likely that the notorious APPEND problem happened. i.e. the connection was dropped by the client while the server was doing an APPEND. This is bug 1270 https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=1270 and is marked FIXED. For completeness' sake: after the IMAP session above, hte lmtpd processes started getting stuck when delivering to this user: [snip] So, is this really fixed in 2.2.3? Has anybody seen something like this since? And would it be OK to apply the patch to 2.1.16? Or does it depend on other stuff that happened in CVS between 2.1.16 and the time the patch was created? This should be fixed in 2.2.3 (if it is indeed the APPEND/quota files issue). We're not backporting it, since the patch was somewhat extensive. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Cyrus IMAPd 2.2.4 Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm pleased to announce the release of Cyrus IMAPd 2.2.4. This release contains a number of bugfixes and improvements since the previous release. Changes include the ability to use a cyrusdb backend for quota tracking, fixing a number of potential deadlocks in APPEND code, a number of NNTP and IPv6 related bugs, fixes to the LDAP ptloader code, as well as many other minor fixes and improvements. A full change list is available in doc/changes.html in the distribution. Download the release at: ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.2.4.tar.gz or http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.2.4.tar.gz Thanks to all who contributed! - -Rob - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.76 iQA/AwUBQKomj2es8cJc4y/MEQIykgCgyn1LLZBlLEqMbksLXIIH6z5TLOUAoLJN +usrafmF8U87vY/KgHev6Rrf =TRDo -END PGP SIGNATURE- --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMAP/LMTP/Quota locking problem
--On Tuesday, May 18, 2004 9:13 AM +0200 Sebastian Hagedorn [EMAIL PROTECTED] wrote: thanks for the info. The patch was definitely added *after* 2.2.1 ... hmm, now that I think about it: seems like it was even added after 2.2.3! Is bug 1270 really fixed in CVS only? Good question! :) I hope it is fixed :) If I remember right, it has something to do with SSL. Are you using SSL? Basically, the quota file gets locked and stays locked because the IMAP process (which is usually the one that has the quota file open for write) is trying to do a read on an SSL socket (this is from memory and from what I have seen in our traces). The quota lock problem is just a side effect of that issue... Currently, we manage the problem by watching the sendmail syslog file for System I/O errors on the Cyrus mailer (grep for 'mailer=cyrus.*System.I.O') We don't get those. I wonder if we actually have separate problems. Or maybe not. However, in our case the sendmail processes get stuck as well, maybe due to our setting of DeliveryMode to interactive!? I find that interesting... after an IMAP process locks the quota file, the LMTP processes start to stack up. After awhile, anything trying to be delivered to that user generates a System I/O error. It makes it easy to catch, since as soon as we see a few errors for a particular user, we run fuser on that user's quota file to get a list of processes, run lsof on that list of processes to find the process that has the quota file open for write and we kill it. The next entry in the syslog should show that a message was sent instead of deferred, which means we fixed the problem. The problem occurs regularly, with some users more reliably triggering the problem than others. What does regularly mean? We've been running the server in prdouction since March, 1, but it happened for the first time a little more than a week ago ... On average, I would say at least once every day or two. Sometimes it gets worse and we get a few in a day, and sometimes, a single user may do it a couple times in a day... It does seem like some users trigger it a lot more than the majority. This suggests some kind of interaction between the IMAP process and the e-mail client, possibly back to that SSL read issue again. Scott -- +---+ Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ UNIX Systems Engineer mailto:[EMAIL PROTECTED] ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 +---+ PGP Public Key available at http://www.cns.ohiou.edu/~sadkins/pgp/ pgpPDk4Ziu4dw.pgp Description: PGP signature
Re: idled thoughts
On Tue, 18 May 2004, Andreas wrote: Is it useful? Does it use too much resources? Is it not used that much, and as such not well tested? Haven't really noticed it taking up too much resources myself. In terms of it being useful, rather informal trial and error experimentation here seemed to indicate that the Microsoft clients were much happier with it enabled. Not sure if that was the ultimate fix, but these particular individuals are no longer having problems, so that's good enough for me! ;) I see that thunderbird 0.6 can use the IDLE extension and I like the idea of the server notifying the client whenever there is new mail. Using the I haven't tried it in a while, but previously when I told TBird to check for new mail in a bunch of folders and had IDLE enabled, things seemed to get really wacky. (Number of new messages would be bogus, some folders tagged as having new mail when they didn't, etc.) So in the end I just turned off the IDLE support in TBird. That was a while ago, though, so I don't know if that has improved. Amos --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sendmail hooks for pre-checking of over-quota imap users?
--On Monday, May 17, 2004 11:17:25 PM +0200 Andrzej Filip [EMAIL PROTECTED] wrote: I have read the sources (sendmail-8.13.0.Beta2/sendmail/map.c) and it seems that current implementation of socket map in *sendmail* does not pass explanation strings to sendmail.cf [no fault at cyrus side] All current version of my cyrus sendmail integration should be capable to handle TEMP replies from smmapd of cyrus. AFAIR some early version did not do it. ...does that mean, that I should get an over quota reply? I could manage to configure sendmail in order to do that. I just get User unknown when a user is over quota. Didi -- - Didi Rieder [EMAIL PROTECTED] PGPKey ID: 3431D0B0 - pgpOaBZvOI6ox.pgp Description: PGP signature
