Huge load after update from 2.3.16 to 2.4.12
Dan White
dwhite at olp.net
Wed Nov 23 13:41:36 EST 2011
On 23/11/11 19:18 +0100, Michael Plate wrote:
>Hi,
>
>I just updated Cyrus Imapd on our somewhat old mailsever (dual-Xeon, but
>8 years now, running gentoo linux) from 2.3.16 to 2.4.12
>
>(options USE="berkdb kerberos pam replication sieve snmp sqlite ssl tcpd
>-afs -mysql -nntp -postgres")
>
>There is no murder and I also could drop sqlite, if better.
>
>After the flawless update, restarting generated a huge load. I believe I
>never had a load of > 50 any time before.
>It even gets "/var/imap/socket/lmtp] timed out while sending MAIL FROM"
>on local delivery of mails.
>
>
>This is cyrus.conf:
>
>START {
> # do not delete this entry!
> recover cmd="ctl_cyrusdb -r"
>
> # this is only necessary if using idled for IMAP IDLE
># idled cmd="idled"
>}
>
># UNIX sockets start with a slash and are put into /var/imap/socket
>SERVICES {
> # add or remove based on preferences
> imap cmd="imapd" listen="127.0.0.1:imap2" prefork=2
> #pop3 cmd="pop3d" listen="pop-3" prefork=0
> # Don't forget to generate the needed keys for SSL or TLS
> # (see doc/html/install-configure.html)
> imaps cmd="imapd -s" listen="imaps" prefork=15
> #pop3s cmd="pop3d -s" listen="pop3s" prefork=0
> sieve cmd="timsieved " listen="sieve" prefork=15
>
> # at least one LMTP is required for delivery
> lmtp cmd="lmtpd -a -D" listen="127.0.0.1:lmtp" prefork=1
> lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=2
>
> # this is only necessary if using notifications
> notify cmd="notifyd" listen="/var/imap/socket/notify"
>proto="udp" prefork=1
>}
>
>EVENTS {
> # this is required
> checkpoint cmd="ctl_cyrusdb -c" period=5
>
> # this is only necessary if using duplicate delivery suppression
># delprune cmd="ctl_deliver -E 3" period=1440
> delprune cmd="cyr_expire -E 3 -x" period=1440
>
> # this is only necessary if caching TLS sessions
> tlsprune cmd="tls_prune" period=1440 at=0600
>
> # squatter indiziert die Boxen fuer die Suche
> squatter cmd="squatter -r -s user" period=1440 at=0200
>}
>
>and imapd.conf:
>
>proxyservers: cyrus
>configdirectory: /var/imap
>partition-default: /var/imap/part
>sievedir: /var/imap/sieve
>
>sieve_sasl_mech_list: PLAIN
>
>tls_cert_file: /etc/cyrusimapd/server2009.pem
>tls_key_file: /etc/cyrusimapd/server2009.pem
>tls_ca_file: /etc/cyrusimapd/server2009.pem
>
>
>duplicate_db: skiplist
>mboxlist_db: skiplist
>quota_db: quotalegacy
>tlscache_db:skiplist
>
>
>admins: cyrus
>
>hashimapspool: yes
>allowanonymouslogin: no
>allowplaintext: yes
>allowusermoves: yes
>
># Use this if sieve-scripts could be in ~user/.sieve.
>#sieveusehomedir: yes
>
># Use saslauthd if you want to use pam for imap.
># But be warned: login with DIGEST-MD5 or CRAM-MD5
># is not possible using pam.
>sasl_pwcheck_method: saslauthd
>sasl_mech_list: LOGIN PLAIN
>autocreatequota: 15000000
>altnamespace: yes
>sasl_auto_transition: no
>quotawarn: 90
>
>
>tls_cipher_list: TLSv1:SSLv3:SSLv2:!NULL:!EXPORT:!DES:!LOW:@STRENGTH
>
>
>allowallsubscribe: no
>unixhierarchysep: yes
>lmtp_downcase_rcpt: yes
>
>annotation_db: skiplist
>seenstate_db: flat
>notifysocket: /var/imap/socket/notify
>
>I have backups of the old packages, but I'man not shure if this will
>work anymore.
>
>Any ideas please ? My bloodpressure can't stand this...
When performing an upgrade from earlier than 2.4.3, all messages are
reparsed, and your cache files are re-generated, when a mailbox is first
opened. You may be able to increase you syslogging levels to get a better
view into what's going on:
http://www.cyrusimap.org/docs/cyrus-imapd/2.4.12/install-configure.php
For other possible upgrade issues, see
http://www.cyrusimap.org/docs/cyrus-imapd/2.4.12/install-upgrade.php
--
Dan White
More information about the Info-cyrus
mailing list