Raspbian: FTL Engine installation failure, Feb 2020

Help
1

I'm running latest updated Raspbian Buster lite on Pi4 4GB. The installation fails in middle with below pasted logs. The pihole doesn't get installed at all, so no "pihole" command is available either.

Expected Behaviour:

Should be getting final "Installation complete" page, but

Actual Behaviour:

[i] Web Server On
[i] Logging On.
[✗] Check for existing repository in /etc/.pihole
[✓] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole

[✗] Check for existing repository in /var/www/html/admin
[✓] Clone https://github.com/pi-hole/AdminLTE.git into /var/www/html/admin

[i] Main Dependency checks...
[✓] Checking for cron
[✓] Checking for curl
[i] Checking for dnsutils (will be installed)
[✓] Checking for iputils-ping
[i] Checking for lsof (will be installed)
[i] Checking for netcat (will be installed)
[✓] Checking for psmisc
[✓] Checking for sudo
[✓] Checking for unzip
[✓] Checking for wget
[i] Checking for idn2 (will be installed)
[i] Checking for sqlite3 (will be installed)
[✓] Checking for libcap2-bin
[i] Checking for dns-root-data (will be installed)
[i] Checking for resolvconf (will be installed)
[✓] Checking for libcap2
[i] Checking for lighttpd (will be installed)
[i] Checking for php-common (will be installed)
[i] Checking for php-cgi (will be installed)
[i] Checking for php-sqlite3 (will be installed)
[✓] Enabling lighttpd service to start on reboot...

[i] FTL Checks...

[✓] Detected ARM-hf architecture (armv7+)
[i] Checking for existing FTL binary...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed
pi@raspberrypi:~ $

Debug Token:

pi@raspberrypi:~ $ pihole -d
-bash: pihole: command not found

2

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run the installer again.

3

Thanks for your reply !!

I can't do install again as it won't take any pihole command or fresh install command either

pi@raspberrypi:~ $ sudo nano /etc/resolv.conf
pi@raspberrypi:~ $ pihole -r
-bash: pihole: command not found

pi@raspberrypi:~ $ curl -sSL https://install.pi-hole.net | bash
curl: (6) Could not resolve host: install.pi-hole.net

This happens after trying pihole install once and then changing resolv.conf

4

What is in resolv.conf now?

cat /etc/resolv.conf | grep nameserver

What are the results of a dig for pi-hole.net from the Pi terminal

dig install.pi-hole.net

5

I tried fresh install of raspbian and hence pihole.

nameserver before pihole install was set to 8.8.8.8 but after install failed the config file was blank. Did set it to google DNS again and then ran DIG command

6 
   pi@raspberrypi:~ $ dig install. pi-hole. net

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> install.pi-hole.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16081
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;install.pi-hole.net. IN A

;; ANSWER SECTION:
install.pi-hole.net. 3599 IN CNAME guinan.pi-hole.net.
guinan.pi-hole.net. 3599 IN A 78.46.180.80

;; Query time: 95 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Feb 05 03:28:18 GMT 2020
;; MSG SIZE rcvd: 85

  1. pihole not found
    pi@raspberrypi:~ $ pihole -r
    -bash: pihole: command not found
  2. Even though

pi@raspberrypi:~ $ cat /etc/resolv.conf | grep nameserver
nameserver 8.8.8.8

7

Now run the install curl script again.

8

pi@raspberrypi:~ $ curl -sSL https://install.pi-hole.net | bash
curl: (6) Could not resolve host: install.pi-hole.net

9

now apt-get update command is misbehaving too

pi@raspberrypi:~ $ sudo apt-get update
Err:1 http://raspbian.raspberrypi. org/raspbian buster InRelease
Temporary failure resolving 'raspbian. raspberrypi . org'
Err:2 http://archive.raspberrypi.org/debian buster InRelease
Temporary failure resolving 'archive. raspberrypi .org'
Reading package lists... Done
W: Failed to fetch http://raspbian. raspberrypi. org/raspbian/ dists/buster/InRelease Temporary failure resolving 'raspbian.raspberrypi .org'
W: Failed to fetch http://archive.raspberrypi. org/debian/dists/buster/InRelease Temporary failure resolving 'archive.raspberrypi. org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

10

This isn't a Pi-Hole problem at this point. Pi-Hole is not installed, your Pi can't reach the internet reliably using a third party nameserver. Check your ethernet cable if you are using one. What are you using for a power supply on the Pi-4?

What is the output of the following from the Pi:

ping -c3 8.8.8.8

ping -c3 google.com

ip addr

11

I'hv connected Pi using lan cable directly to my router (100 mbps). Using 5v 2A powersupply through type C port.

pi@raspberrypi:~ $ ping -c3 8.8.8.8
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=57 time=8.35 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=8.34 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=8.41 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 8.338/8.367/8.410/0.080 ms

pi@raspberrypi:~ $ ping -c3 google.com
ping: google.com: Temporary failure in name resolution

pi@raspberrypi:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether dc:a6:32:20:eb:23 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.119/24 brd 192.168.1.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::aba1:67d4:1b81:ccc9/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether dc:a6:32:20:eb:24 brd ff:ff:ff:ff:ff:ff
12

That is an inadequate power supply for that device. Raspberrypi.org specifies 15 watts, or 3 amps at 5V.

"* A good quality 2.5A power supply can be used if downstream USB peripherals consume less than 500mA in total."

You are short of both.

13

I think power supply is right because I have another Pi4 with same power supply and running OMV with HDD attached to USB.

Anyway, I got it. Somehow the nameserver was resetting back to 127.0.0.1.This time I tried 1.1.1.1 and then restarted pi(didn't restart earlier at all). Afterwards Curl command ran fine.

14

Good that it's sorted now. But, if you are running an inadquate power supply, you will soon have SD card failures. With inadequate power, the Pi won't write properly to the card. It may run for now, but it will fail early with inadequate power.

15

ohk..Thanks for info. I'll change them soon.

16

I am having the exact same problems on clean image Raspbian install on RPi3b+. I've tried new SD cards, a new power adapter, and even a new RPi3b+, without any luck. The install script seems to set DNS 127.0.0.1 "too early", and the rest of the script fails. If I set DNS to i.e. 8.8.8.8, I can now retry the install script, and it will succeed. But the Pi-hole installation will mess up the Raspbian system, eth0 has lots of problems, and in my case it always ends in system crash (kernel panic?).

I created a new post explaining my problems: [RESOLVED] Endless problems with Pi-hole after Raspbian 2020-02-05 update

And yes, this started immediately after the Feb 2020 Raspbian update.

17

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