Do ignore my 2nd message, and consider only the 1st one.

Ron Varburg ronvarburg at
Sun Feb 23 10:42:36 UTC 2020

 I am confusing between working 1.9.6, and non working 1.10.0.
Do ignore the 2nd message about unbound.service.
And consider only my first message, about failure after upgrading to 1.10.0
     On Sunday, February 23, 2020, 09:28:39 AM GMT+1, Ron Varburg via Unbound-users <unbound-users at> wrote:  
  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> wrote:  
 unbound-1.9.6 worked for me, or that is what I think. In particular it did create
/run/ 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: <>

More information about the Unbound-users mailing list