Thanks everyone for the responses. I rebuilt things yet again to make sure
that they are all pointing at the new DB in /usr/local (see the ldd outputs
below) and I have the same problem. I rebuilt cyrus-sasl as well and it is
also pointing at the /usr/local DB, and imapd is pointing to the new
libsasl.so.
One thing I have noticed now is that pam_ldap is NOT pointing to the new
libsasl.so (/usr/local/lib), it is still pointing to the old one (/usr/lib).
Any thoughts on if that would cause the failure? And any thoughts on how I
can get it to compile pointing to the /usr/local/lib location? I included
/usr/local/lib and /usr/local/include in CPPFLAGS and LDFLAGS when I
compiled, so I'm not sure what else to tweak.
I'd love to just uninstall all of the Berkeley DB and Cyrus-sasl stuff, but
since this is RedHat with all of its inter-dependent packages, I'm afraid if
I just force them out, the rest of the system will be unstable.
Thanks again. I'd love for this to work, but I'm close to giving up.
- John
[root@vmsurfrider /root]# ldd /usr/cyrus/bin/master
libssl.so.1 => /usr/lib/libssl.so.1 (0x40024000)
libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x40051000)
libdb-3.2.so => /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so (0x4010d000)
libc.so.6 => /lib/i686/libc.so.6 (0x401a4000)
libdl.so.2 => /lib/libdl.so.2 (0x402d4000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
[root@vmsurfrider /root]# ldd /usr/cyrus/bin/imapd
libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x40018000)
libssl.so.1 => /usr/lib/libssl.so.1 (0x4002e000)
libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x4005b000)
libdb-3.2.so => /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so (0x40117000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401ae000)
libc.so.6 => /lib/i686/libc.so.6 (0x401c5000)
libdl.so.2 => /lib/libdl.so.2 (0x402f5000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x402fa000)
libpam.so.0 => /lib/libpam.so.0 (0x40328000)
libresolv.so.2 => /lib/libresolv.so.2 (0x40330000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
[root@vmsurfrider /root]# ldd /usr/local/lib/libsasl.so.7
libdb-3.2.so => /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so (0x40017000)
libdl.so.2 => /lib/libdl.so.2 (0x400ae000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x400b2000)
libpam.so.0 => /lib/libpam.so.0 (0x400e0000)
libresolv.so.2 => /lib/libresolv.so.2 (0x400e8000)
libc.so.6 => /lib/i686/libc.so.6 (0x400fb000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
[root@vmsurfrider /root]# ldd /lib/security/pam_ldap.so
libldap.so.2 => /usr/lib/libldap.so.2 (0x40016000)
liblber.so.2 => /usr/lib/liblber.so.2 (0x40041000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x4004b000)
libresolv.so.2 => /lib/libresolv.so.2 (0x40079000)
libpam.so.0 => /lib/libpam.so.0 (0x4008c000)
libdl.so.2 => /lib/libdl.so.2 (0x40094000)
libc.so.6 => /lib/i686/libc.so.6 (0x40098000)
libsasl.so.7 => /usr/lib/libsasl.so.7 (0x401c9000)
libkrb4.so.2 => /usr/kerberos/lib/libkrb4.so.2 (0x401d3000)
libdes425.so.3 => /usr/kerberos/lib/libdes425.so.3 (0x401e7000)
libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x401eb000)
libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x40242000)
libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x40253000)
libssl.so.1 => /usr/lib/libssl.so.1 (0x40255000)
libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x40282000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
libdb-3.2.so => /usr/local/BerkeleyDB.3.2/lib/libdb-3.2.so (0x4033f000)
-----Original Message-----
From: Tarjei Huse [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 4:41 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Signaled to death by 11 - Don't know what else to try
Hi,
> I would sugges to have only one valid berkeley db version in your
> system (either 3.1 or 3.2), because otherwise you might encounter
> errors of the third art ;-) Especially on building cyrus imap I already
> found out, that it is better to have only one (and the most actual one)
Also, make sure that you build cyrus with the same version as you build
cyrus-sasl with. If using rh, i suggest getting the latest and greatest rpms
for rh7.1, and the src rpm for cyrus sasl. Then , -Uvh the db rpms, rpm -ba
cyrus-sasl.spec and the -Uvh the rpms. Thus you are sure there is nothing
wrong. Of course, the best solution is to build sasl from src. Also, if
ldap, use the ldap sasl patch.
To the fine men (and women) coding the sasl 2.0 libs. PLEASE include ldap
auth support!!!!!
____________________
Tarjei Huse
920 63 413
