Empty dashboard

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

Expected Behaviour:

statistics should be shown

Actual Behaviour:

empty dashboard/spinning wheel

The browser cache I cleared. No differences between Firefox, Chrome, Safari.

pihole -r executed and rebooted, no changes

Debug Token:

y9jz6k4trg

How's your available space looking like ?

What's the output of df -h ?

> ZBOX ~ # df -h
> Filesystem                                  Size  Used Avail Use% Mounted on
> udev                                        3,8G     0  3,8G   0% /dev
> tmpfs                                       783M  9,5M  774M   2% /run
> /dev/mapper/mint--vg-root                    83G   16G   64G  20% /
> tmpfs                                       3,9G  776K  3,9G   1% /dev/shm
> tmpfs                                       5,0M  4,0K  5,0M   1% /run/lock
> tmpfs                                       3,9G     0  3,9G   0% /sys/fs/cgroup
> /dev/sda2                                   473M  259M  191M  58% /boot
> /dev/sda1                                   511M  4,7M  507M   1% /boot/efi
> cgmfs                                       100K     0  100K   0% /run/cgmanager/fs
> 192.168.1.2:/volume1/Daten                  7,0T  4,1T  3,0T  58% /mnt/nfs/Synology-Daten
> 192.168.1.2:/volume2/Sicherungen/ZBOX-Mint  7,3T  4,7T  2,6T  65% /mnt/nfs/Synology-Sicherung
> tmpfs                                       783M   24K  783M   1% /run/user/1000
> tmpfs                                       783M     0  783M   0% /run/user/999
   2018-07-15 11:26:50: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 191
   2018-07-15 11:26:50: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 192
   2018-07-15 11:42:49: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 191
   2018-07-15 11:42:49: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 192

and

 -----tail of gravity.list------
   zzztube.com
   zzzyzxxx.tumblr.com
   zzzz-m.tumblr.com
  �suchlackofads�

�suchlackofads� - this is not a valid entry.

See if removing this fixes the issue.

https://pgl.yoyo.org/adservers/

this is where the string is coming from.

Remove that list from your adlists, update gravity and try again.

Thank you for the hint. I deactivated this list and another one with the wrong DNS-entry

"c.smartclick.net

But both didn't help

If I open the query log comes the error

DataTables warning: table id=all-queries - Requested unknown parameter '1' for row 90, column 1. For more information about this error, please see 4. Warning: Requested unknown parameter

...now I will flush the logs

Clear the cache and cookies and reload the admin page.

Usually that error shows up when switching between versions (if I remember right, when downgrading).

I flused the cache, the cookies and the logs.
I repaired the pihole twice - first time with errors (Not FTL, no DNS-resolution)
Now it works again.

Thank you for your support.

the same behavior again today :exploding_head:

new debug token is: 88zg05hz96

Flushing cookies and cache didn't help

I installed pihole via pihole -r as a new installation. During installation some errors occures

  [i] Reconfigure option selected
  [✓] 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 interface: enp3s0
  [i] Using Google DNS servers
  [i] Static IP already configured
  [i] Found IPv6 ULA address, using it for blocking IPv6 ads
  [i] IPv4 address: 192.168.1.60/24
  [i] IPv6 address: fd00::9575:6756:3691:52f5
  [i] Web Interface On
  [i] Web Server On
  [i] Logging On.
  [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 bc
  [✓] 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 lighttpd
  [✓] Checking for php-common
  [✓] Checking for php-cgi
  [✓] Checking for php-sqlite3

  [✓] Enabling lighttpd service to start on reboot
  [✓] 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 Checks...
  [✓] Detected x86_64 architecture
  [i] Checking for existing FTL binary...
  [i] Checksum of installed binary matches remote. No need to download!


  [✓] Installing new IPTables firewall rulesets
  [i] Restarting services...
  [✓] Starting lighttpd service
  [✓] Enabling lighttpd service to start on reboot
  [✓] Starting pihole-FTL service
  [✓] Enabling pihole-FTL service to start on reboot
  [✓] Deleting existing list cache
  [✗] DNS resolution is currently unavailable
  [✗] DNS resolution is not available
ZBOX ~ # pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

... and the dashboard is still empty

You are running a system with dnsmasq version 2.75. The minimum version required is 2.76. What is the output from sudo systemctl status --full --no-pager dnsmasq.service?

ZBOX ~ # systemctl status --full --no-pager dnsmasq.service
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/dnsmasq.service.d
           └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
   Active: inactive (dead)

I'm a little confused. I thought dnsmasq was integrated into pihole and therefore up-to-date.
How can I update dnsmasq?

Many thanks, Marko

You might want to check your update manager and see if it a newer dnsmasq package is available for your Linux Mint.

You can always run

sudo apt-get update
sudo apt-get upgrade

and then check dnsmasq -v to see the dnsmasq version.

The standard procedures are done regularly and the system is up to date in this way.About an hour ago.

ZBOX ~ # apt-get update && apt-get upgrade
Ign:1 http://ftp.fau.de/mint/packages sylvia InRelease
OK:2 http://archive.canonical.com/ubuntu xenial InRelease
OK:3 http://ftp.fau.de/ubuntu xenial InRelease
Holen:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
OK:5 http://ftp.fau.de/ubuntu xenial-updates InRelease
OK:6 http://ftp.fau.de/ubuntu xenial-backports InRelease
OK:7 http://ftp.fau.de/mint/packages sylvia Release
Es wurden 107 kB in 1 s geholt (105 kB/s).
Paketlisten werden gelesen... Fertig
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

ZBOX ~ # dnsmasq -v
Dnsmasq version 2.75

You could try to search for the 2.76 package for your OS or (I would recommend this), switch to FTLDNS beta (doesn't rely on system's dnsmasq - comes with it's own tweaked code based on dnsmasq) and that will address your issue.

Setup might fail due to network manager.

You'll probably have to edit /etc/NetworkManager/NetworkManager.conf and comment out or remove the line with dns=dnsmasq

then sudo nano /etc/resolve.conf and edit 127.0.0.1 to 1.1.1.1.

Then run the code from the post above to get the beta version.

That procedure, should prevent errors during install.

RamSet, I'm very thankfull about your support. But I'm really irritated, because i thought i was in the beta branch/dev branch.

ZBOX ~ # pihole -v
  Pi-hole version is v3.3-186-g76c5b4a (Latest: v3.3.1)
  AdminLTE version is v3.2.1-195-g4355bde (Latest: v3.3)
  FTL version is vDev-5ecab0a (Latest: v3.0)

I've missed that in your debug token. Sorry.

Then dnsmasq is irrelevant in this case. It's supposed to be dead since FTLDNS took over.

I looked at it and I see the same errors you had yesterday:

   2018-07-15 11:26:50: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 191
   2018-07-15 11:26:50: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 192
   2018-07-15 11:42:49: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 191
   2018-07-15 11:42:49: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /var/www/html/pihole/index.php on line 192
   2018-07-15 18:10:32: (mod_fastcgi.c.2695) FastCGI-stderr: PHP Warning:  dns_get_record(): A temporary server error occurred. in /var/www/html/pihole/index.php on line 191```

There must be a bad entry in your gravity.list or some erroneous domain that's messing up the query.

What you could do, is to try to see if going (for testing purposes) with a blank adlists.list file and pihole -g after that.

Then if that fails, as a last resort, delete the /etc/pihole/pihole-FTL.db file.

Stop FTLDNS before deleting the db file and start it after.

sudo systemctl stop pihole-FTL.service
sudo rm -f /etc/pihole/pihole-FTL.db
sudo systemctl start pihole-FTL.service

That has no influence/ no effect.

delete the /etc/pihole/pihole-FTL.db file.

The wheel is gone. But the graphs too..

/etc/pihole/pihole-FTL.db is (was) the file with your history.

It's the file that stores the information needed for the graphs to render.

Your data will start to populate after a little use (check it in 60 minutes).

Since it was deleted, there is no information that the graphs can render.

Hi @RamSet,
after some hours...same problems again.

I would reinstall pinhole from scratch. Is the any tutorial how to remove the existing installation (dev-branch) and reinstall this one?

Thank you for your support!