Query Log entries in future

[bearymore]

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 fine.

On the raspbian system, I upgraded dnsmasq to 2.76 following the instructions on this site, checked the log permissions and had a slightly different result with 3.3. Here the dashboard is filled in correctly, but the query log is empty and says "No data available in table". Again, downgrading to 3.2.1 resolves the issue. I'm a bit confused here, as the upgrade of dnsmasq was given as a solution.

Any ideas?

[bearymore]

I just happened to click the show all queries link on the queries page and the total 12,687 queries indicated in the green box on the dashboard page showed up. However, they are all dated December 31, 2018, with the first supposedly occuring just after 12:00:01 and the last at 23:59:59. That is 2018 not 2017. I checked the system date on the Pi and it is correct. Could the problem be in the query logging itself?

[Mcat12]

Run pihole -d for a debug token.

[bearymore]

Here's the debug token: ijenolaswb

[Mcat12]

What is the output of this command?

echo ">getallqueries" | nc localhost 4711 | head

[DL6ER]

@bearymore Maybe you can find something useful here:

PiHole Query Log Only Contains Entries From 2018-12-31

Please follow the below template, it will help us to help you! Expected Behaviour: Query log should be showing current data. Actual Behaviour: In my Query log, all entries are dated 2018-12-31 and there are no new entries populating. Debug Token: The debug token is: kt9duh1knv I've been running pihole for a while now and blocking is working. Thank you very much for your dedication to this project! I happened to notice today, when I was setting up DHCP service, that the query log does not …

[bearymore]

@Mcat12

echo ">getallqueries" | nc localhost 4711 | head

Here is the output:

1546243212 IPv4 pubsub.pubnub.com 10.2.1.221 2 0
1546243214 IPv4 spool1.samsungcloudprint.com 10.2.1.100 2 0
1546243218 IPv4 ads.mopub.com 10.2.1.136 1 0
1546243236 IPv6 srv.myskybell.com 10.2.1.59 2 0
1546243236 IPv4 srv.myskybell.com 10.2.1.59 3 0
1546243265 IPv4 spool1.samsungcloudprint.com 10.2.1.100 2 0
1546243272 IPv4 pubsub.pubnub.com 10.2.1.221 3 0
1546243274 IPv6 srv.myskybell.com 10.2.1.59 3 0
1546243274 IPv4 srv.myskybell.com 10.2.1.59 3 0
1546243300 IPv4 ssl.google-analytics.com 10.2.1.136 1 0

[DL6ER]

@bearymore

1546243212 IPv4 pubsub.pubnub.com 10.2.1.221 2 0

Could you please try

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

I don't really think that this should resolve your issue, but it seem to have helped other users in the past.

[bearymore]

This seems to have worked. Thanks.

[bearymore]

I take it back. It worked, but now query logging is no longer working.

[mjnovak77]

Just wanted to let you all know I had this exact problem with the dates in the future. After following the instructions above to move the FTL.db file it is working normally again. Thanks!

[Mcat12]

Run pihole -d for a new debug token. I was on vacation for awhile, and the rest of the team has also been busy working on getting the next update out the door.