pihole-FTL is working, but webmin says the service is not running

DL6ER · April 14, 2018, 9:32am

Despite nice weather today (sunny, 22°C), I finished coding the systemd unit. More details can be found here:

github.com/pi-hole/pi-hole

Install either init.d script or systemd unit depending on used init

pi-hole:development ← pi-hole:FTLDNS-systemd

opened 09:31AM - 14 Apr 18 UTC

DL6ER

+79 -13

**By submitting this pull request, I confirm the following:** *please fill any… appropriate checkboxes, e.g: [X]* - [x] I have read and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md), as well as this entire template. - [x] I have made only one major change in my proposed changes. - [x] I have commented my proposed changes within the code. - [x] I have tested my proposed changes, and have included unit tests where possible. - [x] I am willing to help maintain this change if there are issues with it later. - [x] I give this submission freely and claim no ownership. - [x] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) - [x] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) Please make sure you [Sign Off](https://github.com/pi-hole/pi-hole/wiki/How-to-signoff-your-commits.) all commits. Pi-hole enforces the [DCO](https://github.com/pi-hole/pi-hole/wiki/Contributing-to-the-project). --- **What does this PR aim to accomplish?:** Replace the ancient `init.d` script for starting and controlling the `pihole-FTL` process by a modern `systemd` unit. This should resolve some problems as discussed [here](https://discourse.pi-hole.net/t/service-pihole-ftl-active-exited/8335) or [here](https://discourse.pi-hole.net/t/pihole-ftl-is-working-but-webmin-says-the-service-is-not-running/8368). This now also makes the `status` command behave correctly, as `systemd` can use the PID file of FTL to find out if it is actually running or not: ![screenshot at 2018-04-14 11-24-00](https://user-images.githubusercontent.com/16748619/38766751-db805ed6-3fd6-11e8-99ad-ca925f00d11e.png) Also, since *FTL*DNS is a very important part of your system, the unit ensures that it will be automatically restarted whenever something unexpected happens. As an example, I sent `SIGKILL` to FTL and as you can see, `systemd` took care about immediately restarting the service: ![screenshot at 2018-04-14 11-27-08](https://user-images.githubusercontent.com/16748619/38766768-1276bd40-3fd7-11e8-97ea-3411a6f0479b.png) Note that we do not restart `pihole-FTL` automatically after having received `SIGTERM` as this is the correct way of terminating the resolver (e.g. through `service pihole-FTL stop`). **How does this PR accomplish the above?:** I wrote a systemd unit for `pihole-FTL` and modified the installer to replace the old init.d script. **What documentation changes (if any) are needed to support this PR?:** All commands should work as before.