[stork-users] Stork-Agent issue detecting Bind 9 config path

[Juliano Alves Guidini]

Hi!

I upgraded Stork Agent to v2.4.0 and observed this message on log:

Mar 04 16:15:31 dns-j01 stork-agent[25575]: time="2026-03-04 16:15:31"
level="warning" msg="Failed to detect BIND 9 DNS server daemon" file="
         monitor.go:427  " error="failed to detect BIND 9 config path:
cannot get file info for /etc/named.conf: stat /etc/named.conf: no
such file or directory" stackTrace="stat /etc/named.conf: no such file
or directory\ncannot get file info for
/etc/named.conf\nisc.org/stork/util.(*systemCommandExecutor).GetFileInfo\n\t/builds/isc-projects/stork/backend/util/executor.go:51\nisc.org/stork/agent.newDetectedDaemonFile\n\t/builds/isc-projects/stork/backend/agent/detectedfiles.go:41\nisc.org/stork/agent.(*detectedDaemonFiles).addFile\n\t/builds/isc-projects/stork/backend/agent/detectedfiles.go:98\nisc.org/stork/agent.(*monitor).detectBind9ConfigPaths\n\t/builds/isc-projects/stork/backend/agent/bind9.go:325\nisc.org/stork/agent.(*monitor).detectBind9Daemon\n\t/builds/isc-projects/stork/backend/agent/bind9.go:468\nisc.org/stork/agent.(*monitor).detectDaemons\n\t/builds/isc-projects/stork/backend/agent/monitor.go:425\nisc.org/stork/agent.(*monitor).run\n\t/builds/isc-projects/stork/backend/agent/monitor.go:319\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed
to detect BIND 9 config path"


When using version 2.2.1.250828143649 this does not occur, but on
version 2.4.0.260218163426 agent can't find named.conf.

My setup:

# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 13 (trixie)
Release:        13
Codename:       trixie

# rndc status
version: BIND 9.18.44 (Extended Support Version) <id:2e74eea>
running on localhost: Linux x86_64 6.12.73+deb13-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17)
boot time: Wed, 04 Mar 2026 17:51:33 GMT
last configured: Wed, 04 Mar 2026 17:51:33 GMT
configuration file: /etc/named.conf (/var/lib/named/etc/named.conf)
CPUs found: 4
worker threads: 4
UDP listeners per interface: 4
number of zones: 46 (16 automatic)
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is ON
recursive clients: 0/9900/10000
tcp clients: 0/3000
TCP high-water: 0
server is up and running

# ps -ef | grep named
bind        2917       1  0 14:51 ?        00:00:06
/var/lib/named/sbin/named -f -u bind -t /var/lib/named

# /var/lib/named/sbin/named -V
BIND 9.18.44 (Extended Support Version) <id:2e74eea>
running on Linux x86_64 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC
Debian 6.12.73-1 (2026-02-17)
built by make with  '--enable-symtable=none' '--enable-full-report'
'--with-libxml2' '--with-openssl' '--prefix=/var/lib/named'
'--exec-prefix=/var/lib/named' '--sysconfdir=/etc' '--enable-dnstap'
'--with-lmdb' '--with-libjson' '--with-python' '--with-maxminddb'
'--with-libidn2' '--disable-doh' '--with-json-c' '--with-zlib=no'
compiled by GCC 14.2.0
compiled with OpenSSL version: OpenSSL 3.5.4 30 Sep 2025
linked to OpenSSL version: OpenSSL 3.5.4 30 Sep 2025
compiled with libuv version: 1.50.0
linked to libuv version: 1.50.0
compiled with libxml2 version: 2.9.14
linked to libxml2 version: 20914
compiled with json-c version: 0.18
linked to json-c version: 0.18
linked to maxminddb version: 1.12.2
compiled with protobuf-c version: 1.5.1
linked to protobuf-c version: 1.5.1
threads support is enabled
DNSSEC algorithms: RSASHA1 NSEC3RSASHA1 RSASHA256 RSASHA512
ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448
DS algorithms: SHA-1 SHA-256 SHA-384
HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224 HMAC-SHA256
HMAC-SHA384 HMAC-SHA512
TKEY mode 2 support (Diffie-Hellman): yes
TKEY mode 3 support (GSS-API): no

default paths:
  named configuration:  /etc/named.conf
  rndc configuration:   /etc/rndc.conf
  DNSSEC root key:      /etc/bind.keys
  nsupdate session key: /var/lib/named/var/run/named/session.key
  named PID file:       /var/lib/named/var/run/named/named.pid
  named lock file:      /var/lib/named/var/run/named/named.lock
  geoip-directory:      /usr/share/GeoIP


Bind is not in the latest version on this machine, but is a test machine.

I noticed the same behavior on Debian 11 ( exactly same setup, only changed
OS version ).

Best Regards,

-- Juliano Alves Guidini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20260304/0907abc8/attachment.htm>