← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

 

Hi Brian,
these versions are actually already in Artful and Bionic.
Given the time you opened this you found that on Xenial I'll add a task for an SRU.

@Andreas - you look at bind fixes every now and then - how about to
include this on your next run?

** Also affects: bind9 (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: bind9 (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: bind9 (Ubuntu Xenial)
       Status: New => Triaged

-- 
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:
  Triaged
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