OPNsense Forum

English Forums => 25.1, 25.4 Production Series => Topic started by: pupadmin on March 28, 2025, 07:44:30 PM

Title: BIND (named) broken in 25.1.4_1
Post by: pupadmin on March 28, 2025, 07:44:30 PM
Hi folks,

after the update to 25.1.4_1 (I think from 25.1.2) BIND is not starting anymore.

In system.log I only see:

<13>1 2025-03-28T19:08:58+01:00 SERVERNAME root 33135 - [meta sequenceId="1"] /usr/local/etc/rc.d/named: ERROR: named-checkconf for /usr/local/etc/namedb/named.conf failed

If I try to start binaries manually via shell, I get:

ld-elf.so.1: Shared object "libisc-9.20.7.so" not found, required by "named-checkconf"
ld-elf.so.1: Shared object "libisc-9.20.6.so" not found, required by "named"
ld-elf.so.1: Shared object "libdns-9.20.7.so" not found, required by "named-journalprint"

So there might something be mixed up in the package with the binaries and their libraries...
It would be great if this could be fixed as I prefer BIND vs. Unbound.

TIA & best regards,
Stefan


Title: Re: BIND (named) broken in 25.1.4_1
Post by: franco on March 28, 2025, 07:50:52 PM
Health audit, likely needs a reinstall of the bind920 package because files are missing...
Title: Re: BIND (named) broken in 25.1.4_1
Post by: pupadmin on March 28, 2025, 08:29:08 PM
Ok, strange: When I got the name resolution finally back running, OPNsense installed updates to bind and haproxy (single version step). Now everything is running again. No idea why these were missed in the full upgrade...

Anyway, I made a health check now afterwards and it complains about:

py37-markupsafe has a missing dependency: python37
py37-markupsafe has a missing dependency: py37-setuptools
py37-markupsafe is missing a required shared library: libpython3.7m.so.1.0

but I do not know if this is actually a problem. Everything seems to run fine again.

So, problem is resolved. Thank you very much for the quick reply and keep up the good work!

Cheers, Stefan
Title: Re: BIND (named) broken in 25.1.4_1
Post by: Patrick M. Hausen on March 28, 2025, 08:58:59 PM
pkg delete py37-markupsafe
Title: Re: BIND (named) broken in 25.1.4_1
Post by: RamSense on March 28, 2025, 09:53:46 PM
Hi Stefan, had this issue also this time again (running BIND, and I am not using unbound), with an earlier update I mentioned it also. Hoping it was a one time event ;-).
The "fix" was again the same, after the update (what looked like it all went well), you have to hit update again, and the missing files for bind are being installed/updated.
Glad you have resolved it also.
Title: Re: BIND (named) broken in 25.1.4_1
Post by: doktornotor on March 30, 2025, 12:00:26 PM
Have seen this on multiple boxes. There's something fishy about the dependencies and/or the way pkg resolves them on upgrades.
Title: Re: BIND (named) broken in 25.1.4_1
Post by: doktornotor on April 19, 2025, 10:38:53 AM
This is the latest one...

[74/74] Upgrading bind920 from 9.20.6 to 9.20.7...
[74/74] Extracting bind920-9.20.7: .......... done
pkg-static: Fail to rename /usr/local/bin/.pkgtemp.named-checkconf.L051g6LB8b9Y -> /usr/local/bin/named-checkconf:No such file or directory


After reboot:

eval: /usr/local/bin/named-checkconf: not found
/usr/local/etc/rc.d/named: ERROR: named-checkconf for /usr/local/etc/namedb/named.conf failed


Had to manually update the bind920 package after OPNsense upgrade finished.