Pihole down after 4.0 fresh install

sander_kerkhoff · August 19, 2018, 8:10am

Please follow the below template, it will help us to help you!

Expected Behaviour:

new install, expect it to run

Actual Behaviour:

[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
/opt/pihole/updatecheck.sh: line 56: /usr/bin/pihole-FTL: Operation not permitted
/opt/pihole/updatecheck.sh: line 62: /usr/bin/pihole-FTL: Operation not permitted

[i] The install log is located at: /etc/pihole/install.log
Update Complete!

Current Pi-hole version is v4.0
Current AdminLTE version is v4.0
/opt/pihole/version.sh: line 19: /usr/bin/pihole-FTL: Operation not permitted
Invalid Option! Try 'pihole -v --help' for more information.

Debug Token:

pm3ey5zw4y

reinstalled several times, no effect.
Also have to manaully start dnsmasq

When i manually start pihole-FTL:
root@vps4:~# /etc/init.d/pihole-FTL start
Not running
chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
sh: 1: /usr/bin/pihole-FTL: Operation not permitted
root@vps4:~#

openvz vps on debian 9
had no issues with v3

DL6ER · August 19, 2018, 1:57pm

Please try

sudo touch /etc/pihole/dhcp.leases
wget https://github.com/pi-hole/FTL/releases/download/v4.0/pihole-FTL-linux-x86_64
sudo mv pihole-FTL-linux-x86_64 /usr/bin/pihole-FTL
sudo service pihole-FTL restart

sander_kerkhoff · August 19, 2018, 2:44pm

still the same:

root@vps4:~# service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Sun 2018-08-19 14:45:18 UTC; 2min 52s ago
     Docs: man:systemd-sysv-generator(8)

Aug 19 14:45:18 vps4 systemd[1]: pihole-FTL.service: Failed to set invocation ID on control group /system.slice/pihole-FTL.servi
Aug 19 14:45:18 vps4 systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 19 14:45:18 vps4 pihole-FTL[2432]: Not running
Aug 19 14:45:18 vps4 su[2455]: Successful su for pihole by root
Aug 19 14:45:18 vps4 su[2455]: + ??? root:pihole
Aug 19 14:45:18 vps4 su[2455]: pam_env(su:session): Unable to open env file: /etc/default/locale: No such file or directory
Aug 19 14:45:18 vps4 su[2455]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 19 14:45:18 vps4 pihole-FTL[2432]: sh: 1: /usr/bin/pihole-FTL: Operation not permitted
Aug 19 14:45:18 vps4 systemd[1]: Started LSB: pihole-FTL daemon.
lines 1-14/14 (END)
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Sun 2018-08-19 14:45:18 UTC; 2min 52s ago
     Docs: man:systemd-sysv-generator(8)

Aug 19 14:45:18 vps4 systemd[1]: pihole-FTL.service: Failed to set invocation ID on control group /system.slice/pihole-FTL.service, ignoring: Operation not permitted
Aug 19 14:45:18 vps4 systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 19 14:45:18 vps4 pihole-FTL[2432]: Not running
Aug 19 14:45:18 vps4 su[2455]: Successful su for pihole by root
Aug 19 14:45:18 vps4 su[2455]: + ??? root:pihole
Aug 19 14:45:18 vps4 su[2455]: pam_env(su:session): Unable to open env file: /etc/default/locale: No such file or directory
Aug 19 14:45:18 vps4 su[2455]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 19 14:45:18 vps4 pihole-FTL[2432]: sh: 1: /usr/bin/pihole-FTL: Operation not permitted
Aug 19 14:45:18 vps4 systemd[1]: Started LSB: pihole-FTL daemon.
~

cybrnook2002 · August 19, 2018, 2:50pm

Noticed the same on a 4.0 installing running in a Debian VM. Would run for approx ~24 hours or, then WenUI shows "Lost connection......". Restarting FTL fixes it temporarily.

sander_kerkhoff · August 19, 2018, 2:53pm

what linux version is best supported?
I had no problems with debian 8 and 3.x release of pihole

cybrnook2002 · August 19, 2018, 2:54pm

I am/was on Debian 9 stretch. In the process of restoring my VM prior to 4.0.

sander_kerkhoff · August 19, 2018, 3:04pm

I was in Debian 8
I reinstalled with stretch with fresh 4.0 but i cannot get it to work

sander_kerkhoff · August 19, 2018, 5:06pm

when i manually start pihole-FTL as root its starting normally
its some user rights thing i think?

i now see this:

> ● pihole-FTL.service - LSB: pihole-FTL daemon
>    Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
>    Active: active (exited) since Sun 2018-08-19 16:49:24 UTC; 15min ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 183 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
>    CGroup: /system.slice/pihole-FTL.service
> 
> Aug 19 16:49:23 vps4 systemd[1]: Starting LSB: pihole-FTL daemon...
> Aug 19 16:49:23 vps4 pihole-FTL[183]: Not running
> Aug 19 16:49:24 vps4 su[267]: Successful su for pihole by root
> Aug 19 16:49:24 vps4 su[267]: + ??? root:pihole
> Aug 19 16:49:24 vps4 su[267]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Aug 19 16:49:24 vps4 pihole-FTL[183]: sh: 1: /usr/bin/pihole-FTL: Operation not permitted
> Aug 19 16:49:24 vps4 systemd[1]: Started LSB: pihole-FTL daemon.
> Aug 19 16:49:29 vps4 systemd[1]: pihole-FTL.service: Failed to set invocation ID on control group /system.slice/pihole-FTL.service, ignoring: Operation not permitted
> root@vps4:/usr/bin#

\

DL6ER · August 19, 2018, 5:33pm

Aha, it may be that you VPS does not support Linux capabilities. What kind of VM software are you using?

If capabilities are not supported, you may need to try an alternative service file. See here:

github.com/pi-hole/pi-hole

Start pihole-FTL as root if capabilities are not supported by the system

pi-hole:development ← pi-hole:fix/pihole-FTL-no-caps

opened 12:35PM - 19 Aug 18 UTC

DL6ER

+7 -3

Signed-off-by: DL6ER <dl6er@dl6er.de> **By submitting this pull request, I co…nfirm 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?:** Fix issue that FTL cannot be started on kernels / file systems that do not support Linux capabilities. **How does this PR accomplish the above?:** We should check if the kernel / file system supports Linux capabilities before trying to start `pihole-FTL` as unprivileged user as binding to port 53 will inevitably fail if capabilities are not supported. Several users confirmed that running `pihole-FTL` as `root` works just fine in these edge cases and we should maybe fall back to starting `pihole-FTL` under `root` (as it is done for `dnsmasq`). This PR add a check if the `setcap` command succeeded and only tries to start `pihole-FTL` as unprivileged user application if this is the case (should almost always be the case). **What documentation changes (if any) are needed to support this PR?:** None, but might be worth mentioning in the 4.1 release blog post so people know that they do not have to manually edit their service file any more.

You could try saving this modified version of pihole-FTL.service as /etc/init.d/pihole-FTL and run sudo service pihole-FTL restart.

sander_kerkhoff · August 19, 2018, 5:54pm

i am running on openvz, wrote that in my first post

sander_kerkhoff · August 19, 2018, 6:11pm

no difference:

  [✗] DNS service is NOT running
/opt/pihole/updatecheck.sh: line 56: /usr/bin/pihole-FTL: Operation not permitted
/opt/pihole/updatecheck.sh: line 62: /usr/bin/pihole-FTL: Operation not permitted

  [i] The install log is located at: /etc/pihole/install.log
    Update Complete!

  Current Pi-hole version is v4.0
  Current AdminLTE version is v4.0
/opt/pihole/version.sh: line 19: /usr/bin/pihole-FTL: Operation not permitted
  Invalid Option! Try 'pihole -v --help' for more information.
root@vps4:~#

DL6ER · August 19, 2018, 6:12pm

@sander_kerkhoff I know, I forgot to point out that I wanted to explicitly ask @cybrnook2002 about the software he's using. Unfortunately, he deleted his post already...

Anyway, I assume my proposed fix should be working for both of you. Please tell me if you see any issues (or if it works, of course ).

sander_kerkhoff · August 19, 2018, 6:15pm

i replaced /etc/init.d/pihole-FTL with this service file:
https://raw.githubusercontent.com/pi-hole/pi-hole/5cd3b11391b719f18313f614a062d29a5e702752/advanced/Templates/pihole-FTL.service

still FTL not running

cybrnook2002 · August 19, 2018, 6:16pm

No worries, I just didn't want to give the impression I am trying to high jack the thread. I am a debian 9 based VM running on Unraid. In my case, pihole starts and runs for some time, however eventually FTL comes down.

When I restart FTL, my log looks similar. I am setting up a fresh VM now, and will install based on your branch with the above fix.

If I want to download the latest basic-install.sh from your branch "pihole-FTL-no-caps", I assume I can just modify a few lines to have the install script do it's install directly from this branch. Instead of having to install 4.0, then switching branches?

cybrnook2002 · August 19, 2018, 7:19pm

pihole@pi-hole:/etc/init.d$ sudo service pihole-FTL restart
Warning: pihole-FTL.service changed on disk. Run 'systemctl daemon-reload' to reload units.

pihole@pi-hole:/etc/init.d$ sudo systemctl daemon-reload

pihole@pi-hole:/etc/init.d$ sudo service pihole-FTL restart

pihole@pi-hole:/etc/init.d$ sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sun 2018-08-19 15:19:13 EDT; 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 11428 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 11459 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Aug 19 15:19:13 pi-hole systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 19 15:19:13 pi-hole pihole-FTL[11459]: Not running
Aug 19 15:19:13 pi-hole pihole-FTL[11459]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Aug 19 15:19:13 pi-hole su[11502]: Successful su for pihole by root
Aug 19 15:19:13 pi-hole su[11502]: + ??? root:pihole
Aug 19 15:19:13 pi-hole su[11502]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 19 15:19:13 pi-hole pihole-FTL[11459]: FTL started!
Aug 19 15:19:13 pi-hole systemd[1]: Started LSB: pihole-FTL daemon.

Still running as user:

pihole@pi-hole:/etc/init.d$ ps -ef | grep FTL
pihole 11506 1 0 15:19 ? 00:00:00 /usr/bin/pihole-FTL

DL6ER · August 19, 2018, 7:46pm

Do you have a new error message / service status message for me?

I understand. If we see that it is a separate issue, I can split the conversation.

This is something I don't understand... But is FTL now running?...

cybrnook2002 · August 19, 2018, 8:09pm

Yes, it is running as pi-hole is up and functioning. But what I will expect to see now, is that in some hours, FTL will be down again.

sander_kerkhoff · August 20, 2018, 6:17am

My pihole is not running, even with the new service file

DL6ER · August 20, 2018, 9:14am

What's the new output of

sudo service pihole-FTL restart
sudo service pihole-FTL status

?

sander_kerkhoff · August 20, 2018, 10:03am

root@vps4:~# sudo service pihole-FTL restart
root@vps4:~# sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Mon 2018-08-20 10:03:12 UTC; 5s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19514 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUC
  Process: 19520 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/S

Aug 20 10:03:11 vps4 systemd[1]: pihole-FTL.service: Failed to set invocation ID
Aug 20 10:03:11 vps4 systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 20 10:03:11 vps4 pihole-FTL[19520]: Not running
Aug 20 10:03:11 vps4 su[19543]: Successful su for pihole by root
Aug 20 10:03:11 vps4 su[19543]: + ??? root:pihole
Aug 20 10:03:11 vps4 su[19543]: pam_unix(su:session): session opened for user pi
Aug 20 10:03:12 vps4 pihole-FTL[19520]: sh: 1: /usr/bin/pihole-FTL: Operation no
Aug 20 10:03:12 vps4 systemd[1]: Started LSB: pihole-FTL daemon.
lines 1-15/15 (END)
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Mon 2018-08-20 10:03:12 UTC; 5s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19514 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 19520 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Aug 20 10:03:11 vps4 systemd[1]: pihole-FTL.service: Failed to set invocation ID on control group /system.slice/pihole-FTL.service, ignoring: Ope
Aug 20 10:03:11 vps4 systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 20 10:03:11 vps4 pihole-FTL[19520]: Not running
Aug 20 10:03:11 vps4 su[19543]: Successful su for pihole by root
Aug 20 10:03:11 vps4 su[19543]: + ??? root:pihole
Aug 20 10:03:11 vps4 su[19543]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 20 10:03:12 vps4 pihole-FTL[19520]: sh: 1: /usr/bin/pihole-FTL: Operation not permitted
Aug 20 10:03:12 vps4 systemd[1]: Started LSB: pihole-FTL daemon.

when i stop it:
Aug 20 10:06:00 vps4 pihole-FTL[19712]: Not running
Aug 20 10:06:00 vps4 su[19751]: Successful su for pihole by root
Aug 20 10:06:00 vps4 su[19751]: + ??? root:pihole
Aug 20 10:06:00 vps4 su[19751]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 20 10:06:00 vps4 pihole-FTL[19712]: sh: 1: /usr/bin/pihole-FTL: Operation not permitted
Aug 20 10:06:00 vps4 systemd[1]: Started LSB: pihole-FTL daemon.
Aug 20 10:07:00 vps4 systemd[1]: pihole-FTL.service: Failed to set invocation ID on control group /system.slice/pihole-FTL.service, ignoring: Operation not permitted
Aug 20 10:07:00 vps4 systemd[1]: Stopping LSB: pihole-FTL daemon...
Aug 20 10:07:00 vps4 pihole-FTL[19812]: Not running
Aug 20 10:07:00 vps4 systemd[1]: Stopped LSB: pihole-FTL daemon.

even starting the binary as root doesn't work:

root@vps4:~# sudo /usr/bin/pihole-FTL
sudo: unable to execute /usr/bin/pihole-FTL: Operation not permitted