group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #40532
[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"
[Xenial has reached its end of standard support.]
** Changed in: bind9 (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1630025
Title:
Fails running In chroot with "ENGINE_by_id failed (crypto failure)"
Status in BIND:
New
Status in bind9 package in Ubuntu:
Fix Released
Status in bind9 source package in Xenial:
Won't Fix
Status in bind9 package in Debian:
Fix Released
Bug description:
Running inside an OpenVZ guest, it is not possible to use the AppArmor
as discussed, so I am trying to configure BIND9 to run in chroot.
Then I got the following in the log:
named[3398]: ENGINE_by_id failed (crypto failure)
named[3398]: error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233:
named[3398]: error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:467:
named[3398]: error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:390:id=gost
named[3398]: initializing DST: crypto failure
named[3398]: exiting (due to fatal error)
systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE
This seems to be a bug that is found in Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820974
To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions