imapd signal 11 blues

Torsten Schlabach tschlabach at gmx.net
Tue Dec 18 02:28:34 EST 2007 

Hi John!

I had just the identical problem last night, but I was able to trace it 
down to a bug in the ldapdb auxprop module. You are not using that 
module, so that can't be it.

How would one do an strace on imapd to find out in what function call it 
dies? That might be an indication.

Regards,
Torsten

John Crawford schrieb:
> Hi.
>   I'm working on a freebsd test server (within vmware server),
> and am having some difficulty. imapd processes terminate abnormally.
> 
> imtest -m login -v -a cyradm -u cyradm localhost
> S: * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=LOGIN AUTH=PLAIN
> SASL-IR] virtualmail2.domain.edu Cyrus IMAP4 v2.3.11 server ready
> C: C01 CAPABILITY
> S: * CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=LOGIN AUTH=PLAIN SASL-IR
> ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME
> UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ
> THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE
> IDLE URLAUTH
> S: C01 OK Completed
> Please enter your password:
> C: L01 LOGIN cyradm {13}
> S: + go ahead
> C: <omitted>
> failure: prot layer failure
> 
> The saslauthd part is going fine. Seems to not want to talk nice to the
> imap server.
> # /usr/local/sbin/saslauthd -a pam -d
> saslauthd[14961] :main            : num_procs  : 5
> saslauthd[14961] :main            : mech_option: NULL
> saslauthd[14961] :main            : run_path   : /var/run/saslauthd
> saslauthd[14961] :main            : auth_mech  : pam
> saslauthd[14961] :ipc_init        : using accept lock file:
> /var/run/saslauthd/mux.accept
> saslauthd[14961] :detach_tty      : master pid is: 0
> saslauthd[14961] :ipc_init        : listening on socket:
> /var/run/saslauthd/mux
> saslauthd[14961] :main            : using process model
> saslauthd[14961] :have_baby       : forked child: 14962
> saslauthd[14962] :get_accept_lock : acquired accept lock
> saslauthd[14961] :have_baby       : forked child: 14963
> saslauthd[14961] :have_baby       : forked child: 14964
> saslauthd[14961] :have_baby       : forked child: 14965
> saslauthd[14961] :get_accept_lock : acquired accept lock
> saslauthd[14962] :rel_accept_lock : released accept lock
> saslauthd[14962] :do_auth         : auth success: [user=cyradm]
> [service=imap] [realm=] [mech=pam]
> saslauthd[14962] :do_request      : response: OK
> 
> I have similar problems with invoking cyradm, with the pam mechanism
> working but
> imap kicking it out.
> 
> # su cyrus
> %cyradm -u cyradm -auth plain localhost
> Password:
> IMAP Password: at
> /usr/local/lib/perl5/site_perl/5.8.8/mach/Cyrus/IMAP/Admin.pm line 119
> cyradm: cannot authenticate to server with plain as cyradm
> %cyradm -u cyradm -auth login localhost
> IMAP Password: at
> /usr/local/lib/perl5/site_perl/5.8.8/mach/Cyrus/IMAP/Admin.pm line 119
> cyradm: cannot authenticate to server with login as cyradm
> 
> newer syntax, both plain and login mechanisms
> %cyradm --user cyradm --auth plain localhost
> Password:
> IMAP Password: at
> /usr/local/lib/perl5/site_perl/5.8.8/mach/Cyrus/IMAP/Admin.pm line 119
> cyradm: cannot authenticate to server with plain as cyradm
> 
> %cyradm --user cyradm --auth login localhost
> IMAP Password: at
> /usr/local/lib/perl5/site_perl/5.8.8/mach/Cyrus/IMAP/Admin.pm line 119
> cyradm: cannot authenticate to server with login as cyradm
> 
> doing cyradm or imtest results in signal 11 for imapd (from cyradm example
> here)
> Dec 17 20:27:41 virtualmail2 saslauthd[14963]: get_accept_lock : acquired
> accept lock
> Dec 17 20:27:41 virtualmail2 saslauthd[14961]: rel_accept_lock : released
> accept lock
> Dec 17 20:27:41 virtualmail2 kernel: pid 25130 (imapd), uid 60: exited on
> signal 11
> Dec 17 20:27:41 virtualmail2 kernel: Dec 17 20:27:41 virtualmail2 kernel:
> pid 25130 (imapd), uid 60: exited on signal 11
> Dec 17 20:27:41 virtualmail2 saslauthd[14961]: pam_smb: Local UNIX
> username/password pair correct.
> Dec 17 20:27:41 virtualmail2 saslauthd[14961]: do_auth         : auth
> success: [user=cyradm] [service=imap] [realm=] [mech=pam]
> Dec 17 20:27:41 virtualmail2 saslauthd[14961]: do_request      : response: OK
> Dec 17 20:27:41 virtualmail2 master[1763]: process 25130 exited, signaled
> to death by 11
> Dec 17 20:27:41 virtualmail2 kernel: Dec 17 20:27:41 virtualmail2
> master[1763]: process 25130 exited, signaled to death by 11
> Dec 17 20:27:41 virtualmail2 master[1763]: service imap pid 25130 in BUSY
> state: terminated abnormally
> 
> The same death form shows in syslog upon imap connection login
> telnet localhost 143
> Trying ::1...
> Connected to localhost.
> Escape character is '^]'.
> * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=LOGIN AUTH=PLAIN
> SASL-IR] virtualmail2.domain.edu Cyrus IMAP4 v2.3.11 server ready
> a login cyradm pass
> Connection closed by foreign host.
> 
> 
> showing imapd.conf
> configdirectory: /var/imap
> partition-default: /var/spool/imap
> allowplaintext: 1
> admins: cyradm cliff cyrus
> sieveusehomedir: false
> sievedir: /var/imap/sieve
> sendmail: /var/somebinary
> sieve_maxscriptsize: 128
> sasl_minimum_layer: 0
> sasl_pwcheck_method: saslauthd
> sasl_mech_list: PLAIN LOGIN
> sasl_auto_transition: yes
> lmtp_tls_cert_file: disabled
> lmtp_tls_key_file: disabled
> sieve_tls_cert_file: disabled
> sieve_tls_key_file: disabled
> 
>   cyrus.conf
> START {
>    recover       cmd="ctl_cyrusdb -r"
> }
> SERVICES {
>    imap          cmd="imapd" listen="imap" prefork=0
>    imaps         cmd="imapd -s -C /usr/local/etc/imapd-ssl.conf"
> listen="imaps" prefork=0
>    pop3          cmd="pop3d" listen="pop3" prefork=0
>    pop3s         cmd="pop3d -s -C /usr/local/etc/imapd-ssl.conf"
> listen="pop3s" prefork=0
>    sieve         cmd="timsieved" listen="sieve" prefork=0
>    lmtpunix      cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
> }
> EVENTS {
>    checkpoint    cmd="ctl_cyrusdb -c" period=30
>    delprune      cmd="cyr_expire -E 3" at=0400
>    tlsprune      cmd="tls_prune" at=0400
>    squatter      cmd="squatter -sr user" at=0400
> }
> 
> 
> %cat /usr/local/lib/sasl2/Cyrus.conf
> pwcheck_method: saslauthd
> 
> 
> I installed cyrus-imap23 from FreeBSD ports, config.log shows
>    $ ./configure --sysconfdir=/usr/local/etc
> --with-cyrus-prefix=/usr/local/cyrus --with-cyrus-user=cyrus
> --with-cyrus-group=cyrus --with-sasl=/usr/local --with-bdb=db41
> --with-com_err=/usr
>   --with-openssl=/usr/local --with-perl=/usr/local/bin/perl5.8.8
> --with-bdb-incdir=/usr/local/include/db41
> --with-bdb-libdir=/usr/local/lib --with-snmp=no --prefix=/usr/local
> --mandir=/usr/local/man
>   --infodir=/usr/local/info/ i386-portbld-freebsd6.2
> 
> I had the same problems with cyrus-imap 2.2 in testing.
> Suggestions leading to understanding are welcome. I see
> some of the keywords in online searches of the archives,
> but I have I'm missing the issue in my understanding.
> Any helpful comments are welcome.
> 
> Thank you,
> John
> 
> 
> 
> 
> 
> 
> 
> ----
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

More information about the Info-cyrus mailing list