https://bugzilla.novell.com/show_bug.cgi?id=726453 https://bugzilla.novell.com/show_bug.cgi?id=726453#c0 Summary: 64-bit BIND fails to start in chroot when both 32- and 64-bit openssl libs are installed Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: schuetzm@gmx.net QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=458808) --> (http://bugzilla.novell.com/attachment.cgi?id=458808) trivial correction in /etc/init.d/named User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 /etc/init.d/named contains code to setup the chroot for BIND. There, the files from /lib/engines or /lib64/engines resp. are copied. Because the code checks for the 32-bit libs first, and the copying of the 64-bit libs is in the "else" branch, the 64-bit libs are never copied if the 32-bit ones happen to be installed. Patch attached. Reproducible: Always Steps to Reproduce: 1. zypper install libopenssl1_0_0-1.0.0e-33.1.x86_64 libopenssl1_0_0-32bit-1.0.0e-33.1.x86_64 bind bind-chrootenv 2. set NAMED_CHROOT_ENV in /etc/sysconfig/named 3. rcnamed start Actual Results: start of named fails with message "initializing DST: openssl failure" Expected Results: start of named succeeds -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.