<div dir="ltr"><div><br clear="all"></div><div>Hi Ankney, thanks by help!<br><br>I viewed this issues, #974 opened some years ago by me. Finded #1217 , but is an old version of stork agent, and version 2.2.1.250828143649 worked well all the time with chroot on bind (-t).<br><br>Before a mailed this list i tested with STORK_AGENT_BIND9_CONFIG=/etc/named.conf on /etc/stork/agent.env, sorry to forget to relate this before.<br><br>Testing now with -c on Bind:<br><br># Before:<br># ps -ef | grep named<br>bind 461508 1 0 Mar05 ? 00:00:47 /var/lib/named/sbin/named -f -u bind -t /var/lib/named<br><br># After:<br># ps -ef | grep named<br>bind 630919 1 0 08:56 ? 00:00:00 /var/lib/named/sbin/named -f -u bind -t /var/lib/named -c /etc/named.conf<br><br># ps -ef | grep stork<br>stork-a+ 631687 1 0 08:59 ? 00:00:00 /usr/bin/stork-agent<br><br># rndc status<br>version: BIND 9.18.44 (Extended Support Version) <id:2e74eea><br>running on localhost: Linux x86_64 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17)<br>boot time: Fri, 06 Mar 2026 11:56:27 GMT<br>last configured: Fri, 06 Mar 2026 11:56:27 GMT<br>configuration file: /etc/named.conf (/var/lib/named/etc/named.conf)<br>CPUs found: 4<br>worker threads: 4<br>UDP listeners per interface: 4<br>number of zones: 46 (16 automatic)<br>debug level: 0<br>xfers running: 0<br>xfers deferred: 0<br>soa queries in progress: 0<br>query logging is ON<br>recursive clients: 0/9900/10000<br>tcp clients: 0/3000<br>TCP high-water: 0<br>server is up and running<br><br><br>Stork Log (STORK_LOG_LEVEL=WARN):<br><br>Mar 06 09:01:04 dns-j01 stork-agent[631687]: time="2026-03-06 09:01:04" 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\<a href="http://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">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</a> to detect BIND 9 config path"<br><br><br>Stork Log (STORK_LOG_LEVEL=DEBUG) - The newlines on logs were introduced by me, to clear view.<br><br><br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="debug" msg="Profiler is not available in this build" file=" disabled.go:10 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Starting Stork Agent, version 2.4.0, build date 2026-02-18 16:31" file=" main.go:48 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="=============================================================================" file=" register.go:450 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="AGENT TOKEN: FBE852A6279452B3FB3B2AC42FC2114AD558D32F7EEED51A577E18B46FFEAF75" file=" register.go:451 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="=============================================================================" file=" register.go:452 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Authorize the machine in the Stork web UI" file=" register.go:455 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Try to register agent in Stork Server" file=" register.go:468 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Machine already registered" file=" register.go:325 " machineID="20"<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="The GRPC credentials will be used as the client TLS certificate when connecting to Kea" file=" main.go:109 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Started daemon monitor" file=" monitor.go:293 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Per-subnet statistics are enabled. You may consider turning it off if you observe the performance problems for Kea deployments with many subnets." file=" promkeaexporter.go:389 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Prometheus Kea Exporter listening on <a href="http://0.0.0.0:9547">0.0.0.0:9547</a>" file=" promkeaexporter.go:627 "<br><br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="debug" msg="Looking for BIND 9 config file in -c parameter of a running process." file=" bind9.go:255 "<br><br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="debug" msg="Looking for BIND 9 config file in output of `named -V`." file=" bind9.go:293 "<br><br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" 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\<a href="http://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:299\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed">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:299\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed</a> to detect BIND 9 config path"<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="warning" msg="No daemon detected for monitoring; please check if they are running, and Stork can communicate with them." file=" monitor.go:451 "<br><br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Prometheus BIND 9 Exporter listening on <a href="http://0.0.0.0:9119">0.0.0.0:9119</a>" file="prombind9exporter.go:915 "<br>Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="Started serving Stork Agent" file=" agent.go:1000 " address="<a href="http://10.2.0.194:8080">10.2.0.194:8080</a>"<br><br>Mar 06 09:01:51 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:51" level="debug" msg="Looking for BIND 9 config file in -c parameter of a running process." file=" bind9.go:255 "<br>Mar 06 09:01:51 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:51" level="debug" msg="Looking for BIND 9 config file in output of `named -V`." file=" bind9.go:293 "<br>Mar 06 09:01:51 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:51" 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\<a href="http://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">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</a> to detect BIND 9 config path"<br><br>Mar 06 09:01:53 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:53" level="info" msg="Loaded server cert" file=" agent.go:127 "<br>Mar 06 09:01:53 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:53" level="info" msg="Loaded CA cert" file=" agent.go:110 "<br><br><br>Not working yet. <br><br>Added STORK_AGENT_BIND9_CONFIG=/etc/named.conf on /etc/stork/agent.env and not removed -c from bind. Same result, see logs.<br><br><br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="debug" msg="Profiler is not available in this build" file=" disabled.go:10 "<br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="Starting Stork Agent, version 2.4.0, build date 2026-02-18 16:31" file=" main.go:48 "<br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="=============================================================================" file=" register.go:450 "<br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="AGENT TOKEN: FBE852A6279452B3FB3B2AC42FC2114AD558D32F7EEED51A577E18B46FFEAF75" file=" register.go:451 "<br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="=============================================================================" file=" register.go:452 "<br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="Authorize the machine in the Stork web UI" file=" register.go:455 "<br>Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="Try to register agent in Stork Server" file=" register.go:468 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Machine already registered" file=" register.go:325 " machineID="20"<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="The GRPC credentials will be used as the client TLS certificate when connecting to Kea" file=" main.go:109 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Started daemon monitor" file=" monitor.go:293 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Per-subnet statistics are enabled. You may consider turning it off if you observe the performance problems for Kea deployments with many subnets." file=" promkeaexporter.go:389 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Prometheus Kea Exporter listening on <a href="http://0.0.0.0:9547">0.0.0.0:9547</a>" file=" promkeaexporter.go:627 "<br><br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="debug" msg="Looking for BIND 9 config file in -c parameter of a running process." file=" bind9.go:255 "<br><br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="debug" msg="Looking for BIND 9 config in /etc/named.conf as explicitly specified in settings." file=" bind9.go:270 "<br><br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="error" msg="File explicitly specified in settings (/etc/named.conf) not found or unreadable." file=" bind9.go:278 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="debug" msg="Looking for BIND 9 config file in output of `named -V`." file=" bind9.go:293 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" 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\<a href="http://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:299\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed">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:299\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed</a> to detect BIND 9 config path"<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="warning" msg="No daemon detected for monitoring; please check if they are running, and Stork can communicate with them." file=" monitor.go:451 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Prometheus BIND 9 Exporter listening on <a href="http://0.0.0.0:9119">0.0.0.0:9119</a>" file="prombind9exporter.go:915 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Started serving Stork Agent" file=" agent.go:1000 " address="<a href="http://10.2.0.194:8080">10.2.0.194:8080</a>"<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Loaded server cert" file=" agent.go:127 "<br>Mar 06 09:11:37 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:37" level="info" msg="Loaded CA cert" file=" agent.go:110 "<br><br><br>Removed -c from bind but not removed STORK_AGENT_BIND9_CONFIG=/etc/named.conf from /etc/stork/agent.env. Same result, see logs.<br><br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="debug" msg="Profiler is not available in this build" file=" disabled.go:10 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Starting Stork Agent, version 2.4.0, build date 2026-02-18 16:31" file=" main.go:48 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="=============================================================================" file=" register.go:450 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="AGENT TOKEN: FBE852A6279452B3FB3B2AC42FC2114AD558D32F7EEED51A577E18B46FFEAF75" file=" register.go:451 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="=============================================================================" file=" register.go:452 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Authorize the machine in the Stork web UI" file=" register.go:455 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Try to register agent in Stork Server" file=" register.go:468 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Machine already registered" file=" register.go:325 " machineID="20"<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="The GRPC credentials will be used as the client TLS certificate when connecting to Kea" file=" main.go:109 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Started daemon monitor" file=" monitor.go:293 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Per-subnet statistics are enabled. You may consider turning it off if you observe the performance problems for Kea deployments with many subnets." file=" promkeaexporter.go:389 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Prometheus Kea Exporter listening on <a href="http://0.0.0.0:9547">0.0.0.0:9547</a>" file=" promkeaexporter.go:627 "<br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="debug" msg="Looking for BIND 9 config file in -c parameter of a running process." file=" bind9.go:255 "<br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="debug" msg="Looking for BIND 9 config in /etc/named.conf as explicitly specified in settings." file=" bind9.go:270 "<br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="error" msg="File explicitly specified in settings (/etc/named.conf) not found or unreadable." file=" bind9.go:278 "<br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="debug" msg="Looking for BIND 9 config file in output of `named -V`." file=" bind9.go:293 "<br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" 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\<a href="http://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:299\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed">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:299\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693\nfailed</a> to detect BIND 9 config path"<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="warning" msg="No daemon detected for monitoring; please check if they are running, and Stork can communicate with them." file=" monitor.go:451 "<br><br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Prometheus BIND 9 Exporter listening on <a href="http://0.0.0.0:9119">0.0.0.0:9119</a>" file="prombind9exporter.go:915 "<br>Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="Started serving Stork Agent" file=" agent.go:1000 " address="<a href="http://10.2.0.194:8080">10.2.0.194:8080</a>"<br><br><br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" level="debug" msg="Looking for BIND 9 config file in -c parameter of a running process." file=" bind9.go:255 "<br><br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" level="debug" msg="Looking for BIND 9 config in /etc/named.conf as explicitly specified in settings." file=" bind9.go:270 "<br><br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" level="error" msg="File explicitly specified in settings (/etc/named.conf) not found or unreadable." file=" bind9.go:278 "<br><br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" level="debug" msg="Looking for BIND 9 config file in output of `named -V`." file=" bind9.go:293 "<br><br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" 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\<a href="http://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">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</a> to detect BIND 9 config path"<br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" level="info" msg="Loaded server cert" file=" agent.go:127 "<br>Mar 06 09:17:27 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:27" level="info" msg="Loaded CA cert" file=" agent.go:110 "<br><br><br>Many Thanks!</div><div><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div><div><font color="#000000" face="Helvetica"><span style="font-size:12px">-- Juliano Alves Guidini</span></font></div></div><div><br></div></div></div></div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Em sex., 6 de mar. de 2026 às 07:06, Darren Ankney <<a href="mailto:darren.ankney@gmail.com">darren.ankney@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
It may well be the `-t ` that is preventing the successful connection.<br>
There is an issue about it:<br>
<a href="https://gitlab.isc.org/isc-projects/stork/-/issues/1217" rel="noreferrer" target="_blank">https://gitlab.isc.org/isc-projects/stork/-/issues/1217</a> This closed<br>
issue (<a href="https://gitlab.isc.org/isc-projects/stork/-/issues/974" rel="noreferrer" target="_blank">https://gitlab.isc.org/isc-projects/stork/-/issues/974</a>) may<br>
indicate that if you add `-c /etc/named.conf` (or whatever your actual<br>
config path inside the chroot is) to your named command line, that<br>
Stork may discover the file.<br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
On Thu, Mar 5, 2026 at 12:35 PM Juliano Alves Guidini <<a href="mailto:jguidini@usp.br" target="_blank">jguidini@usp.br</a>> wrote:<br>
><br>
> Hi Math, don't worry. Yes, the issue is related to jail (-t).<br>
> Many thanks!<br>
><br>
> Cheers,<br>
><br>
> -- Juliano Alves Guidini<br>
><br>
><br>
><br>
><br>
> Em qua., 4 de mar. de 2026 às 22:58, <<a href="mailto:isc-mailing-list@secmail.8shield.net" target="_blank">isc-mailing-list@secmail.8shield.net</a>> escreveu:<br>
>><br>
>> Hello Juliano,<br>
>><br>
>> I had formatting issues with your message and just noticed the error (in plain text mode) that the /etc/named.conf is being found by the stork agent (parsing the named -V output). Therefore ignore my previous message. Maybe something to do with the use of the chroot jail (-t) but I have to leave the question to the experts - sorry for the noise.<br>
>><br>
>> Cheers,<br>
>> Math.<br>
>><br>
>><br>
>><br>
>> On Wednesday, March 4th, 2026 at 20:37, isc-mailing-list at <a href="http://secmail.8shield.net" rel="noreferrer" target="_blank">secmail.8shield.net</a> wrote:<br>
>><br>
>> > Hello Juliano,<br>
>> ><br>
>> > I noticed that your "default paths" configuration lists "/etc/named.conf" (I believe no longer the standard location on Debian since Bind 9.x). Based on the documentation (<a href="https://stork.readthedocs.io/en/v2.4.0/dns.html#detection" rel="noreferrer" target="_blank">https://stork.readthedocs.io/en/v2.4.0/dns.html#detection</a>) I don't believe the agent will find the file there. You can try defining STORK_AGENT_BIND9_CONFIG=/etc/named.conf parameter in the /etc/stork/agent.env file and restart the agent to see if that helps.<br>
>> ><br>
>> ><br>
>> > Cheers,<br>
>> > Math.<br>
>> ><br>
>> ><br>
>> ><br>
>> > On Wednesday, March 4th, 2026 at 14:34, Juliano Alves Guidini <<a href="mailto:jguidini@usp.br" target="_blank">jguidini@usp.br</a>> wrote<br>
>> ><br>
>> > ><br>
>> > ><br>
>> > > Hi!<br>
>> > ><br>
>> > > I upgraded Stork Agent to v2.4.0 and observed this message on log:<br>
>> > ><br>
>> > ><br>
>> > > 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\<a href="http://nisc.org/stork/util.(*systemCommandExecutor).GetFileInfo%5Cn%5Ct/builds/isc-projects/stork/backend/util/executor.go:51%5Cnisc.org/stork/agent.newDetectedDaemonFile%5Cn%5Ct/builds/isc-projects/stork/backend/agent/detectedfiles.go:41%5Cnisc.org/stork/agent.(*detectedDaemonFiles).addFile%5Cn%5Ct/builds/isc-projects/stork/backend/agent/detectesfiles.go:98%5Cnisc.org/stork/agent.(*monitor).detectBind9ConfigPaths%5Cn%5Ct/builds/isc-projects/stork/backend/agent/bind9.go:325%5Cnisc.org/stork/agent.(*monitor).detectBind9Daemon%5Cn%5Ct/builds/isc-projects/stork/backend/agent/bind9.go:468%5Cnisc.org/stork/agent.(*monitor).detectDaemons%5Cn%5Ct/builds/isc-projects/stork/backend/agent/monitor.go:425%5Cnisc.org/stork/agent.(*monitor).run%5Cn%5Ct/builds/isc-projects/stork/backend/agent/monitor.go:319%5Cnruntime.goexit%5Cn%5Ct/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1693%5Cnfailed" rel="noreferrer" target="_blank">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/detectesfiles.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</a> to detect BIND 9 config path"<br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > When using version 2.2.1.250828143649 this does not occur, but on version 2.4.0.260218163426 agent can't find named.conf.<br>
>> > ><br>
>> > > My setup:<br>
>> > ><br>
>> > ><br>
>> > > # lsb_release -a<br>
>> > > No LSB modules are available.<br>
>> > > Distributor ID: Debian<br>
>> > > Description: Debian GNU/Linux 13 (trixie)<br>
>> > > Release: 13<br>
>> > > Codename: trixie<br>
>> > ><br>
>> > > # rndc status<br>
>> > > version: BIND 9.18.44 (Extended Support Version) <id:2e74eea><br>
>> > > running on localhost: Linux x86_64 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17)<br>
>> > > boot time: Wed, 04 Mar 2026 17:51:33 GMT<br>
>> > > last configured: Wed, 04 Mar 2026 17:51:33 GMT<br>
>> > > configuration file: /etc/named.conf (/var/lib/named/etc/named.conf)<br>
>> > > CPUs found: 4<br>
>> > > worker threads: 4<br>
>> > > UDP listeners per interface: 4<br>
>> > > number of zones: 46 (16 automatic)<br>
>> > > debug level: 0<br>
>> > > xfers running: 0<br>
>> > > xfers deferred: 0<br>
>> > > soa queries in progress: 0<br>
>> > > query logging is ON<br>
>> > > recursive clients: 0/9900/10000<br>
>> > > tcp clients: 0/3000<br>
>> > > TCP high-water: 0<br>
>> > > server is up and running<br>
>> > ><br>
>> > > # ps -ef | grep named<br>
>> > > bind 2917 1 0 14:51 ? 00:00:06 /var/lib/named/sbin/named -f -u bind -t /var/lib/named<br>
>> > ><br>
>> > > # /var/lib/named/sbin/named -V<br>
>> > > BIND 9.18.44 (Extended Support Version) <id:2e74eea><br>
>> > > running on Linux x86_64 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17)<br>
>> > > 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'<br>
>> > > compiled by GCC 14.2.0<br>
>> > > compiled with OpenSSL version: OpenSSL 3.5.4 30 Sep 2025<br>
>> > > linked to OpenSSL version: OpenSSL 3.5.4 30 Sep 2025<br>
>> > > compiled with libuv version: 1.50.0<br>
>> > > linked to libuv version: 1.50.0<br>
>> > > compiled with libxml2 version: 2.9.14<br>
>> > > linked to libxml2 version: 20914<br>
>> > > compiled with json-c version: 0.18<br>
>> > > linked to json-c version: 0.18<br>
>> > > linked to maxminddb version: 1.12.2<br>
>> > > compiled with protobuf-c version: 1.5.1<br>
>> > > linked to protobuf-c version: 1.5.1<br>
>> > > threads support is enabled<br>
>> > > DNSSEC algorithms: RSASHA1 NSEC3RSASHA1 RSASHA256 RSASHA512 ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448<br>
>> > > DS algorithms: SHA-1 SHA-256 SHA-384<br>
>> > > HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224 HMAC-SHA256 HMAC-SHA384 HMAC-SHA512<br>
>> > > TKEY mode 2 support (Diffie-Hellman): yes<br>
>> > > TKEY mode 3 support (GSS-API): no<br>
>> > ><br>
>> > > default paths:<br>
>> > > named configuration: /etc/named.conf<br>
>> > > rndc configuration: /etc/rndc.conf<br>
>> > > DNSSEC root key: /etc/bind.keys<br>
>> > > nsupdate session key: /var/lib/named/var/run/named/session.key<br>
>> > > named PID file: /var/lib/named/var/run/named/named.pid<br>
>> > > named lock file: /var/lib/named/var/run/named/named.lock<br>
>> > > geoip-directory: /usr/share/GeoIP<br>
>> > ><br>
>> > ><br>
>> > > Bind is not in the latest version on this machine, but is a test machine.<br>
>> > ><br>
>> > > I noticed the same behavior on Debian 11 ( exactly same setup, only changed OS version ).<br>
>> > ><br>
>> > > Best Regards,<br>
>> > ><br>
>> > ><br>
>> > > -- Juliano Alves Guidini<br>
>> > ><br>
>><br>
> --<br>
> Stork-users mailing list<br>
> <a href="mailto:Stork-users@lists.isc.org" target="_blank">Stork-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/stork-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/stork-users</a><br>
-- <br>
Stork-users mailing list<br>
<a href="mailto:Stork-users@lists.isc.org" target="_blank">Stork-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/stork-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/stork-users</a><br>
</blockquote></div>