Pi-hole on pogoplug pro

Help Community Help
1

Found an old Pogoplug Pro on the attic and decided to run pi-hole on it.

The device is running Debian Buster and is therefore "supported". Followed this small writeup (Running PiHole (network ad blocker) on a Pogoplug Pro) to get me started.

The pi-hole is running fine and (and it is blocking adds) I can even update it, whenever pi-hole detects there's a newer version available.

The problem is, even the update is ok (after restarting some services, or rebooting the device), but running pihole -up yields "Unable to complete update, please contact Pi-hole Support". This is the whole output:

root@pogo02:~# pihole -up
]  [i] Checking for updates...
  [i] Pi-hole Core:	up to date
  [i] Web Interface:	up to date
  [i] FTL:		update available

  [i] FTL out of date, it will be updated by the installer.

  [✓] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.3.19-1~deb10u1
  [i] Performing unattended setup, no whiptail dialogs will be displayed

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

  [i] Installer Dependency checks...
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail
  [✓] Checking for dnsutils

  [✓] Supported OS detected
  [i] SELinux not detected
  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] 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 libcap2
  [✓] Checking for lighttpd
  [✓] Checking for php7.3-common
  [✓] Checking for php7.3-cgi
  [✓] Checking for php7.3-sqlite3
  [✓] Checking for php7.3-xml
  [✓] Checking for php7.3-json
  [✓] Checking for php7.3-intl

  [✓] Enabling lighttpd service to start on reboot...
  [✓] Checking for user 'pihole'

  [i] FTL Checks...

  [✓] Detected ARMv5 (or newer) processor
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v5.6). Confirming Checksum...
  [i] Corruption detected...
  [✓] Downloading and Installing FTL
  [✓] 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
  [i] 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...
  Unable to complete update, please contact Pi-hole Support

Any reason why it fails to complete the update? I do realise this has to do with a more or less unsupported device, but I am trying to figure out what I need to change to let the update.
Many thanks in advance for your help.

2

Please run

sudo bash -x /opt/pihole/update.sh for a more verbose output.

7

Is this what you are looking for?

+ echo -e '  [i] FTL out of date, it will be updated by the installer.'
  [i] FTL out of date, it will be updated by the installer.
+ [[ true == true ]]
+ '/etc/.pihole/automated install/basic-install.sh' --reconfigure --unattended

  [✓] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.3.19-1~deb10u1
  [i] Performing unattended setup, no whiptail dialogs will be displayed

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

  [i] Installer Dependency checks...
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail
  [✓] Checking for dnsutils

  [✓] Supported OS detected
  [i] SELinux not detected
  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] 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 libcap2
  [✓] Checking for lighttpd
  [✓] Checking for php7.3-common
  [✓] Checking for php7.3-cgi
  [✓] Checking for php7.3-sqlite3
  [✓] Checking for php7.3-xml
  [✓] Checking for php7.3-json
  [✓] Checking for php7.3-intl

  [✓] Enabling lighttpd service to start on reboot...
  [✓] Checking for user 'pihole'

  [i] FTL Checks...

  [✓] Detected ARMv5 (or newer) processor
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v5.6). Confirming Checksum...
  [i] Corruption detected...
  [✓] Downloading and Installing FTL
  [✓] 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
  [i] 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...+ echo -e '\n  Unable to complete update, please contact Pi-hole Support'

  Unable to complete update, please contact Pi-hole Support
+ exit 1
8

I hoped for more ...
Please try

sudo bash -x pihole -up

Please look also for errors in /var/log/lighttpd/error.log

9

I was also hoping for more:

root@pogo02:~# bash -x pihole -up
+ readonly PI_HOLE_SCRIPT_DIR=/opt/pihole
+ PI_HOLE_SCRIPT_DIR=/opt/pihole
+ setupVars=/etc/pihole/setupVars.conf
+ PI_HOLE_BIN_DIR=/usr/local/bin
+ readonly colfile=/opt/pihole/COL_TABLE
+ colfile=/opt/pihole/COL_TABLE
+ source /opt/pihole/COL_TABLE
++ [[ -t 1 ]]
+++ tput colors
++ [[ 256 -ge 8 ]]
++ COL_BOLD=''
++ COL_ULINE=''
++ COL_NC=''
++ COL_GRAY=''
++ COL_RED=''
++ COL_GREEN=''
++ COL_YELLOW=''
++ COL_BLUE=''
++ COL_PURPLE=''
++ COL_CYAN=''
++ COL_WHITE=''
++ COL_BLACK=''
++ COL_LIGHT_BLUE=''
++ COL_LIGHT_GREEN=''
++ COL_LIGHT_CYAN=''
++ COL_LIGHT_RED=''
++ COL_URG_RED=''
++ COL_LIGHT_PURPLE=''
++ COL_BROWN=''
++ COL_LIGHT_GRAY=''
++ COL_DARK_GRAY=''
++ TICK='[✓]'
++ CROSS='[✗]'
++ INFO='[i]'
++ QST='[?]'
++ DONE=' done!'
++ OVER='\r'
+ [[ 1 = 0 ]]
+ case "${1}" in
+ [[ ! 0 -eq 0 ]]
+ case "${1}" in
+ updatePiholeFunc -up
+ shift
+ /opt/pihole/update.sh
  [i] Checking for updates...
  [i] Pi-hole Core:	up to date
  [i] Web Interface:	up to date
  [i] FTL:		update available

  [i] FTL out of date, it will be updated by the installer.

  [✓] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.3.19-1~deb10u1
  [i] Performing unattended setup, no whiptail dialogs will be displayed

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

  [i] Installer Dependency checks...
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail
  [✓] Checking for dnsutils

  [✓] Supported OS detected
  [i] SELinux not detected
  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] 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 libcap2
  [✓] Checking for lighttpd
  [✓] Checking for php7.3-common
  [✓] Checking for php7.3-cgi
  [✓] Checking for php7.3-sqlite3
  [✓] Checking for php7.3-xml
  [✓] Checking for php7.3-json
  [✓] Checking for php7.3-intl

  [✓] Enabling lighttpd service to start on reboot...
  [✓] Checking for user 'pihole'

  [i] FTL Checks...

  [✓] Detected ARMv5 (or newer) processor
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v5.6). Confirming Checksum...
  [i] Corruption detected...
  [✓] Downloading and Installing FTL
  [✓] 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
  [i] 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...
  Unable to complete update, please contact Pi-hole Support
+ exit 0

lighttpd error.log:

2021-01-01 16:53:20: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-01 16:55:18: (server.c.2059) server stopped by UID = 0 PID = 8191
2021-01-01 16:55:34: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-01 17:02:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  session_start(): open(/var/lib/php/sessions/sess_kjl6v66e6o2i92ngab6tnfa2jj, O_RDWR) failed: Permission denied (13) in /var/www/html/admin/scripts/pi-hole/php/password.php on line 12
2021-01-01 17:02:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/html/admin/scripts/pi-hole/php/password.php on line 12
2021-01-01 17:02:45: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  session_start(): open(/var/lib/php/sessions/sess_kjl6v66e6o2i92ngab6tnfa2jj, O_RDWR) failed: Permission denied (13) in /var/www/html/admin/scripts/pi-hole/php/password.php on line 12
2021-01-01 17:02:45: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/html/admin/scripts/pi-hole/php/password.php on line 12
2021-01-01 17:02:50: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  session_start(): open(/var/lib/php/sessions/sess_kjl6v66e6o2i92ngab6tnfa2jj, O_RDWR) failed: Permission denied (13) in /var/www/html/admin/scripts/pi-hole/php/password.php on line 12
2021-01-01 17:02:50: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/html/admin/scripts/pi-hole/php/password.php on line 12
2021-01-17 13:19:08: (server.c.2059) server stopped by UID = 0 PID = 10536
2021-01-17 13:19:24: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-20 19:06:04: (server.c.2059) server stopped by UID = 0 PID = 1935
2021-01-20 19:06:08: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-20 19:06:47: (server.c.2059) server stopped by UID = 0 PID = 2079
2021-01-20 19:06:58: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-20 19:07:14: (server.c.2059) server stopped by UID = 0 PID = 2300
2021-01-20 19:07:31: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-21 16:47:06: (server.c.2059) server stopped by UID = 0 PID = 26094
2021-01-21 16:47:23: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-24 09:21:25: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 0 in /var/www/html/pihole/index.php on line 228
2021-01-24 09:21:25: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 229
2021-01-28 19:18:09: (server.c.2059) server stopped by UID = 0 PID = 15369
2021-01-28 19:18:25: (server.c.1464) server started (lighttpd/1.4.53)
2021-01-28 19:24:34: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:24:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:24:54: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:25:05: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:25:16: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:25:27: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:25:38: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:25:49: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:26:00: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:26:11: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:26:22: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:26:33: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:26:44: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:26:55: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:27:06: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:27:17: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:27:28: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:27:39: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:27:50: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:28:01: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:28:12: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:28:24: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:28:35: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:28:52: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:29:04: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:29:15: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107
2021-01-28 19:29:27: (mod_fastcgi.c.421) FastCGI-stderr: PHP Notice:  Undefined offset: 2 in /var/www/html/admin/api_FTL.php on line 107

Nothing special here either :confused:

10

Some useful info, maybe, when performing an update I build a new version of the FTL library myself (no idea if this is still necessary, since I thought no builds for the pogoplug where available: Linux pogo02 4.14.198-oxnas-tld-1 #1 SMP PREEMPT Sun Sep 20 22:15:05 PDT 2020 armv6l GNU/Linux)

Then, I perform: pihole -up, which fails with aforementioned error
When I do: pihole -up again, it says this:

root@pogo02:~/FTL# pihole -up
  [i] Checking for updates...
  [i] Pi-hole Core:	up to date
  [i] Web Interface:	up to date
  [i] FTL:		up to date

  [✓] Everything is up to date!

So it has to do something with me compiling the FTL binary. Is this still necessary?

11

I'm out of ideas :man_shrugging:
Maybe someone with a Pogoplug and a working Pi-hole installation can help

13

You can look through all the posts on this forum related to Pogoplug and see if anybody has a solution:

https://discourse.pi-hole.net/search?q=pogoplug

14

Close, but that still fires off the actual update as a subprocess and eats the verbosity.

sudo bash -x '/etc/.pihole/automated install/basic-install.sh' --reconfigure --unattended

My guess is that you're missing the init system in the chroot jail you made. systemctl or service is not there or not allowed to execute.

1 Like
15

I can't answer that for your PogoPlug hardware.

Supporting precompiled FTL binaries for ARMv4, ARMv5 and ARMv8 was added with FTL v5.3.
ARMv6 with hard float(!) has been supported way back.

While v4 and v5 definitely lack hard float, v6 and v7 sit in between, as hard float is optional with them. Afaik all Raspberry Pi CPUs (including the v6 varieties) support hard float.
I am not sure about the PogoPlug hardware, though.

You probably could check your CPU Features for that:

cat /proc/cpuinfo
16 
root@pogo02:~# cat /proc/cpuinfo
processor       : 0
model name      : ARMv6-compatible processor rev 5 (v6l)
BogoMIPS        : 339.14
Features        : half thumb fastmult edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb02
CPU revision    : 5

processor       : 1
model name      : ARMv6-compatible processor rev 5 (v6l)
BogoMIPS        : 339.14
Features        : half thumb fastmult edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb02
CPU revision    : 5

Hardware        : Generic DT based system
Revision        : 0000
Serial          : 0000000000000000
root@pogo02:~#

Hmmm, so I guess this thing is supported after all and no need for me to compile my own FTL ?

17

pihole-FTL's binary for ARMv6 is targetting the hard float variant.

According to your above output, you are lacking a hardware floating point unit, as no vfp features are reported (and no asimd to be expected).

RPI Zero output for comparison (click) 
~ $ cat /proc/cpuinfo
processor       : 0
model name      : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS        : 697.95
Features        : half thumb fastmult vfp edsp java tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xb76
CPU revision    : 7

Hardware        : BCM2835
Revision        : 900093
Serial          : 0000000022840bee
Model           : Raspberry Pi Zero Rev 1.3

I'm not entirely certain yet whether that's really missing from your hardware.
(I think cpu id info is indeed read from the processor, but then matched against a table defined at compile-time. Chances are slim for vfp ids missing, though, especially with current kernels, but more exotic cpus might report features in a manufacturer dependent way)

What's the output of:

uname -m

ldd /bin/ls
18

In addition to what @Bucking_Horn said, I'd agree. We haven't had no-hard-float support before, but you may succeed in running a soft-float binary (armv5, for instance). With the extra output you were asked to provide, we may be able to improve the installer to detect scenarios where the processor is ARMv6 but no hard-float is available.

19

Many thanks for your help, so far.

root@pogo02:~# uname -m
armv6l
root@pogo02:~#

root@pogo02:~# ldd /bin/ls
	libselinux.so.1 => /lib/arm-linux-gnueabi/libselinux.so.1 (0xb6ec3000)
	libc.so.6 => /lib/arm-linux-gnueabi/libc.so.6 (0xb6d6e000)
	/lib/ld-linux.so.3 (0xb6f26000)
	libpcre.so.3 => /lib/arm-linux-gnueabi/libpcre.so.3 (0xb6cf5000)
	libdl.so.2 => /lib/arm-linux-gnueabi/libdl.so.2 (0xb6ce2000)
	libpthread.so.0 => /lib/arm-linux-gnueabi/libpthread.so.0 (0xb6cb7000)
root@pogo02:~#

own compiled pihole-FTL:

root@pogo02:~/FTL# ldd pihole-FTL
	libm.so.6 => /lib/arm-linux-gnueabi/libm.so.6 (0xb6be3000)
	librt.so.1 => /lib/arm-linux-gnueabi/librt.so.1 (0xb6bcc000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabi/libgcc_s.so.1 (0xb6b9d000)
	libpthread.so.0 => /lib/arm-linux-gnueabi/libpthread.so.0 (0xb6b72000)
	libc.so.6 => /lib/arm-linux-gnueabi/libc.so.6 (0xb6a1d000)
	/lib/ld-linux.so.3 (0xb6f82000)
root@pogo02:~/FTL# ldd /usr/bin/pi
pic              pico             piconv           pihole-FTL       pinentry         pinentry-curses  pinky

official pihole-FTL, I think:

root@pogo02:~/FTL# ldd /usr/bin/pihole-FTL
	libm.so.6 => /lib/arm-linux-gnueabi/libm.so.6 (0xb6bf1000)
	librt.so.1 => /lib/arm-linux-gnueabi/librt.so.1 (0xb6bda000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabi/libgcc_s.so.1 (0xb6bab000)
	libpthread.so.0 => /lib/arm-linux-gnueabi/libpthread.so.0 (0xb6b80000)
	libc.so.6 => /lib/arm-linux-gnueabi/libc.so.6 (0xb6a2b000)
	/lib/ld-linux.so.3 (0xb6f8b000)
root@pogo02:~/FTL#
23

Thank you.

All considered, Pi-hole's installer is correct in pulling ARMv5 binaries in your case, even if your actual CPU is ARMv6 (because it is lacking hard-float support).

"Corruption detected" was likely prompted by your self-compiled pihole-FTL binary.
Your self-compiled binary may still be more specific for your cpu, but it would prompt for update failures.
If running Pi-hole's ARMv5 binary is working for you, you should consider using that to allow for smooth updates in the future.

That would leave lighttpd as the remaining cause of failure.

Could you please provide output as requested by Dan?

24

I just checked that this exactly what the installer should do:

        # No hard-float support found: Use gnueabi binaries
        # Use the ARMv4-compliant binary only if we detected an ARMv4T core
        if [[ "${rev}" -eq 4 ]]; then
            printf "%b  %b Detected ARMv4 processor\\n" "${OVER}" "${TICK}"
            # set the binary to be used
            l_binary="pihole-FTL-armv4-linux-gnueabi"
        # Otherwise, use the ARMv5 binary. To date (end of 2020), all modern ARM processors
        # are backwards-compatible to the ARMv5
        else
            printf "%b  %b Detected ARMv5 (or newer) processor\\n" "${OVER}" "${TICK}"
            # set the binary to be used
            l_binary="pihole-FTL-armv5-linux-gnueabi"
        fi

And

Detected ARMv5 (or newer) processor

is correct. We may change this to

Detected ARMv5 (or newer) processor without hard-float support

if you think that is any better?

The corruption will come from the self-compiled binary which has a different checksum than the one we precompiled for download.

25

I think this is the most relevant part:

+ [[ baa482d31df91dd17350fb0bb31e8ee85bb43771 != \d\5\9\2\2\4\c\5\7\3\f\1\0\d\9\9\4\b\6\5\6\5\3\0\e\8\8\4\4\7\0\2\c\c\6\4\1\4\b\5 ]]
+ printf '  %b Corruption detected...\n' '[i]'
  [i] Corruption detected...
+ return 0
+ FTLinstall pihole-FTL-armv5-linux-gnueabi
+ local latesttag
+ local 'str=Downloading and Installing FTL'
+ printf '  %b %s...' '[i]' 'Downloading and Installing FTL'
  [i] Downloading and Installing FTL...++ mktemp -d
+ pushd /tmp/tmp.IvmSgoOD7U
+ install -T -m 0755 /etc/.pihole/advanced/Templates/pihole-FTL.service /etc/init.d/pihole-FTL
+ local ftlBranch
+ local url
+ [[ -f /etc/pihole/ftlbranch ]]
+ ftlBranch=master
+ local binary
+ binary=pihole-FTL-armv5-linux-gnueabi
+ [[ master == \m\a\s\t\e\r ]]
+ url=https://github.com/pi-hole/ftl/releases/latest/download
+ curl -sSL --fail https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv5-linux-gnueabi -o pihole-FTL-armv5-linux-gnueabi
curl: (23) Failed writing body (8687 != 16375)
+ popd
+ printf '%b  %b %s\n' '\r' '[✗]' 'Downloading and Installing FTL'
  [✗] Downloading and Installing FTL
+ printf '  %bError: URL %s/%s not found%b\n' '' https://github.com/pi-hole/ftl/releases/latest/download pihole-FTL-armv5-linux-gnueabi ''
  Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv5-linux-gnueabi not found
+ return 1
+ return 1
+ printf '  %b FTL Engine not installed\n' '[✗]'
  [✗] FTL Engine not installed
+ exit 1
root@pogo02:~/FTL#

And second try it succeeds :confused:

...
+ printf '  %b Corruption detected...\n' '[i]'
  [i] Corruption detected...
+ return 0
+ FTLinstall pihole-FTL-armv5-linux-gnueabi
+ local latesttag
+ local 'str=Downloading and Installing FTL'
+ printf '  %b %s...' '[i]' 'Downloading and Installing FTL'
  [i] Downloading and Installing FTL...++ mktemp -d
+ pushd /tmp/tmp.BfoLsYXYf4
+ install -T -m 0755 /etc/.pihole/advanced/Templates/pihole-FTL.service /etc/init.d/pihole-FTL
+ local ftlBranch
+ local url
+ [[ -f /etc/pihole/ftlbranch ]]
+ ftlBranch=master
+ local binary
+ binary=pihole-FTL-armv5-linux-gnueabi
+ [[ master == \m\a\s\t\e\r ]]
+ url=https://github.com/pi-hole/ftl/releases/latest/download
+ curl -sSL --fail https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv5-linux-gnueabi -o pihole-FTL-armv5-linux-gnueabi
+ curl -sSL --fail https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv5-linux-gnueabi.sha1 -o pihole-FTL-armv5-linux-gnueabi.sha1
+ sha1sum --status --quiet -c pihole-FTL-armv5-linux-gnueabi.sha1
+ printf 'transferred... '
transferred... + curl -sSL https://ftl.pi-hole.net/macvendor.db -o /etc/pihole/macvendor.db
+ chmod 644 /etc/pihole/macvendor.db
+ chown pihole:pihole /etc/pihole/macvendor.db
+ stop_service pihole-FTL
+ install -T -m 0755 pihole-FTL-armv5-linux-gnueabi /usr/bin/pihole-FTL
+ popd
+ printf '%b  %b %s\n' '\r' '[✓]' 'Downloading and Installing FTL'
  [✓] Downloading and Installing FTL
...
++ BLOCKING_ENABLED=true
++ PIHOLE_INTERFACE=eth0
++ IPV4_ADDRESS=192.168.0.2/24
++ IPV6_ADDRESS=
++ PIHOLE_DNS_1=8.8.8.8
++ PIHOLE_DNS_2=8.8.4.4
++ QUERY_LOGGING=true
++ INSTALL_WEB_SERVER=true
++ INSTALL_WEB_INTERFACE=true
++ LIGHTTPD_ENABLED=true
++ CACHE_SIZE=10000
+ [[ '' == \t\r\u\e ]]
+ [[ -f /etc/dnsmasq.d/02-pihole-dhcp.conf ]]
+ copy_to_install_log
+ sed 's/[[0-9;]\{1,5\}m//g'
+ chmod 644 /etc/pihole/install.log
+ [[ true == true ]]
+ pw=
++ grep WEBPASSWORD -c /etc/pihole/setupVars.conf
+ [[ 1 == 0 ]]
+ disable_resolved_stublistener
+ printf '  %b Testing if systemd-resolved is enabled\n' '[i]'
  [i] Testing if systemd-resolved is enabled
+ check_service_active systemd-resolved
+ is_command systemctl
+ local check_command=systemctl
+ command -v systemctl
+ systemctl is-enabled systemd-resolved
+ printf '%b  %b Systemd-resolved is not enabled\n' '\r' '[i]'
  [i] Systemd-resolved is not enabled
+ [[ true == true ]]
+ [[ true == true ]]
+ restart_service lighttpd
+ local 'str=Restarting lighttpd service'
+ printf '  %b %s...' '[i]' 'Restarting lighttpd service'
  [i] Restarting lighttpd service...+ is_command systemctl
+ local check_command=systemctl
+ command -v systemctl
+ systemctl restart lighttpd
root@pogo02:~/FTL#

Spooky. Anyway, since everything is working as it should, I guess we should drop this for now and maybe revisit this should I have problems on the next update.

Thanks for your help.

26

I have several Pogoplug's, both Pro's and the earlier versions. I have never had to compile for the Pro's. I couldn't tell whether you just tried a straight install without compiling?

For the older versions such as E02 and Mobile, the installer used to work but quit working with newer versions of Pi-Hole. I was then unable to to use the installer but compiling did work for some time. Then that stopped working with version 5 and I quit using the older Pogoplugs for Pi-Hole. As stated above there were some updates that should have allowed the armv5tel versions to work, but I've had no luck with it.

Ironically, I recently had both of my drives go bad almost simultaneously on my Pro's and I will be starting fresh again. I will use the installer but will refer to this post if I have any issues.

27

That's an issue. Something is ending the download before the entire body is written.

28

@bluzfanmr1 I installed pihole using these instructions: Running PiHole (network ad blocker) on a Pogoplug Pro

After installing (and not compiling FTL) I could see a red dot in the pihole user interface, indicating FTL was not running. After compiling it myself, everything started working.

Anyway, seems after upgrading the FTL github release seems to work as well. Let's see if I encounter any issues next time FTL updates.

Thanks.