From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: Re: [Greg Troxel] gnus/dovecot open transactions panic
Date: Tue, 02 Nov 2010 13:29:06 -0400 [thread overview]
Message-ID: <smuvd4focrh.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <m38w1g34e3.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 30 Oct 2010 02:34:12 +0200")
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Greg Troxel <gdt@work.lexort.com> writes:
>
>> Oct 29 19:58:23 linuxpal dovecot: IMAP(gdt): Panic: Trying to
>> close mailbox foo.bar with open transactions Oct 29 19:58:23
>> linuxpal dovecot: dovecot: child 28914 (imap) killed with signal 6
>> (core not dumped - set mail_drop_priv_before_exec=yes)
>> and in *imap log*
>> 19:58:23 1537 EXAMINE "foo.bar" (QRESYNC (1153316454 1))
>> followed by 109 more EXAMINE lines, all with qresync params. Given
>> that it's dovecot that's crashing, this is feeling like a dovecot
>> bug.
>
> It sounds like it, but there might be a Gnus pattern that triggers the
> bug, and perhaps Gnus could work around that. Do you see anything in
> particular that makes dovecot panic? Is there a specific mailbox that
> triggers this, or, uhm. Something? :-)
Dovecot author says this is the fix. I'll try it when I get a chance.
I don't think any gnus workaround would be reasonable.
http://hg.dovecot.org/dovecot-1.2/rev/b30af25c622d
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2010-11-02 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 23:45 Greg Troxel
2010-10-26 7:04 ` Julien Danjou
2010-10-27 11:24 ` Greg Troxel
2010-10-29 22:53 ` Lars Magne Ingebrigtsen
2010-10-30 0:02 ` Greg Troxel
2010-10-30 0:34 ` Lars Magne Ingebrigtsen
2010-10-30 0:52 ` Greg Troxel
2010-11-02 17:29 ` Greg Troxel [this message]
2010-11-24 2:19 ` Greg Troxel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=smuvd4focrh.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).