Empty /etc/pihole after re install

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

Expected Behaviour:

Content available in /etc/pihole or error was thrown on installation

Actual Behaviour:

No errors on installation, folder /etc/pihole is empty, FTL is missed as well.

Debug Token:

Not able to get debug token as pihole is missed

Today I've found that admin panel not able to load all data. Ran installation again. FTL pop up, but admin was still empty. I've uninstall and than install pihole again.
Now folder /etc/pihole is empty, folder /opt/pihole is not exist. No errors during installation. Web admin loads, with no data, shows FTL offline.
No idea how to process further :frowning:
No pihole-FTL:
ls /etc/init.d/pihole-FTL :frowning:
ls: cannot access /etc/init.d/pihole-FTL: No such file or directory

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

[✓] Root user check

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

[✓] 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

[✓] Stopping dnsmasq service...

[✓] Stopping lighttpd service...
[i] Using Google DNS servers
[i] Static IP already configured
[i] IPv4 address:
[i] IPv6 address:
[i] Web Interface On
[i] Logging On.
[✓] Check for existing repository in /etc/.pihole
[✓] Update repo in /etc/.pihole

[✓] Check for existing repository in /var/www/html/admin
[✓] Update repo in /var/www/html/admin

[i] Main Dependency checks...
[✓] Checking for bc
[✓] Checking for cron
[✓] Checking for curl
[✓] Checking for dnsmasq
[✓] Checking for dnsutils
[✓] Checking for iputils-ping
[✓] Checking for lsof
[✓] Checking for netcat
[✓] Checking for sudo
[✓] Checking for unzip
[✓] Checking for wget
[✓] Checking for idn2
[✓] Checking for lighttpd
[✓] Checking for php5-common
[✓] Checking for php5-cgi
[✓] Checking for php5-sqlite

[i] Enabling lighttpd service to start on reboot...#

My server is:
uname -a :frowning:
Linux bananapro 4.8.4-sunxi #6 SMP Sun Oct 23 15:55:47 CEST 2016 armv7l GNU/Linux
Debian GNU/Linux 7 (wheezy)

Wheezy is not supported anymore. Debian Stretch is the current release, and we have problems with Jessie, which is the release previous to Stretch. Wheezy is not even supported by Debian anymore. I would suggest getting an updated image.

1 Like

Thanks for reply, is it possible to install some of the previous version that supports Jessie?

Thanks Jacob for your links ...
Feels bad my self, as didn't find that before :frowning:

My receipt to fix that issue:

  1. Install latest version:
    curl -sSL https://install.pi-hole.net | bash
  2. Change pihole to v3.2:
    cd /etc/.pihole
    sudo git fetch --tags
    sudo git checkout v3.2
  3. Change admin to v3.2:
    sudo git fetch --tags
    sudo git checkout v3.2
  4. Run repair for your fetched pihole version:
    cd /etc/.pihole/
    bash pihole -r
  5. Update pihole ftl:
    pihole checkout ftl v2.13.2
  6. Restart lighttpd:
    service lighttpd restart
  7. Might be needed to restart pihole-ftl service as well:
    service pihole-FTL restart

And finally everything is works again!

P.S: Correction, due to this issue changed pihole from 3.2 to 3.2.1: Settings.php in v3.2 doesn't work with Wheezy, CentOS 7 · Issue #628 · pi-hole/AdminLTE · GitHub

1 Like

How about to add some type of capability check on upgrade procedure?
Let's say if my OS is Jessy, and pihole not support that, then abort upgrade with a proper message ... may be include link to FAQ why that issue occurred?

The problem is that it'll always be your local update script that does it, i.e. only an already updated version (that means non-working on Jessie) could include the check. We argued back and forth about this and eventually decided that the next version will be Pi-hole v4.0 featuring FTLDNS (you might have seen our announcement of the beta testing phase) which will restore compatibility with Jessie. We'd highly appreciate it if you join the testing phase, especially as Jessie user! We think FTLDNS is almost finished (requires only some more polishing in some areas) but appreciate the chance to get early on user feedback, hoping to be able to release a bug-free :tm: version :wink:


Is that my "local update script" never updates? It should right?

Yes, but the following happens:

  1. Your local script pulls in all updates
  2. The installer runs and updates your local script

As you can see, the local script gets updated, but not early enough to prevent the update from happening just right now. An example:

3.3 does not work, we would release a fix for the updater in 3.3.1. Still, 3.3.1 would be installed (as your local script is still of version 3.3 at the point your updater runs) and we could only take care then that 3.3.2 would not be installed.

However, this detection would be quite complicated and we rather decided to go to v4.0 instead of releasing a v3.3.2, so a fix in v3.3.1 would have been useless while it would have also been a lot of work.

Thanks, understood.

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