On Sep 10, 2009, at 2:43 PM, Timo Sirainen wrote:
On Thu, 2009-09-10 at 14:32 -0400, Jonathan Siegle wrote:
It only helps when I kill dovecot-auth, not dovecot-auth -w.
Interesting..
What if you kill imap-login processes instead?
I don't have imap-login processes associated with inetd spawned dovecot.
Why do you use inetd? I'm currently wondering if I should bother
adding inetd support to Dovecot v2.0.
We ran imap(Uwash) for years. Is there a reason to not run it from
inetd?
Yes I have truss. So tomorrow when this happens I'll do truss -f -p
on the dovecot-auth process?Yes. Also having auth_debug=yes enabled might show something useful. What does it log last before it stops responding?
I found something in syslog today:
local0.log.20090916:Sep 16 11:58:01 tr27n18.aset.psu.edu dovecot: auth (default): BUG: Worker sent reply with id 1, expected 2 local0.log.20090916:Sep 16 11:58:01 tr27n18.aset.psu.edu dovecot: auth (default): worker-server(mck2,146.186.125.214): Aborted: Worker is buggy