Steve Jacobson wrote:
All,I had a successful installation of FDS 1.1 on CentOS 5.1 x86_64. I had a bunch of cruft in the directory from a poor migration, so I decided to start over with a re-install to get things clean. The uninstall was successful, and I wiped /etc/dirsrv, /var/lib/dirsrv, and /usr/share/dirsrv.
Also /usr/lib64/dirsrv/slapd*
Then I re-installed, and ran setup-ds-admin.pl. The dialogs were as expected, and seemed to be just fine. The setup program reported that everything was fine, and the directory was created. However, the domain didn’t materialize. There was nothing in the setup log to hint at any problem. I found the following messages in /var/log/messages:Mar 5 19:20:38 corp-admin-001 ns-slapd: unable to dlopen /usr/lib/sasl2/libcrammd5.so.2: /usr/lib/sasl2/libcrammd5.so.2: wrong ELF class: ELFCLASS32 Mar 5 19:20:38 corp-admin-001 ns-slapd: unable to dlopen /usr/lib/sasl2/libanonymous.so.2: /usr/lib/sasl2/libanonymous.so.2: wrong ELF class: ELFCLASS32 Mar 5 19:20:38 corp-admin-001 ns-slapd: unable to dlopen /usr/lib/sasl2/libplain.so.2: /usr/lib/sasl2/libplain.so.2: wrong ELF class: ELFCLASS32 Mar 5 19:20:38 corp-admin-001 ns-slapd: unable to dlopen /usr/lib/sasl2/libgssapiv2.so.2: /usr/lib/sasl2/libgssapiv2.so.2: wrong ELF class: ELFCLASS32 Mar 5 19:20:38 corp-admin-001 ns-slapd: unable to dlopen /usr/lib/sasl2/liblogin.so.2: /usr/lib/sasl2/liblogin.so.2: wrong ELF class: ELFCLASS32 Mar 5 19:20:38 corp-admin-001 ns-slapd: unable to dlopen /usr/lib/sasl2/libdigestmd5.so.2: /usr/lib/sasl2/libdigestmd5.so.2: wrong ELF class: ELFCLASS32So, this implies that ns-slapd is trying to get at the 32 bit libraries instead of the 64 bit versions.
I'm assuming you have the 64-bit versions of the sasl package installed?
rpm -qa --queryformat '%{name}-%{version}.%{arch}\n' | grep sasl
I tried setting LD_LIBRARY_PATH to /usr/lib64, I’ve tried renaming /usr/lib/sasl2 to get it out of the path, hoping the software would just find the right version.After these two attempts, the setup procedure created without generating any error messages. However, the domain still failed to be created.
I'm not sure what you mean by "domain" in this context.If you can, try starting over from scratch, and running setup-ds-admin.pl -ddd to generate verbose debug logs. By default the log file is written to /tmp/setupXXXXX.log
Any advice on where to look, or what else to try? Thanks! -steve j -- * **Steve Jacobson* • *Cozi * • IT Manager • m: 206.310.7760 • www.cozi.com ------------------------------------------------------------------------ -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
<<attachment: smime.p7s>>
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
