Re: cyradm login loops
Occasionally, I see something mentioned about tracing a particular cyrus process to determine what's going on (or wrong, as the case may be). How is this done? I'm not getting very far at resolving my particular problem, so I'd like to know what the proxyd process thinks it's doing each time it spawns a new connection to itself. Rob On 7/1/11 9:10 AM, Robert Spellman wrote: We have recently upgraded to cyrus 2.4.6. Our environment includes a server running as a murder server, four back end mailstores, and two front end servers. If we mistakenly create a user mailbox on one of the front end servers using cyradm, and then try to manage it (dm, sam, info, lm), cpu load on the front end server increases until the box is unusable. Syslogs show the user cyrus (our admin user) logging in over and over, each time creating a new proxyd process, which explains the high cpu load. Managing mailboxes on the back end servers from the front end servers works fine. Here's my imapd.conf for one of my front end servers: configdirectory: /var/lib/imap partition-default: /home/imap defaultpartition: default sievedir: /var/lib/imap/sieve admins: cyrus backend sasl_pwcheck_method: saslauthd sasl_mech_list: PLAIN GSSAPI altnamespace: true hashimapspool: true allowallsubscribe: true allowusermoves: true autocreateinboxfolders: Trash|Sent|Junk autosubscribeinboxfolders: Trash|Sent|Junk autosubscribesharedfolders: shared.announce lmtp_downcase_rcpt: true tls_cert_file: /etc/pki/tls/certs/mail.bates.edu-cert.pem tls_key_file: /etc/pki/tls/certs/mail.bates.edu-key.pem tls_ca_file: /etc/pki/tls/certs/bates.edu-cert.pem proxy_authname: backend proxyservers: backend mupdate_server: murder.bates.edu mupdate_username: backend Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ attachment: rspell.vcf Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: cyradm login loops
See: http://stuff.mit.edu/afs/sipb/project/linerva/project/packages/cyrus/cyrus21-imapd-2.1.18/debian/README.Debian.debug On 05/07/11 13:38 -0400, Robert Spellman wrote: Occasionally, I see something mentioned about tracing a particular cyrus process to determine what's going on (or wrong, as the case may be). How is this done? I'm not getting very far at resolving my particular problem, so I'd like to know what the proxyd process thinks it's doing each time it spawns a new connection to itself. Rob On 7/1/11 9:10 AM, Robert Spellman wrote: We have recently upgraded to cyrus 2.4.6. Our environment includes a server running as a murder server, four back end mailstores, and two front end servers. If we mistakenly create a user mailbox on one of the front end servers using cyradm, and then try to manage it (dm, sam, info, lm), cpu load on the front end server increases until the box is unusable. Syslogs show the user cyrus (our admin user) logging in over and over, each time creating a new proxyd process, which explains the high cpu load. Managing mailboxes on the back end servers from the front end servers works fine. Here's my imapd.conf for one of my front end servers: configdirectory: /var/lib/imap partition-default: /home/imap defaultpartition: default sievedir: /var/lib/imap/sieve admins: cyrus backend sasl_pwcheck_method: saslauthd sasl_mech_list: PLAIN GSSAPI altnamespace: true hashimapspool: true allowallsubscribe: true allowusermoves: true autocreateinboxfolders: Trash|Sent|Junk autosubscribeinboxfolders: Trash|Sent|Junk autosubscribesharedfolders: shared.announce lmtp_downcase_rcpt: true tls_cert_file: /etc/pki/tls/certs/mail.bates.edu-cert.pem tls_key_file: /etc/pki/tls/certs/mail.bates.edu-key.pem tls_ca_file: /etc/pki/tls/certs/bates.edu-cert.pem proxy_authname: backend proxyservers: backend mupdate_server: murder.bates.edu mupdate_username: backend Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ begin:vcard fn:Robert Spellman n:Spellman;Robert org:Bates College;Information and Library Services adr;dom:;;110 Russell Street;Lewiston;Maine;04240 email;internet:rsp...@bates.edu title:Assistant Directory, Network Services tel;work:207-786-6422 note;quoted-printable:01000111011000100101001001100101011001000101001101100= 011=0D=0A= url:http://www.bates.edu/ version:2.1 end:vcard Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ -- Dan White Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Cyrus 2.4.10 Released
We are pleased to announce the release of Cyrus IMAPd 2.4.10. This is a stable release in the 2.4.x series, fixing a few bugs found since the release of 2.4.9, and also adding some new features. We recommend that all users of the 2.4 series update to this release. NOTE: there is a known bug in the new SORT=DISPLAY feature, which means that non-ASCII characters can sort incorrectly. NOTE: the quota -f bug mentioned in the 2.4.9 release notes is now fixed. *** with 2.4.10 (and later) you only need run 'quota -f' once *** The list of reported bugs fixed can be found here: http://cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.10 (or check the changelog for the ones that were actually FIXED in this release rather than closed as no-longer-present) If you want extreme detail of all changes made, check git: http://git.cyrusimap.org/cyrus-imapd/log/?id=cyrus-imapd-2.4.10 You can download via HTTP or FTP: http://cyrusimap.org/releases/cyrus-imapd-2.4.10.tar.gz ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.10.tar.gz Regards, Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
