LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   bind-9.9.1-P2 in chroot-jail won't start, "initializing DST: openssl failure" (http://www.linuxquestions.org/questions/slackware-14/bind-9-9-1-p2-in-chroot-jail-wont-start-initializing-dst-openssl-failure-4175419314/)

wailingwailer 07-30-2012 03:48 AM

bind-9.9.1-P2 in chroot-jail won't start, "initializing DST: openssl failure"
 
after updating to the new bind-9.9.1-P2 (using slackware64-current a.k.a. slackware64-14.0_beta), I could not get bind to start in a chroot-jail. in troubleshooting this problem, I tried rebuilding bind from source, reinstalling the binary packages, and regenerating the server host key for signed zone transfers.

then, after some googling I found this fix for bind in a chroot-jail on bsd which seems to allow bind to start up without complaining.

http://snarfu.com/freebsd/freebsd-bi...l-failure-fix/

I needed to adjust the path names from the bsd path
Code:

/usr/local/lib/engines
to the slackware64 path
Code:

/usr/lib64/engines
so I ended up running,
Code:

# mkdir -p /chroot/named/usr/lib64/engines
# cp -av /usr/lib64/engines/libgost.so /chroot/named/usr/lib64/engines

however, I wanted to ask if anyone here might know of any relevant configuration or runtime options that could be used instead of copying the .so file or if anyone had a better solution. thanks.


All times are GMT -5. The time now is 06:31 AM.