Install fails

Help
1

Please see below. I cannot seem to get pi-hole installed, regardless of what distribution I try to install into.

How can I resolve this? it always seems to drop out of the script before it finishes:

[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: 159553
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 136325
[i] Nothing to whitelist!
[i] Number of regex filters: 0
[✓] Parsing domains into hosts format
[✓] Cleaning up stray matter

[✓] Force-reloading DNS service
[✓] DNS service is running
[i] Pi-hole blocking will be enabled
/usr/local/bin/pihole: line 296: pihole: command not found
root@LXC_NAME:~#

2

Share the full install log

3

Is there a way to force the installer to install 4.0 instead of 4.1?

4

Where is the log located? It should be of interest that this will not install on Debian either. It is currently my opinion there is an issue with the 4.1 installer script

5

Once Pi-hole is installed, you can use pihole checkout to switch to v4.0.

The install log is the terminal output of the installer.

6

Is /usr/local/bin in your PATH?

7

I cannot get it to install. Note at the bottom when it errors out, it calls a specific line of the script:

root@LXC_NAME:~# curl -sSL https://install.pi-hole.net | bash
stty: 'standard input': Inappropriate ioctl for device

  [✓] Root user check

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

  [✓] Disk space check
  [✓] Update local cache of available packages

  [✗] Checking apt-get for upgraded packages
      Kernel update detected. If the install fails, please reboot and try again
  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [i] Checking for dialog (will be installed)
  [✓] Checking for debconf
  [i] Checking for dhcpcd5 (will be installed)
  [i] Checking for git (will be installed)
  [✓] Checking for iproute2
  [✓] Checking for whiptail
  [i] Using Google DNS servers
  [i] Your static IPv4 address: 192.168.2.253/24
  [i] Your static IPv4 gateway: 192.168.2.254
  [✓] Set IP address to 192.168.2.253 
  You may need to restart after the install is complete
  [i] Found IPv6 ULA address, using it for blocking IPv6 ads
  [i] IPv4 address: 192.168.2.253/24
  [i] IPv6 address: fdb2:3ac7:94ce:0:a0f6:80ff:fec6:1854
  [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...
  [i] Checking for bc (will be installed)
  [✓] 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)
  [i] Checking for psmisc (will be installed)
  [✓] Checking for sudo
  [i] Checking for unzip (will be installed)
  [i] Checking for wget (will be installed)
  [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)
  [✓] Checking for resolvconf
  [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...
  [✓] Creating user 'pihole'
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [✓] No dnsmasq.conf found... restoring default dnsmasq.conf...
  [✓] 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

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...

  [✓] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [✓] Downloading and Installing FTL
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old

  [i] No active firewall detected.. skipping firewall configuration
  [i] man not installed
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [✓] Starting lighttpd service...
  [✓] Enabling lighttpd service to start on reboot...
  [i] Restarting services...
  [✓] Enabling pihole-FTL service to start on reboot...
  [✓] Starting 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: 159551
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 136324
  [i] Nothing to whitelist!
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [i] Pi-hole blocking will be enabled
/usr/local/bin/pihole: line 296: pihole: command not found
8

I'll ask again, is /usr/local/bin/ in your PATH? And there is an issue with your LXC container if there is an error of stty: ‘standard input’: Inappropriate ioctl for device displayed as there will be questions asked via whiptail which needs stdin.

9

It might not be in my path, as I just set:

echo "alias pihole='/usr/local/bin/pihole'" >> ~/.bash_aliases && source ~/.bash_aliases

How would I set it in my path, I am not a linux expert.

As far as ioctl/stdin, I have no clue what that means or how to address it. All I know is that I didn't have any issues installing pi-hole 4.0 on Debian Jessie.

If you have commands I need to try, please enumerate them and I will gladly try. Thank you for your help.

10

I am still having issues here, I attempted to add/confirm the PATH as you mentioned, using:

root@LXC_NAME:~# PATH=$PATH:~/usr/local/bin
root@LXC_NAME:~# PATH=~/user/local/bin:$PATH

And the install still crashes out:

/usr/local/bin/pihole: line 296: pihole: command not found

Thanks, please advise.
-Rob

11

You've added ~/usr/local/bin to the path which for the root user expands to /root/usr/local/bin/. Try just /usr/local/bin/ but that may not be enough if the script is unable to get input from stdin.

12

I don't understand anything about stdin. All I know is this worked perfectly with Pi-Hole 4.0 and something has changed in 4.1 so how I can I perform an install of 4.0 from scratch???

13

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