[stork-users] Problems with agent version 1.13.0 and cwd

[Slawek Figiel]

Hello Bret!

Thank you for your report!

Could you provide some details about your environment:

1. Do you run your BIND 9 in the chroot mode (you run it using the -t flag)?
2. Is the `/var/cache/bind/etc/bind/named.conf` path correct? Is it a 
configuration file used by your BIND 9 instance?
3. Please attach the output of this command: `named-checkconf -g -p 
/var/cache/bind/etc/bind/named.conf`.
4. Are you sure BIND 9 was correctly detected in Stork 1.11.0? Are you 
sure you haven't provided any changes in the BIND 9 before updating 
Stork Agent?
5. Could you attach your anonymized BIND 9 configuration?
6. Could you provide the exact command (CLI arguments) used to run BIND 9?

Regards,
Slawek Figiel


On 31/10/2023 10:27, Giddings, Bret wrote:
> Hi,
> 
> If I upgrade from what was a fairly plain install of stork agent 1.12.0 
> on Debian 12, then stork-agent is no longer able to read named.conf from 
> my (again) plain and simple install of bind9.
> 
> The log shows
> 
> WARN[2023-10-31 09:22:08]          monitor.go:225   Cannot get process 
> current working directory  error="readlink /proc/576/cwd: permission denied"
> 
> INFO[2023-10-31 09:22:08]            bind9.go:560   Found BIND 9 config 
> file in /var/cache/bind/etc/bind/named.conf based on output of `named -V`.
> 
> WARN[2023-10-31 09:22:08]            bind9.go:579   Cannot parse BIND 9 
> config file /var/cache/bind/etc/bind/named.conf: exit status 1;
> 
> WARN[2023-10-31 09:22:08]          monitor.go:194   No Kea nor Bind9 app 
> detected for monitoring; please check if they are running, and Stork can 
> communicate with them.
> 
> I have tried setting STORK_BIND9_CONFIG in agent.env which doesn’t help.
> 
> Are there any workarounds to get this working again?
> 
> Thanks in advance,
> 
> Bret
> 
>