fatal errors after upgrading 1.9.6 to 1.10.0. 1.9.6 is working.

Ron Varburg ronvarburg at yahoo.com
Sun Feb 23 08:28:08 UTC 2020

 Thank you.
Well, maybe I should have examine the distribution related files prior to asking.
can you confirm it is probably caused by:

$ grep ReadWritePaths /usr/lib/systemd/system/unbound.service
ReadWritePaths=/run /etc/unbound /etc/unbound

Is this a distribution, or supplied by unbound upstream, file?
     On Sunday, February 23, 2020, 09:12:13 AM GMT+1, Ron Varburg via Unbound-users <unbound-users at lists.nlnetlabs.nl> wrote:  
 unbound-1.9.6 worked for me, or that is what I think. In particular it did create
/run/unbound.pid and /run/unbound.sock.
With 1.10.0, and without changing unbound.conf or any other configuration file that I am aware of, I get

fatal error: could not open ports
error: cannot open control interface /run/unbound.sock 8953
error: Cannot remove old local socket /run/unbound.sock (Read-only file system)

It could be the distribution has changed some unbound related files with 1.10.0.
Should I examine this more closely? As far as I can tell, there is no /run/unbound.sock
when unbound starts. Neither /run is a Read-only file system.
Perhaps the problem is related to
Fix #138: stop binding pidfile inside chroot dir in systemd service file
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20200223/02eb9499/attachment.htm>

More information about the Unbound-users mailing list