Pihole fails to install on Pogoplug Arm box Debian 8.11 / 9.8 , Pihole-FTL won't install / failed to start


#1

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

Expected Behaviour:

New installation

Actual Behaviour:

Install script will fail with error:
Error Dnsmasq bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf

tried

 **pihole checkout ftl master**
 *[✓] Detected ARM architecture*
*  [✓] Branch master exists*
*  [✓] Downloading and Installing FTL*
*  [i] Restarting pihole-FTL service...*
*root@debian:~# pihole-FTL*
*-bash: /usr/bin/pihole-FTL: No such file or directory*

tried on debian 9.8 box

**pihole -r**
 [✓] Enabling lighttpd service to start on reboot...

  [i] FTL Checks...

  [✓] Detected ARM architecture
  [i] Checking for existing FTL binary...
/etc/.pihole/automated install/basic-install.sh: line 2358: /usr/bin/pihole-FTL: No such file or directory
  [✓] Downloading and Installing FTL
  [✓] Checking for user 'pihole'
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old
  [✓] man pages installed and database updated
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [i] Restarting lighttpd service...
root@debian:~# pihole-FTL
-bash: /usr/bin/pihole-FTL: No such file or directory

tried
pihole -r
on debian 8.11

 [✓] Enabling lighttpd service to start on reboot...

  [i] FTL Checks...

  [✓] Detected ARM architecture
  [i] Checking for existing FTL binary...
/etc/.pihole/automated install/basic-install.sh: line 2358: /usr/bin/pihole-FTL: No such file or directory
  [✓] Downloading and Installing FTL
  [✓] Checking for user 'pihole'
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old
  [✓] man pages installed and database updated
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [✓] Restarting lighttpd service...
  [✓] Enabling lighttpd service to start on reboot...
  [i] Restarting services...
  [✓] Enabling pihole-FTL service to start on reboot...
  [✓] Restarting pihole-FTL service...
  [✓] Deleting existing list cache
  [i] Pi-hole blocking is enabled
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 134827
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 112384
  [i] Nothing to whitelist!
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter
  [✓] Starting DNS service

  [✗] DNS service is NOT running
/opt/pihole/updatecheck.sh: line 75: /usr/bin/pihole-FTL: No such file or directory
/opt/pihole/updatecheck.sh: line 88: /usr/bin/pihole-FTL: No such file or directory

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

  Current Pi-hole version is v4.2.2
  Current AdminLTE version is v4.2
/opt/pihole/version.sh: line 19: /usr/bin/pihole-FTL: No such file or directory
  Invalid Option! Try 'pihole -v --help' for more information.

Debug Token:

debian 9.8 box
https://tricorder.pi-hole.net/gw8yr5ah10!

debian 8.11 box
https://tricorder.pi-hole.net/jg2unyqya9!


#2

I understand pihole-FTL is a custom version of dnsmasq, so when it runs, the standard dnsmasq won’t run?

Any idea why pihole-FTL can’t be installed?
Is it because the error:
dnsmasq bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf

That line seems to be
dhcp-name-match=set:wpad-ignore,wpad

with this line, the standard dnsmasq won’t start as well.


#3

When pihole-FTL runs, dnsmasq cannot run as a separate process since they both require the same ports.

The conflict may be between pihole-FTL and an existing dnsmasq process. On the Debian 9 install, what are the outputs of the following commands:

sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'

sudo service pihole-FTL status


#4

On the Debian 8.11 system
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1686/lighttpd
tcp6 0 0 :::80 :::* LISTEN 1686/lighttpd

sudo service pihole-FTL status
sudo: unable to resolve host debian8


#5

It turns out that the release bin from git for pihole FTL engine is not compatible for pogoplug arm debian boxes:
Pogoplug E02 Jessie 8.11 gcc 4.9.2 kernel 4.20.6-kirkwood-tld-1
Pogoplug P21 Stretch 9.8 gcc 6.3 kernel 4.4.176-oxnas-tld-1

apt install ca-certificates
apt-get update
apt-get upgrade
apt-get install fake-hwclock
curl -sSL https://install.pi-hole.net | bash

after running the install script and failed at FTL not installed/failed to start, do the following to continue installing the pihole FTL DNS server:

apt install build-essential libgmp-dev m4
wget https://ftp.gnu.org/gnu/nettle/nettle-3.4.tar.gz      
tar -xvzf nettle-3.4.tar.gz
cd nettle-3.4
./configure
make
make install


git clone https://github.com/pi-hole/FTL.git
cd FTL
make -j 4
make install
service pihole-FTL restart

This would pull the FTL code from git and compile, which fixed the problem on the E02 Kirkwood box.

However FTL will fail to compile on the P21 Stretch 9.8 gcc 6.3 oxnas box with this error:
cc: internal compiler error: Killed (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
Makefile:98: recipe for target ‘obj/sqlite3.o’ failed
make: *** [obj/sqlite3.o] Error 4

what is preventing the code from compiled here?

From the link here, maybe upgrade sqlite from 3 to 4 could solve the problem?


#6

That GitHub repo is for node-sqlite3, not sqlite. The arm build we support is targeted at Raspberry Pis (1B, 1B+, and Zero), whose architecture can be described as armv6hf. Your device is most likely armv6 or armv5, which may not be supported by SQLite. We do not modify the source code of SQLite, so you may need to contact them for more information on why it will not build.


#7

Thanks. I guess that’s the case.

The POGO-E02 has Marvell Kirkwood 1.2GHz which is ARMv5te, that builds FTL fine.
The PLX-NAS7820 based POGO-P21 is plain ARMv6, even archlinux arm has dropped support to this one. Similar boxes are:

MEDION LIFE P89626 NAS
Pogoplug Pro/Video/v3
Iomega Home Media Network Hard Drive, Cloud Edition