From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: [Greg Troxel] gnus/dovecot open transactions panic
Date: Mon, 25 Oct 2010 19:45:18 -0400 [thread overview]
Message-ID: <smur5fddegh.fsf@linuxpal.mit.edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 700 bytes --]
I'm not sure if this is a dovecot or gnus issue.
The problem happens at:
commit 18836c407ba5a49028cc957fa511195199dbbd77
Author: Julien Danjou <julien@danjou.info>
Date: Mon Oct 25 17:40:10 2010 +0200
Remove gnus-with-local-quit
Signed-off-by: Julien Danjou <julien@danjou.info>
but seems not to at:
commit bf9d34407b6ba1fdd35573efeb8f4de213273421
Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Date: Thu Oct 7 15:24:43 2010 +0200
(shr-insert): Don't leave trailing spaces.
I don't mean to malign Julien - that commit is surely fine but I haven't
bisected the 210 in between. And I think it's likely gnus is being
legal but more aggressive.
[-- Attachment #1.2: Type: message/rfc822, Size: 2704 bytes --]
[-- Attachment #1.2.1.1: Type: text/plain, Size: 1789 bytes --]
I have been using dovecot with gnus for a long time. Recently, I
started getting failures, and I think it's a dovecot problem triggered
by gnus being more aggressive, but I'd like to hear opinions about
whether I should pursue this as a gnus bug.
The log shows:
Oct 25 19:27:36 gdtserver dovecot: IMAP(gdt): Panic: Trying to close mailbox foo.bar with open transactions
Oct 25 19:27:36 gdtserver dovecot: dovecot: child 26231 (imap) killed with signal 6 (core not dumped - set mail_drop_priv_before_exec=yes)
and this seems to be triggered when dovecot is going GCC: to a local
mailbox (not imap) when sending, but also semi-randomly.
most of dovecot -n: (I'm sure that I'm not having auth problems and
would rather not post that part):
# 1.2.14: /usr/pkg/etc/dovecot.conf
# OS: NetBSD 5.1_RC1 i386
protocols: imaps
login_dir: /var/run/dovecot/login
login_executable: /usr/pkg/libexec/dovecot/imap-login
login_processes_count: 4
login_max_processes_count: 16
max_mail_processes: 32
first_valid_uid: 128
mail_location: maildir:~/IMAP
I have 162 mailboxes polled by gnus on this dovecot instance.
I get the panic on various mailboxes and I can't see a pattern.
I do get
Checking new news...
nnimap-send-command: SIGPIPE raised on process *nnimap*; closed it
From gnus. I then look at the listed one in the panic, and *imap-log*
From gnus. This just may be an artifact of pipelining, but the
panic-list mbox has 30 more after it that were sent, as in:
19:35:43 506 EXAMINE "mbox.named-in-panic" (QRESYNC (1208908407 1))
[30 more lines]
I'm guessing that this is a dovecot problem. I realize I should update
to 1.2.15 :-) but I didn't see anything in the 1.2.15 release notes that
looks like a match.
[-- Attachment #1.2.1.2: Type: application/pgp-signature, Size: 194 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2010-10-25 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 23:45 Greg Troxel [this message]
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
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=smur5fddegh.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).