DNS Will Not Start - Illegal Instruction (possibly downgrade FTL to v2.13.2?)

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

Trying to get Pi-hole running on an old i86 system running Debian 8 /
Found out about the dnsmasq v2.72 issue, following instructions to downgrade at:

All of the steps work except the last (downgrading FTL):
pihole checkout ftl v2.13.2

Expected Behaviour:

Branch v2.13.2 exists

Actual Behaviour:

Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y

[✓] Detected 32bit (i686) architecture
[✗] Requested branch "v2.13.2" is not available
[i] Available branches for FTL are:
- bughaunting/overTime
- development
- feature/deb-and-rpm
- fix/dnssec-retry-crash
- fix/issue_template
- fix/msatter_crazy_IPv6
- master
- master-find-missing-reference
- new/CNAME_inspection_details
- new/GeoIP
- new/NAPTR
- new/http
- release/v5.0
- tweak/blocked_counting
- tweak/external_blocked_IPs
- tweak/gcc_pipe
- tweak/log_upstream_errors
- tweak/remove-unused-FTL-var
- update/dnsmasq
- update/sqlite_3.31.1

Debug Token:

Your debug token is: https://tricorder.pi-hole.net/h6os82sitq

Those instructions are 2 years old. Currently FTL is version 4+.

I realize that. I am trying to make use of some good, old hardware rather than waste it. Debian dropped support for older CPU architectures in 9, that's why I am intentionally running an older version. The stable release of dnsmasq for Jessie is v2.72.

Is FTL v.2.13.2 still out there in the world somewhere?

What version of Pi-Hole are you currently running? pihole -v

I originally loaded the latest version from the script and then reverted to v3.2.1 per the checkout instructions above.

Did the latest version fail to work? If so, what was the error?

The latest version installed but the DNS service would not start. I believe this is due to FTL utilizing a newer version of dnsmasq, but the stable release of dnsmasq for Jessie is v2.72. That's why I am trying to roll FTL back to an earlier version, but either that version is no longer available in the checkout branch, or it has just moved somewhere else and I need to know where to point pihole checkout to get it. It seems odd that all of the prior versions of pi-hole are made available to load but the dependencies (FTL) are not.

The latest 4.x version of Pi-Hole will run on Jessie. Let's look at why the DNS service won't start.

sudo service pihole-FTL status

I don't have a port forwarded to get into that box remotely, but when I am back at it physically I'll uninstall pi-hole and then reinstall the latest version from the script and post that info.

pihole@pihole:~$ sudo curl -sSL https://install.pi-hole.net | bash

  [✗] Root user check
  [i] Script called with non-root privileges
      The Pi-hole requires elevated privileges to install and run
      Please check the installer for any concerns regarding this requirement
      Make sure to download this script from a trusted source

  [✓] Sudo utility check

  [✓] Root user check

         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
                 .. ','.
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........

  [i] Existing PHP installation detected : PHP version 5.6.40-0+deb8u8
  [✓] Disk space check
  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... up to date!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Using Level3
  [i] Static IP already configured
  [i] IPv4 address:
  [i] IPv6 address:
  [i] Web Interface On
  [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
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [✓] Checking for libcap2
  [✓] Checking for lighttpd
  [✓] Checking for php5-common
  [✓] Checking for php5-cgi
  [✓] Checking for php5-sqlite

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

  [i] FTL Checks...

  [✓] Detected 32bit (i686) architecture
  [i] Checking for existing FTL binary...
  [✓] 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] FTL can now resolve DNS Queries without dnsmasq running separately
  [✓] Stopping dnsmasq service...
  [✓] Disabling dnsmasq service...
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old

  [i] Skipping firewall configuration
  [✓] 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
  [✗] DNS service is not running
  [✓] Restarting DNS service
  [✗] DNS resolution is not available

pihole@pihole:~$ sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL)
   Active: active (exited) since Mon 2020-02-03 09:52:21 HST; 3min 10s ago
  Process: 1698 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 1704 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Feb 03 09:52:21 pihole pihole-FTL[1704]: Not running
Feb 03 09:52:21 pihole su[1733]: Successful su for pihole by root
Feb 03 09:52:21 pihole su[1733]: + ??? root:pihole
Feb 03 09:52:21 pihole su[1733]: pam_unix(su:session): session opened for u...0)
Feb 03 09:52:21 pihole pihole-FTL[1704]: Illegal instruction
Feb 03 09:52:21 pihole systemd[1]: Started LSB: pihole-FTL daemon.
Hint: Some lines were ellipsized, use -l to show in full.

Any ideas on this one?

Perhaps dnsmasq 2.80 is not supported on Jessie with an i86. This version of dnsmasq is in pihole-FTL.

What is the output of the following commands from the Linux terminal:

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

dig chaos txt version.bind +short

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0    *               LISTEN      1563/lighttpd
tcp6       0      0 :::80                   :::*                    LISTEN      1563/lighttpd
pihole@pihole:~$ dig chaos txt version.bind +short

(no output)

There is no instance of dnsmasq running, so no interference with pihole-FTL being able to launch due to a port conflict. It may just be an OS incompatibility.

I'd spring for the $10 for a Pi Zero W and install Buster and Pi-Hole on it.

So back to my original question then, where can I get FTL v2.13.2 if I want to try to run 3.2.1?

I'm not looking to force update dnsmasq or anything from another repository because it's going to also pull it's dependencies from a newer version and break all kinds of stuff, I just want to run an older version of pi-hole with an older version of FTL but the given command "pihole checkout ftl v2.13.2' does not work because that file is not where it used to be. Is it somewhere else? Can I grab it manually from somewhere?

If I can't get it to work, I'll just build a hosts file and throw it on my router, but the whole point of this project is to make use of hardware I already have. I know I can just go by a new pi for $10, that's not the point.

Perhaps one of the developers will know if this much older version of FTL is still available. Stand by.

Well I think I did end up finding the file I need at:


but I'm not sure what to do with it. Is it source? It doesnt look to be a tarball.
Can I force checkout to pull from here?

It's not supported in any way. Sorry to be blunt but you're on your own.

Edit: 2.13.12 released on Jan 7, 2018.

Fair - but just to be clear, but are you saying the old version or the current version on i86 is not supported?