On Sep 9, 2009, at 4:16 PM, Timo Sirainen wrote:
On Wed, 2009-09-09 at 14:12 -0400, Jonathan Siegle wrote:
Running dovecot 1.2.4(imap only) on AIX out of inetd. I accept passwords(PAM for auth) and kerberos tickets. Occasionally we see dovecot-auth stop responding. I just kill it off and another process is spawned which works fine.
If you use PAM then I guess you should have auth worker processes too?
Yes
So one dovecot-auth and 1+ "dovecot-auth -w"?
Yes. One of each.
Does it help if you kill off the worker processes?
It only helps when I kill dovecot-auth, not dovecot-auth -w.
What if you kill imap-login processes instead?
I don't have imap-login processes associated with inetd spawned
dovecot. imap-login is what I call in inetd. I don't see them in the
process table.
Segmentation fault in __fd_poll at 0x900000000117634 ($t1) 0x900000000117634 (__fd_poll+0x98) e8410028 ld r2,0x28(r1) (dbx) where __fd_poll(??, ??, ??) at 0x900000000117634 ioloop-poll.poll(__listptr = 0x00000001104dd330, __nfds = 145,
This just shows that it was waiting for something to do. Does AIX have something like strace or truss? Use it to see what's happening when a request comes.
Yes I have truss. So tomorrow when this happens I'll do truss -f -p on
the dovecot-auth process?
Oh my dovecot.conf file has this for pam:
passdb pam { args = max_requests=1
}
because of the expire password problem for kerberos.
thanks, Jonathan