Greets Again.
Following up on my previous email I've now got a core file from cyrus
2.0.14. This comes from a sig 11 of imapd during auth from my previously
posted hurtme.php script. My current config is listed in the previous email
as well:
[root@oggvorbis test1]# gdb /usr/cyrus/bin/imapd core
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `/usr/cyrus/bin/imapd'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/libsasl.so.7...done.
Reading symbols from /usr/lib/libssl.so.1...done.
Reading symbols from /usr/lib/libcrypto.so.1...done.
Reading symbols from /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so...done.
Reading symbols from /lib/libnsl.so.1...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /lib/libcrypt.so.1...done.
Reading symbols from /lib/libresolv.so.2...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /usr/lib/sasl/libcrammd5.so...done.
Reading symbols from /usr/lib/sasl/libdigestmd5.so...done.
Reading symbols from /usr/lib/sasl/libanonymous.so...done.
Reading symbols from /usr/lib/sasl/libplain.so...done.
Reading symbols from /usr/lib/sasl/liblogin.so...done.
Reading symbols from /lib/libnss_files.so.2...done.
Reading symbols from /lib/libnss_nisplus.so.2...done.
Reading symbols from /lib/libnss_nis.so.2...done.
#0 0x402156e9 in chunk_alloc (ar_ptr=0x402aad40, nb=24) at malloc.c:2763
2763 malloc.c: No such file or directory.
(gdb) bt
#0 0x402156e9 in chunk_alloc (ar_ptr=0x402aad40, nb=24) at malloc.c:2763
#1 0x402155ae in __libc_malloc (bytes=16) at malloc.c:2696
#2 0x4018240f in __os_malloc () from /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so
#3 0x40162d6c in __ham_db_create () from /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so
#4 0x40143d29 in __db_init () from /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so
#5 0x4014399d in db_create () from /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so
#6 0x4001c9d3 in berkeleydb_open (conn=0x810ccf0, rdwr=0, mbdb=0xbffff064) at
db_berkeley.c:85
#7 0x4001cc4b in getsecret (context=0x810ccf0, mechanism=0x40021009 "CRAM-MD5",
auth_identity=0x810d218 "test8Å\020\b3", realm=0x810d1f8 "oggvorbis.raleigh.ibm.com",
secret=0xbffff110) at db_berkeley.c:191
#8 0x400202a6 in server_continue_step (conn_context=0x810cf08, sparams=0x810d188,
clientin=0x810d0f8 "test1 52f7adc6c6dd31082baff2e5ff4cb0e1", clientinlen=38,
serverout=0xbffff250, serveroutlen=0xbffff254, oparams=0x810cd34,
errstr=0xbffff258) at cram.c:476
#9 0x40019e4a in sasl_server_step (conn=0x810ccf0, clientin=0x810d0f8 "test1
52f7adc6c6dd31082baff2e5ff4cb0e1", clientinlen=38, serverout=0xbffff250,
serveroutlen=0xbffff254, errstr=0xbffff258) at server.c:1029
#10 0x804f3be in cmd_authenticate (tag=0x810cf88 "00000001", authtype=0x810d068
"CRAM-MD5") at imapd.c:1549
#11 0x804d234 in cmdloop () at imapd.c:727
#12 0x804cda2 in service_main (argc=1, argv=0xbffffb44, envp=0xbffffb4c) at imapd.c:545
#13 0x804bb92 in main (argc=1, argv=0xbffffb44, envp=0xbffffb4c) at service.c:285
On Thu, Jul 05, 2001 at 12:01:20PM -0400, Scott Russell wrote:
> All -
>
> I'm new to Cyrus and have been experiencing sig 11 issues on imapd over the
> past 2 weeks. I've spent a great deal of time reading the list archives
> trying to id the root cause. So far it hasn't been pretty but I've boiled
> down to the following info.
>
> Current Config:
>
> Red Hat 6.2 + errata
> BerkeleyDB 3.2 (From tgz source)
> Cyrus IMAPd 2.0.13 vs 2.0.14 (From tgz source)
> Cyrus sasl 1.5.24 (From tgz source)
>
> Compile options for Cyrus IMAPd:
>
> ./configure --with-dbdir=/usr/local/BerkeleyDB.3.2 --enable-netscapehack
> --without-ucdsnmp -without-krb --with-perl --with-libwrap --with-openssl
> --with-com_err=/usr --with-cyrus-user=cyrus --with-cyrus-group=mail
>
> Summary:
>
> On RH6.2 cyrus-imapd 2.0.14 fails with sig11 errors on imapd. This can be
> seen with that attached php 4.0.5 script "hurtme.php". In my case about
> 1/3 of the logins would fail due to imapd sig 11.
>
> On the same box cyrus-imapd 2.0.13 works fine. (NOTE: After I built 2.0.13 I didn't
> install it. I just took the imap/imapd binary and replaced the existing
> cyrus-2.0.14 imapd binary found in /usr/cyrus/bin. In effect only the imapd
> was from cyrus 2.0.13, all other bins / scripts were from cyrus 2.0.14.)
>
> Conclusion:
>
> Something introduced into imapd.c between 2.0.13 and 2.0.14 is causing imapd
> to sig 11 on Red Hat 6.2 (And possibly Red Hat 7.1). A diff between the two
> files shows several changes but I don't have enough experience to spot the
> root cause. No core files are generated when a sig 11 happens so a gdb trace
> isn't available.
>
> If anyone wants to provide me with a patch against imapd for 2.0.14 that I
> can test I'll be happy to do it and report the results.
>
> On another note it's a shame that so many sig 11 problems with cyrus 2.0.xx
> exist. It seems like a really nice closed box IMAPd solution and I hope the
> developers concentrate on code cleanups and stability issues for the next
> release.
--
Regards,
Scott Russell ([EMAIL PROTECTED])
Linux Technology Center, System Admin, RHCE.
T/L 441-9289 / External 919-543-9289
http://bzimage.raleigh.ibm.com/webcam
