Condition check resulted in Unbound DNS server via resolvconf being skipped

[Michael Tokarev]

13.05.2024 03:28, subscription2 via Unbound-users wrote:
> 
> I'm running unbound on Ubuntu 22.04.4 LTS and am getting this message when I start unbound. I've posted this issue in the Ubuntu forum, but have had 
> no reply.

This is normal and a do-nothing warning.

In debian (and ubuntu), unbound service startup triggers startup of
unbound-resolvconf service too, - this is to tell resolvconf, if it
is present, about unbound presence.

The condition which you're seeing is in unbound-resolvconf.service:

   ConditionFileIsExecutable=/sbin/resolvconf

so the service does nothing if there's no /sbin/resolvconf on your
system.  And systemd is logging this message.  Which is, as I
mentioned earlier, absolutely normal.

Unbound itself works as configured.

This is how the packaging is done in debian.  And while I'm the
maintainer of unbound package in debian, I don't know why it's
done this way, - it was before my time.

Thanks,

/mjt
---
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt