een poll() and epoll() ?
Nothing important. What I meant by that above is that strace shows that
the code that's running and eating 100% CPU is either pam_ldap or
nss_ldap, not Dovecot.
[attachment "signature.asc" deleted by JackyC/UMAC]
ecot] Timeout Value
Sent by:
dovecot-bounces+jackyc=umac...@dovecot.org
On Wed, 2010-04-07 at 11:20 +0800, jac...@umac.mo wrote:
> > At least for dovecot-auth -w it looks like it's doing an LDAP lookup
(or
> connect) in here. Maybe it keeps rapidly reconnecting to it all the
&
"..., 257) = 257
At least for dovecot-auth -w it looks like it's doing an LDAP lookup (or
connect) in here. Maybe it keeps rapidly reconnecting to it all the
time?.. Anything in Dovecot's error logs?
http://wiki.dovecot.org/Logging
But you said other processes also eat 100% CPU, and LDAP doesn't explain
that.
[attachment "signature.asc" deleted by JackyC/UMAC]
here's something really wrong
in your installation. A few things that might show something useful:
1) strace -tt -p output for a 10 lines or so.
2) dovecot --build-options output
[attachment "signature.asc" deleted by JackyC/UMAC]
es
debug: yes
passdb:
driver: pam
userdb:
driver: passwd
Yours Sincerely,
Jacky Chan
From:
Charles Marcus
To:
dovecot@dovecot.org
Date:
06/04/2010 下午 06:57
Subject:
Re: [Dovecot] Timeout Value
Sent by:
dovecot-bounces+jackyc=umac...@dovecot.org
On 2010-04-06 12:13 AM, jac...@uma
Dear All,
I constantly encounter 'dovecot-auth', 'login-imap', 'login-pop3' and
'imap' processes consume 100% CPU.
I run 'ps' and found those hanged up processes were running for a long
time.
I am wondering whether dovecot.conf has some configuration parameters that
timeout those processes (or
Hi all,
I am running dovecot version 1.1.1 (dovecot --version) and keeps to have
time moved backwards problem.
I first found dovecot dead without obvious error message, but see the
following when restart dovecot service by
# service dovecot restart
>Stopping Dovecot Imap: [FAILED]
>Sta
