Cannot complete fresh install

craigim · May 25, 2019, 9:43pm

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

Expected Behaviour:

Pi-hole successfully installs

Actual Behaviour:

I have experienced the same problem expressed in Upgrade Fail Everytime After V4.0. In the past, I've always eventually given up and done a fresh install and it works thereafter.

This time I've tried two different ways to install and both have failed.

Hardware: Raspberry Pi 2 Model B Rev 1.1
OS: Raspbian Stretch Lite, 2019-04-08 release date

Steps:

Fresh burn of image with Etcher, added empty ssh file to root
Boot pi and ssh into it.
Change default password and hostname
Change locale to US and timezone to Pacific
sudo apt-get update && sudo apt-get dist-upgrade -y
test connection with ping google.com and get positive result
reboot

First attempt : curl -sSL https://install.pi-hole.net | bash
Result: -bash: bash: command not found

Second attempt: install git, clone project, run auto-install.sh
Result:

...
  [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@pihole:~/Pi-hole/automated install $ sudo ping google.com
ping: google.com: Temporary failure in name resolution

As far as I can tell, everything I'm doing is on the basic recommended hardware using the basic recommended operating system and following the basic recommended procedure. What step did I miss? What did the pi-hole install script do to kill my connectivity and what can I do to get it back?

I've been without my pi-hole on my network for a week now and it's insufferable. Please help me get it back!

Debug Token:

N/A, can't install

deHakkelaar · May 25, 2019, 11:23pm

pi@noads:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.9 (stretch)
Release:        9.9
Codename:       stretch

pi@noads:~ $ sudo grep -v '^#\|^$' -R /etc/apt/sources.list*
/etc/apt/sources.list:deb http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi
/etc/apt/sources.list.d/raspi.list:deb http://archive.raspberrypi.org/debian/ stretch main ui

pi@noads:~ $ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games

pi@noads:~ $ which bash
/bin/bash

pi@noads:~ $ dpkg -S /bin/bash
bash: /bin/bash

pi@noads:~ $ apt policy bash
bash:
  Installed: 4.4-5
  Candidate: 4.4-5
  Version table:
 *** 4.4-5 500
        500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
        100 /var/lib/dpkg/status

pi@noads:~ $ stat /bin/bash
  File: /bin/bash
  Size: 912712          Blocks: 1784       IO Block: 4096   regular file
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

pi@noads:~ $ file /bin/bash
/bin/bash: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=b1e8e19f3b7b388468f2914bfb2ae8ac6b9f0478, stripped

pi@noads:~ $ /bin/bash --version
GNU bash, version 4.4.12(1)-release (arm-unknown-linux-gnueabihf)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Anything different on your Pi ?
Could be power related as this should not happen.
Have you tried another power source (and maybe need to flash SD again too) ?

deHakkelaar · May 25, 2019, 11:37pm

Ow and run below one to get name resolution back temporarily:

echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf

craigim · May 26, 2019, 7:53pm

One slight difference:

pi@pihole:~ $ stat /bin/bash
  File: /bin/bash
  Size: 912712          Blocks: 1784       IO Block: 4096   regular file
Device: b302h/45826d    Inode: 966         Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2019-04-08 03:25:19.077722802 -0700
Modify: 2017-05-15 12:45:32.000000000 -0700
Change: 2019-04-08 03:24:45.806383429 -0700
 Birth: -

Otherwise identical. I can try another power supply, but the one I'm using is a 60 W Anker that at one point I had 3 pis and 2 hard drives plugged into. It's a beast. I will also try flashing again.

However, I will say that this has happened pretty much every time I've upgraded Pi-Hole. It updates, seems to work for a while, and then DNS resolution stops (thus pinging google to test). I end up searching around for fixes and usually end up giving up and doing a fresh install which up until now has fixed the problem. One time I even switched to another Pi and switched SD cards. Two updates ago I upgraded my router and I've moved across the country since the last update, so this is a problem that transcends time and space.

deHakkelaar · May 26, 2019, 8:22pm

Not different, I only posted relevant info from my output.
Was looking for Size, if regular file and not symlinked, permissions and ownership of the file.

Did you install other software besides Pi-hole ?

The Pi-1B that I have Pi-hole running on is doing so for more then two years now with no issues at all.
Bash is part of the Raspbian installation and not Pi-hole.
Pi's are known to be power critical.
Dont connect too many power hungry USB devices to the Pi.
Also suspect the USB cable your using to power the Pi.
Less likely but still, it might be that your SD card is malfunctioning intermittently:

craigim · May 26, 2019, 8:23pm

Once I made this change (I actually went with 9.9.9.9), I was able to run the manual install, but the curl method still wouldn't work.

pi@pihole:~ $ curl -sSL https://install.pi-hole.net | bash
-bash: bash: command not found
curl: (23) Failed writing body (2182 != 2759)

So, for now my immediate problem (can't install) is solved.

deHakkelaar · May 26, 2019, 8:25pm

And below one ?

curl -sSL https://install.pi-hole.net | sudo bash -x

deHakkelaar · May 26, 2019, 8:27pm

And below three ?

df -h

free -h

mount | grep ' / '

EDIT: added some

craigim · May 26, 2019, 8:34pm

Only git. I previously had PADD installed and will be reinstalling, but that's been running just fine for the last 6 months.

Just before the failed update, my 2B had an uptime of 60+ days. It's been running pihole for two years without problems and the only reason I moved from the 1B to the 2B was because I bought a new 3 and had a spare 2B from another project and wanted the web interface to be a little snappier. The previous 1B had been running for a year before that. The only problems I ever have is when I try to install a pihole update. Once I fight my way through that, things run pretty smoothly.

craigim · May 26, 2019, 8:38pm

Now that pihole is successfully installed, the script runs both with and without the -x, so that, unfortunately, ins't going to help you.

pi@pihole:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        59G  1.2G   55G   3% /
devtmpfs        484M     0  484M   0% /dev
tmpfs           488M   96K  488M   1% /dev/shm
tmpfs           488M   13M  476M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           488M     0  488M   0% /sys/fs/cgroup
/dev/mmcblk0p1   43M   23M   21M  53% /boot
tmpfs            98M     0   98M   0% /run/user/1000
tmpfs            98M     0   98M   0% /run/user/999

pi@pihole:~ $ free -h
              total        used        free      shared  buff/cache   available
Mem:           975M         56M        781M         20M        137M        850M
Swap:           99M          0B         99M

pi@pihole:~ $ mount | grep ' / '
/dev/mmcblk0p2 on / type ext4 (rw,noatime)

deHakkelaar · May 26, 2019, 8:43pm

Try run debug again and post token so the devs can have a looksee:

pihole -d

craigim · May 26, 2019, 8:59pm

OK, so things aren't perfect. Between the previous post and now, I was looking at my router setup and saw that I had 9.9.9.9 as my secondary backup DNS. I removed that line to make my pihole the only DNS. Before I did, I had run pihole -d and everything looked normal. After, I get this:

[?] Would you like to upload the log? [y/N] y
    * Using curl for transmission.
[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole_debug.log

The two entries with red text are for the IPv6 addresses don't match (they did match before I removed the quad9 DNS entry) and the IPv6 name resolution. I used to have a script setup with a cron entry to periodically check the IPv6 address and update it to match, but I haven't set that back up, yet.

Even though I can't upload the log, I can ping google.com and I opened some links that I know aren't in my cache and they loaded up quickly.

deHakkelaar · May 26, 2019, 9:09pm

Below one allows you to upload the log and receive a token:

nc tricorder.pi-hole.net 9999 < /var/log/pihole_debug.log

You can test name resolution on Pi-hole or a client PC with the nslookup command:

pi@noads:~ $ nslookup pi.hole 10.0.0.2
Server:         10.0.0.2
Address:        10.0.0.2#53

Name:   pi.hole
Address: 10.0.0.2

C:\>nslookup doubleclick.com 10.0.0.2
Server:  noads.dehakkelaar.nl
Address:  10.0.0.2

Name:    doubleclick.com
Addresses:  ::
          0.0.0.0

EDIT: canged some so wont need cat

craigim · May 26, 2019, 10:56pm

I think that worked to upload (there was no error), but I didn't get a token.

deHakkelaar · May 26, 2019, 10:59pm

Its mangled at the end:

pi@noads:~ $ nc tricorder.pi-hole.net 9999 < /etc/resolv.conf
https://tricorder.pi-hole.net/sr0yvzasrypi@noads:~ $

This part:

https://tricorder.pi-hole.net/sr0yvzasry

craigim · May 26, 2019, 11:01pm

Token: scaa9ydkfb

technicalpyro · May 27, 2019, 12:02am

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain 
[✓] webroot.112.2o7.net is :: via localhost (::1) 
[✗] Failed to resolve webroot.112.2o7.net via Pi-hole (2605:e000:1523:cc:3b90:ae2c:27e6:ce73)
 [✓] doubleclick.com is 2607:f8b0:4007:804::200e via a remote, public DNS server (2001:4860:4860::8888)

is the only error i see at the moment

system · June 17, 2019, 12:03am

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