FS#59136 - [powerdns] chroot when running from systemd
Attached to Project:
Community Packages
Opened by Anton Hvornum (Torxed) - Sunday, 24 June 2018, 21:27 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 25 June 2018, 01:30 GMT
Opened by Anton Hvornum (Torxed) - Sunday, 24 June 2018, 21:27 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 25 June 2018, 01:30 GMT
|
Details
Description:
Jun 24 23:25:18 Hostname systemd[1]: Starting PowerDNS Authoritative Server... Jun 24 23:25:19 Hostname pdns_server[17102]: UDP server bound to 0.0.0.0:53 Jun 24 23:25:19 Hostname pdns_server[17102]: UDPv6 server bound to [::]:53 Jun 24 23:25:19 Hostname pdns_server[17102]: TCP server bound to 0.0.0.0:53 Jun 24 23:25:19 Hostname pdns_server[17102]: TCPv6 server bound to [::]:53 Jun 24 23:25:19 Hostname pdns_server[17102]: Unable to chroot when running from systemd. Please disable chroot= or set the 'Type' for this service to 'simple' Jun 24 23:25:19 Hostname systemd[1]: pdns.service: Main process exited, code=exited, status=1/FAILURE Jun 24 23:25:19 Hostname systemd[1]: pdns.service: Failed with result 'exit-code'. Jun 24 23:25:19 Hostname systemd[1]: Failed to start PowerDNS Authoritative Server. Additional info: * package version(s) powerdns 4.1.3-2 |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Monday, 25 June 2018, 01:30 GMT
Reason for closing: Not a bug
Additional comments about closing: You set the chroot option, it's your responsibility to set the other options it needs.
Monday, 25 June 2018, 01:30 GMT
Reason for closing: Not a bug
Additional comments about closing: You set the chroot option, it's your responsibility to set the other options it needs.
However, seams odd that this has to be done each installation/upgrade, so a change to the build script may be in order?
There's no need to edit the service file on every run, use systemd *.conf.d/ drop-ins.
The pdns.conf shipped in the package disables chroot by default, for exactly this reason.