Top blocked domain not showing any clients

[Valiceemo]

Expected behaviour

Clicking on the top blocked domain shows me the clients making the queries

Actual Behaviour:

Clicking on top blocked domains shows nothing in the query log with message No data available in table

EDIT:
Also noticed I'm at 80%+ blocked and the web UI is a bit sluggish loading data?

[deHakkelaar]

Looking up "No data available in table":

Query Log entries in future

I am having the same issue here. I have two versions of Pihole - one running on Ubuntu mate 16.04 which has dnsmasq 2.75 and one running under Raspbian. On the Ubuntu mate installation, my admin console is completely blank under 3.3. The dashboard appears identical to the image uploaded by starsick and the query page is blank and says "No data available in table". I made sure that the /var/log/pihole.log permissions were set to 644 and still no joy. When I downgraded to 3.2.1, everything worked …

Have you checked date/time ?

date

Start with a fresh pihole-FTL.db database ?

@DL6ER

sudo service pihole-FTL stop
sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL.db_
sudo service pihole-FTL start

Run debug and post token ?

How do I debug my Pi-hole installation?

Method 1: Generate a debug token via the Web interface Log in to your Pi-hole's Web interface Navigate to Tools > Generate debug log Click the Generate debug log button Send us the debug token [debug] Method 2: Use the command line to generate a debug token Login into your Pi-hole's command line Enter pihole -d Provide us with the debug token that is generated after the debug script completes Alternative: Securely sending us additional information Preferred Method If there is additi…

[jfb]

What is the output of the following command from the Pi terminal:

echo ">stats" | nc localhost 4711

[Valiceemo]

@jfb

What is the output of the following command from the Pi terminal:

echo ">stats" | nc localhost 4711

pi@pi-hole:~ $ echo ">stats" | nc 127.0.0.1 4711
domains_being_blocked 870543
dns_queries_today 4970
ads_blocked_today 3952
ads_percentage_today 79.517105
unique_domains 2267
queries_forwarded 1159
queries_cached 750
clients_ever_seen 16
unique_clients 7
dns_queries_all_types 6749
reply_NODATA 0
reply_NXDOMAIN 0
reply_CNAME 780
reply_IP 7749
status enabled
---EOM---

@deHakkelaar

Have you checked date/time ?

date

Date is showing correct

@deHakkelaar

Start with a fresh pihole-FTL.db database ?

Ideally I'd like to avoid this.

@deHakkelaar

Run debug and post token ?

5fw0hmna3j

[jfb]

When did this problem start? Did you make any changes to your Pi-Hole recently prior to this problem starting?

What are the outputs of:

stat /etc/pihole/pihole-FTL.db

stat /var/log/pihole.log

[Valiceemo]

Ok this is wierd....ran pihole -r and repaired.

Script ran and ended with DNS resolution not available

Reloaded pihole web UI, and blocked percentage dropped to ~60%, which is about normal for me and top blocked domains changed, with the one I quoted above nowhere to be seen?

[Valiceemo]

@jfb

When did this problem start? Did you make any changes to your Pi-Hole recently prior to this problem starting?

I noticed it today, and I've made no changes to my setup

@jfb

What are the outputs of:

stat /etc/pihole/pihole-FTL.db

stat /var/log/pihole.log

pi@pi-hole:~ $ stat /etc/pihole/pihole-FTL.db
  File: /etc/pihole/pihole-FTL.db
  Size: 11493376        Blocks: 22456      IO Block: 4096   regular file
Device: b302h/45826d    Inode: 123009      Links: 1
Access: (0644/-rw-r--r--)  Uid: (  999/  pihole)   Gid: (  996/  pihole)
Access: 2018-09-22 10:11:18.161712843 +0100
Modify: 2018-10-12 20:06:01.738040725 +0100
Change: 2018-10-12 20:06:01.738040725 +0100
 Birth: -
pi@pi-hole:~ $ stat /var/log/pihole.log
  File: /var/log/pihole.log
  Size: 1500810         Blocks: 2944       IO Block: 4096   regular file
Device: b302h/45826d    Inode: 2219        Links: 1
Access: (0644/-rw-r--r--)  Uid: (  999/  pihole)   Gid: (  996/  pihole)
Access: 2018-10-12 20:02:26.952964214 +0100
Modify: 2018-10-12 20:06:30.547380404 +0100
Change: 2018-10-12 20:06:30.547380404 +0100
 Birth: -

[jfb]

@Valiceemo

I noticed it today, and I’ve made no changes to my setup

With the changes you have made to the default cron scripts, your gravity list updates daily (not once a week). Updating gravity may have caused this.

-rw-r--r-- 1 root root 1496 Sep 26 11:34 /etc/cron.d/pihole
   48 4   * * *   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity

[Valiceemo]

@jfb

With the changes you have made to the default cron scripts, your gravity list updates daily (not once a week). Updating gravity may have caused this.

Hmmm, ok. I didn't think the change I made could every this, hence I didn't think about it, apologies!

Will pihole -r set the cron back to default?

[jfb]

I don't know without looking at the code. Run it and see if the cron changes.

[Valiceemo]

Running pihole -r did set the cron job back to once per week. I'll leave it and see if the problem comes back.
Out of interest, how would setting the cron to once per day cause this problem?

[jfb]

@Valiceemo

how would setting the cron to once per day cause this problem?

Changing a cron script itself would not directly cause the problem, but the fact that gravity updated that day may have had an effect on your Pi-Hole operation. In your previously reply, you noted you had made no changes to your setup, but a gravity update can change things.