Please share the unbound.conf that causes the issue. On 2025-09-28 21:42 -04, Sonic <[email protected]> wrote: > Looks like it was a configuration problem in the remote-control > section that didn't have an issue with the previous version. > Seems like it should have been called out by unbound-checkconf but > pledge caused that check to fail. > > On Sun, Sep 28, 2025 at 9:09 PM Sonic <[email protected]> wrote: >> >> Hello, >> >> I'm having an issue with Unbound after upgrading to the latest snapshot. >> ========================== >> # rcctl start unbound >> unboundunbound-checkconf(21617): pledge sysctl 6: 4 17 0 0 3 0 >> unbound-checkconf[21617]: pledge "", syscall 202 >> (failed) >> ========================== >> or: >> ========================== >> # unbound-checkconf >> unbound-checkconf(11383): pledge sysctl 6: 4 17 0 0 3 0 >> unbound-checkconf[11383]: pledge "", syscall 202 >> Abort trap (core dumped) >> ========================== >> >> Three other system upgrades were fine, no Unbound issues but this one is >> toast. >> >> How to resolve? >> >> Thank you. >
-- In my defence, I have been left unsupervised.
