Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unbound-helper root_trust_anchor_update fails without notice what happened #815

Closed
emdete opened this issue Dec 29, 2022 · 4 comments
Closed

Comments

@emdete
Copy link

emdete commented Dec 29, 2022

Describe the bug

when issuing /usr/libexec/unbound-helper root_trust_anchor_update it may fail (exit code 1) but doesnt tell what happened.

strace shows that it tries (unconditionally it seems, the config has a different path) to read and write to /usr/share/dns/root.key and /usr/share/dns doesnt exist.

To reproduce
Steps to reproduce the behavior:

  1. run /usr/libexec/unbound-helper root_trust_anchor_update
  2. alternativly watch what happens with strace /usr/libexec/unbound-helper root_trust_anchor_update

Expected behavior

the file to be generated.

System:

  • OS: Devuan ceres
  • unbound -V output:
Version 1.17.0

Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --with-pythonmodule --with-pyunbound --enable-subnet --enable-dnstap --enable-systemd --with-libnghttp2 --with-chroot-dir= --with-dnstap-socket-path=/run/dnstap.sock --disable-rpath --with-pidfile=/run/unbound.pid --with-libevent --enable-tfo-client --with-rootkey-file=/usr/share/dns/root.key --enable-tfo-server
Linked libs: libevent 2.1.12-stable (it uses epoll), OpenSSL 3.0.7 1 Nov 2022
Linked modules: dns64 python subnetcache respip validator iterator
TCP Fastopen feature available

Additional information

in fact this are two problems: the wrong path and the missing logging.

@Jakker
Copy link
Contributor

Jakker commented Dec 30, 2022 via email

@emdete
Copy link
Author

emdete commented Dec 30, 2022

Sorry, in that case it seems to be a debian packaging problem, unbound-anchor is not part of the package it seems.

@max-aigner
Copy link

apt install unbound unbound-anchor

@DaDummy
Copy link

DaDummy commented Jan 27, 2024

Looks like there is a packaging mistake in the current Debian package version of unbound-anchor as it does not create the directory /usr/share/dns, which then causes invocations to unbound-anchor to fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants