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

Fri Mar 6 15:33:28 UTC 2026

Hi Juliano,

Throwing an uneducated guess out there...   Have you tried to reference the file using its chroot path location? i.e. STORK_AGENT_BIND9_CONFIG=/var/lib/named/etc/named.conf

It could be something to do with config file change detection?

Cheers,
Math

On Friday, March 6th, 2026 at 07:22, Juliano Alves Guidini <jguidini at usp.br> wrote:

> 
> Hi Ankney, thanks by help!
> 
> 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).
> 
> 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.
> 
> Testing now with -c on Bind:
> 
> # Before:
> # ps -ef | grep named
> bind 461508 1 0 Mar05 ? 00:00:47 /var/lib/named/sbin/named -f -u bind -t /var/lib/named
> 
> # After:
> # ps -ef | grep named
> 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
> 
> # ps -ef | grep stork
> stork-a+ 631687 1 0 08:59 ? 00:00:00 /usr/bin/stork-agent
> 
> # 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: Fri, 06 Mar 2026 11:56:27 GMT
> last configured: Fri, 06 Mar 2026 11:56:27 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
> 
> 
> Stork Log (STORK_LOG_LEVEL=WARN):
> 
> 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\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"
> 
> 
> Stork Log (STORK_LOG_LEVEL=DEBUG) - The newlines on logs were introduced by me, to clear view.
> 
> 
> 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 "
> 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 "
> Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="=============================================================================" file=" register.go:450 "
> 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 "
> Mar 06 09:01:41 dns-j01 stork-agent[632299]: time="2026-03-06 09:01:41" level="info" msg="=============================================================================" file=" register.go:452 "
> 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 "
> 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 "
> 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"
> 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 "
> 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 "
> 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 "
> 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 0.0.0.0:9547" file=" promkeaexporter.go:627 "
> 
> 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 "
> 
> 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 "
> 
> 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\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 to detect BIND 9 config path"
> 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 "
> 
> 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 0.0.0.0:9119" file="prombind9exporter.go:915 "
> 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="10.2.0.194:8080"
> 
> 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 "
> 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 "
> 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\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"
> 
> 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 "
> 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 "
> 
> 
> Not working yet.
> 
> Added STORK_AGENT_BIND9_CONFIG=/etc/named.conf on /etc/stork/agent.env and not removed -c from bind. Same result, see logs.
> 
> 
> 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 "
> 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 "
> Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="=============================================================================" file=" register.go:450 "
> 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 "
> Mar 06 09:11:36 dns-j01 stork-agent[634644]: time="2026-03-06 09:11:36" level="info" msg="=============================================================================" file=" register.go:452 "
> 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 "
> 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 "
> 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"
> 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 "
> 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 "
> 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 "
> 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 0.0.0.0:9547" file=" promkeaexporter.go:627 "
> 
> 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 "
> 
> 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 "
> 
> 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 "
> 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 "
> 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\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 to detect BIND 9 config path"
> 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 "
> 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 0.0.0.0:9119" file="prombind9exporter.go:915 "
> 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="10.2.0.194:8080"
> 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 "
> 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 "
> 
> 
> Removed -c from bind but not removed STORK_AGENT_BIND9_CONFIG=/etc/named.conf from /etc/stork/agent.env. Same result, see logs.
> 
> 
> 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 "
> 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 "
> Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="=============================================================================" file=" register.go:450 "
> 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 "
> Mar 06 09:17:16 dns-j01 stork-agent[636225]: time="2026-03-06 09:17:16" level="info" msg="=============================================================================" file=" register.go:452 "
> 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 "
> 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 "
> 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"
> 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 "
> 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 "
> 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 "
> 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 0.0.0.0:9547" file=" promkeaexporter.go:627 "
> 
> 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 "
> 
> 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 "
> 
> 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 "
> 
> 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 "
> 
> 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\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 to detect BIND 9 config path"
> 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 "
> 
> 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 0.0.0.0:9119" file="prombind9exporter.go:915 "
> 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="10.2.0.194:8080"
> 
> 
> 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 "
> 
> 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 "
> 
> 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 "
> 
> 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 "
> 
> 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\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"
> 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 "
> 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 "
> 
> 
> Many Thanks!
> 
> -- Juliano Alves Guidini
> 
> 
> Em sex., 6 de mar. de 2026 às 07:06, Darren Ankney <darren.ankney at gmail.com> escreveu:
> 
> > Hi,
> > 
> > It may well be the `-t ` that is preventing the successful connection.
> > There is an issue about it:
> > https://gitlab.isc.org/isc-projects/stork/-/issues/1217 This closed
> > issue (https://gitlab.isc.org/isc-projects/stork/-/issues/974) may
> > indicate that if you add `-c /etc/named.conf` (or whatever your actual
> > config path inside the chroot is) to your named command line, that
> > Stork may discover the file.
> > 
> > Thank you,
> > Darren Ankney
> > 
> > On Thu, Mar 5, 2026 at 12:35 PM Juliano Alves Guidini <jguidini at usp.br> wrote:
> > >
> > > Hi Math, don't worry. Yes, the issue is related to jail (-t).
> > > Many thanks!
> > >
> > > Cheers,
> > >
> > > -- Juliano Alves Guidini
> > >
> > >
> > >
> > >
> > > Em qua., 4 de mar. de 2026 às 22:58, <isc-mailing-list at secmail.8shield.net> escreveu:
> > >>
> > >> Hello Juliano,
> > >>
> > >> 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.
> > >>
> > >> Cheers,
> > >> Math.
> > >>
> > >>
> > >>
> > >> On Wednesday, March 4th, 2026 at 20:37, isc-mailing-list at secmail.8shield.net wrote:
> > >>
> > >> > Hello Juliano,
> > >> >
> > >> > 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 (https://stork.readthedocs.io/en/v2.4.0/dns.html#detection) 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.
> > >> >
> > >> >
> > >> > Cheers,
> > >> > Math.
> > >> >
> > >> >
> > >> >
> > >> > On Wednesday, March 4th, 2026 at 14:34, Juliano Alves Guidini <jguidini at usp.br> wrote
> > >> >
> > >> > >
> > >> > >
> > >> > > 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/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 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
> > >> > >
> > >>
> > > --
> > > Stork-users mailing list
> > > Stork-users at lists.isc.org
> > > https://lists.isc.org/mailman/listinfo/stork-users
> > --
> > Stork-users mailing list
> > Stork-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/stork-users