Just installed Pihole for the first time onto Raspbian Lite, hitting FTL errors

Expected Behaviour:

Pi hole works, FTL & DNS services are running, admin web dashboard is up

Actual Behaviour:

FTL errors, -r cannot repair due to what seems like a git issue

Details

Got a new Pi Zero W headless, installed Raspbian Lite on it (2019-06-20 v4.19), used curl script to pipe to bash as described on git. Everything seemed fine but I couldn't access web dashboard & setting DNS on router did not connect to internet.

Used putty to ssh in
pihole status says 'DNS Service is NOT running'
pihole enable says 'pihole-FTL: no process found'
pihole restartdns says 'Failed to start pihole-FTL.service: Unit pihole-FTL.service not found'
pihole-FTL version says 'v4.3.1'
which pihole-FTL says '/usr/bin/pihole-FTL'
file /usr/bin/pihole-FTL says '/usr/bin/pihole-FTL: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, with debug_info, not stripped'
and finally
pihole -r fails with...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=25.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=14.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=15.2 ms

ping: google.com: Temporary failure in name resolution

Debug Token:

When I ran pihole -d, it ran a bunch of debug spew, but I don't see the word token anywhere. When it offered to upload logs I said yes, but hit 'There was an error uploading your debug log. Please try again or contact the Pi-hole team for assistance.'. There seems to be a local copy, what is the best way to get this to you?

Okay, I was able to address my problem from the thread here:

The solution was to temporarily change nameserver in /etc/resolv.conf from 127.0.0.1 to 8.8.8.8 :
sudo sed -i 's/127.0.0.1/8.8.8.8/' /etc/resolv.conf

And run repair:
pihole -r

Here are the failures:
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found... not backing up
[✗] DNS service is NOT running

After a pihole restartdns and pihole status I see:
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

However, I'm still not able to access the dashboard at http://PIHOLE-IPADDRESS/admin/

I suspect lighttpd is to blame.

sudo service lighttpd start
Job for lighttpd.service failed because the control process exited with error code.
See "systemctl status lighttpd.service" and "journalctl -xe" for details.

systemctl status lighttpd.service
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-06-26 01:51:31 BST; 2min 4s ago
Process: 13777 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=255/EXCEPTION)

Jun 26 01:51:31 raspberrypi systemd[1]: lighttpd.service: Service RestartSec=100ms expired, scheduling restart.
Jun 26 01:51:31 raspberrypi systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5.
Jun 26 01:51:31 raspberrypi systemd[1]: Stopped Lighttpd Daemon.
Jun 26 01:51:31 raspberrypi systemd[1]: lighttpd.service: Start request repeated too quickly.
Jun 26 01:51:31 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jun 26 01:51:31 raspberrypi systemd[1]: Failed to start Lighttpd Daemon.

Okay, trying to get more info about the failure, but hitting a wall...

Trying to get more info about lighttpd failure

lighttpd -D -f /etc/lighttpd/lighttpd.conf
/bin/bash: /usr/share/lighttpd/create-mime.assign.pl: No such file or directory
2019-06-26 01:54:43: (configfile.c.1461) command "/usr/share/lighttpd/create-mime.assign.pl" exited non-zero: 127
2019-06-26 01:54:43: (configfile.c.1289) source: /etc/lighttpd/lighttpd.conf line: 53 pos: 14 parser failed somehow near here: (EOL)
lighttpd -D -f /etc/lighttpd/external.conf
2019-06-26 02:17:07: (configfile.c.1613) a default document-root has to be set
2019-06-26 02:17:07: (server.c.1164) setting default values failed

Looks like the conf file is corrupted.

From this bug:

"I had this problem. The workaround:
sudo apt-get install gamin

It appears that the default lighttpd configuration tries to use fam (aka gamin), but there is no dependency on gamin. I would suggest either the package adds a gamin dependency, or the default configuration removes the fam dependency."

Installing gamin did nothing, looks like conf file corruption to me.
Not sure about next steps.

Are you trying to install on Buster?

https://discourse.pi-hole.net/t/getting-ready-for-buster/21001/19

Aaah, so that's what that word means :slight_smile:

Raspbian Buster Lite on this page...
https://www.raspberrypi.org/downloads/raspbian/

To be clear, I have Pi-hole up and running (beautifully, I might add). I just wish I knew how well--my web dashboard is out because of lighttpd.

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