1.10 now works, but I can not locate the pid file

[Ron Varburg]

 1) The problem was that with 1.9.6 I had 
 control-enable: yes
 control-interface: /run/unbound.sock
in my 1.9.6 unbound.conf. This conflicts with 1.10.0 unbound.service because it has a
 RuntimeDirectory=unbound
setting. Adjusting unbound.conf to point to /run/unbound/unbound.sock enabled 
unbound to run.
2) 1.10.0 unbound.service states:
 ; - `RuntimeDirectory=unbound` creates a /run/unbound directory, owned by the
 ; unit User and Group with read-write permissions (0755) as soon as the
 ; unit starts. This allows unbound to store its pidfile. The directory and
 ; its content are automatically removed by systemd when the unit stops.
Yet 1.10.0 unbound.conf suggests /run/unbound.pid. And I am confused if this is
only a suggestion, or a statement about the default location. unbound.conf.5
explicitly states the default is /run/unbound.pid. Am I suppose to find the pid file?
I can not see it. Where should I look for it?
     On Sunday, February 23, 2020, 11:43:04 AM GMT+1, Ron Varburg via Unbound-users <unbound-users at lists.nlnetlabs.nl> wrote:  
 
  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 lists.nlnetlabs.nl> 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 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/20200227/524e034d/attachment.htm>