On 9/24/2010 5:27 AM, enid vx wrote:
and now, can you respond to Timos request for a backtrace:
On 2010-09-21 10:16 AM, Timo Sirainen<tss@iki.fi> wrote:
Are these coming only from pop3 processes? Are you running imap? It's anyway difficult to say anything about segfaults without a gdb backtrace. See http://dovecot.org/bugreport.html how to get one.
--
Hi all,
after the update I noticed that the error messages didn't go away for a little time. Also seeing the high load and high kernel cpu usage I did some changes to the /etc/fstab (adding noatime,nodiratime) to /var /home partitions. Also the dovecot -n now is like this: auth_mechanisms = plain login default_login_user = dovecot disable_plaintext_auth = no dotlock_use_excl = yes mail_access_groups = mail mail_fsync = never mail_location = mbox:~/.:INBOX=/var/mail/%u mmap_disable = yes passdb { driver = pam } ssl_cert =</etc/ssl/certs/dovecot.pem ssl_key =</etc/ssl/private/dovecot.pem userdb { driver = passwd }
I see that for about 2-3 days now the error has gone away, and dovecot is running ok, but the high load is continually present, and I suspect of disk I/O latency.
You might try running 'vmstat 2', 'iostat -x', etc.. It sounds to me like a disk i/o problem, but we are just guessing unless we know more about the hardware and utilization. A simple fix might be to add a fast local drive and move /var/mail to it's own spindle, assuming you don't have this configuration already.
Ken
Again thank you for your support. Enid
-- Ken Anderson Pacific Internet - http://www.pacific.net