Pi-hole on Fedora 27 - pihole-FTL not running

Help
1

I'm trying to install pi-hole on my Fedora 27 server (headless). I've had to make some adjustments, namely in lighttpd.conf, changing the port to 81, as Apache is already running on port 80.

systemctl status shows everything running, but when I specifically check for pihole-FTL, it shows that it was active, but exited, with some errors indicating missing files and permissions. I've tried running pihole -r, as well as the basic script again, choosing update to retain settings.

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

Expected Behaviour:

piHole-FTL should run after install

Actual Behaviour:

piHole-FTL is not running

Debug Token:

https://tricorder.pi-hole.net/gblvqrx9f7

[root@galactica lighttpd]# systemctl status pihole-FTL.service
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/rc.d/init.d/pihole-FTL; generated; vendor preset: disabled)
Active: active (exited) since Wed 2019-04-10 14:03:32 EDT; 12s ago
Docs: man:systemd-sysv-generator(8)
Process: 5228 ExecStop=/etc/rc.d/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 5588 ExecStart=/etc/rc.d/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Apr 10 14:03:32 galactica.starfleet.org systemd[1]: Starting LSB: pihole-FTL daemon...
Apr 10 14:03:32 galactica.starfleet.org pihole-FTL[5588]: Not running
Apr 10 14:03:32 galactica.starfleet.org pihole-FTL[5588]: /etc/rc.d/init.d/pihole-FTL: line 4
Apr 10 14:03:32 galactica.starfleet.org su[5611]: (to pihole) root on none
Apr 10 14:03:32 galactica.starfleet.org pihole-FTL[5588]: dnsmasq: cannot open or create leas
Apr 10 14:03:32 galactica.starfleet.org systemd[1]: Started LSB: pihole-FTL daemon.

2

This line got cropped. It probably mentions a missing file. Please create this file manually and change ownership to user and group pihole.

3

You're right, it did get cropped. I extended out my terminal for the whole thing.

[tmorgenthaler@galactica ~]$ systemctl status pihole-FTL.service 
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/rc.d/init.d/pihole-FTL; generated; vendor preset: disabled)
   Active: active (exited) since Wed 2019-04-10 14:03:32 EDT; 2h 1min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5228 ExecStop=/etc/rc.d/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 5588 ExecStart=/etc/rc.d/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/pihole-FTL.service

Apr 10 14:03:32 galactica.starfleet.org systemd[1]: Starting LSB: pihole-FTL daemon...
Apr 10 14:03:32 galactica.starfleet.org pihole-FTL[5588]: Not running
Apr 10 14:03:32 galactica.starfleet.org pihole-FTL[5588]: /etc/rc.d/init.d/pihole-FTL: line 44: /sbin/resolvconf: No such file or directory
Apr 10 14:03:32 galactica.starfleet.org su[5611]: (to pihole) root on none
Apr 10 14:03:32 galactica.starfleet.org pihole-FTL[5588]: dnsmasq: cannot open or create lease file /var/lib/misc/dnsmasq.leases: Permission denied
Apr 10 14:03:32 galactica.starfleet.org systemd[1]: Started LSB: pihole-FTL daemon.
[tmorgenthaler@galactica ~]$
4

Okay, so run

sudo touch /var/lib/misc/dnsmasq.leases
sudo chown pihole:pihole /var/lib/misc/dnsmasq.leases
sudo service pihole-FTL restart
5

Now different messages...

[root@galactica ~]# service pihole-FTL restart
Not running

/etc/init.d/pihole-FTL: line 44: /sbin/resolvconf: No such file or directory

dnsmasq: failed to bind DHCP server socket: Address already in use

6

I found this thread....
https://www.reddit.com/r/pihole/comments/a3g9a0/dnsmasq_fails_with_dhcp_socket_address_already_in

I applied the following commands:

sudo service dnsmasq stop

sudo systemctl disable dnsmasq

sudo service pihole-FTL restart

It now is running, but I did get an error message:

[root@galactica dnsmasq.d]# service pihole-FTL restart
/etc/init.d/pihole-FTL: line 58: /sbin/resolvconf: No such file or directory
.
Stopped

/etc/init.d/pihole-FTL: line 44: /sbin/resolvconf: No such file or directory
FTL started!

[root@galactica dnsmasq.d]# systemctl status pihole-FTL.service
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/rc.d/init.d/pihole-FTL; generated; vendor preset: disabled)
Active: active (exited) since Thu 2019-04-11 08:41:11 EDT; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 3124 ExecStop=/etc/rc.d/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 3141 ExecStart=/etc/rc.d/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Apr 11 08:41:11 galactica.starfleet.org systemd[1]: Starting LSB: pihole-FTL daemon...
Apr 11 08:41:11 galactica.starfleet.org pihole-FTL[3141]: Not running
Apr 11 08:41:11 galactica.starfleet.org pihole-FTL[3141]: /etc/rc.d/init.d/pihole-FTL: line 44: /sbin/r
Apr 11 08:41:11 galactica.starfleet.org su[3164]: (to pihole) root on none
Apr 11 08:41:11 galactica.starfleet.org pihole-FTL[3141]: FTL started!
Apr 11 08:41:11 galactica.starfleet.org systemd[1]: Started LSB: pihole-FTL daemon.

Is this normal upon the first start?

7

Please generate a new debug log, upload it and post the token.

8

Here you go...

https://tricorder.pi-hole.net/q4edxgbib6

It actually seems to be working, which is good. Just curious about the error messages.

9

The reason it wasn't running originally is that you had an instance of dnsmasq running and that was interfering with pihole-FTL running. Now that you have disabled dnsmasq, pihole-FTL can run.

One of the developers will have to address the error message issue.

12

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.