Historical data, lists, graphs don't work

hdnwfsjv0v

None of the historical data is available to sort through or browse. The main screen is showing that its blocking, with statistics. But long-term data requests never resolve.

Do you have a debug token?

Do the data requests seem to time out? Open the dev tools (F12) and check if there's any errors in the console or network tabs.

Debug token is listed in my original post.

No errors under dev tool window on any page or tab in the UI.

Historical data is still a no-show.

Debug tokens have a TTL of 48 hours.

The one provided above is expired/no longer available.

Here's a new one, thanks.

lbakvo1uqf

The historical data is served up from the logs, so let's clear them and restart logging. On the Pi-Hole web admin page, under Settings - System, click the box for "disable query logging and flush logs." After that process is complete, re-enable query logging.

OK, done. I had flushed the logs before, lots of times actually, but never disabling while clearing. I'll give it a few hours and see what happens.

A cron script rotates the logs nightly, so see if that works properly for a few nights as well.

No effect whatsoever. Still no historical data.

Let's run a quick check on your SD card space - please paste output of

df -h -a

pi@pi-hole:~ $ df -h -a
df: /proc/sys/fs/binfmt_misc: No such device
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G  1.7G   26G   6% /
devtmpfs        460M     0  460M   0% /dev
sysfs              0     0     0    - /sys
proc               0     0     0    - /proc
tmpfs           464M     0  464M   0% /dev/shm
devpts             0     0     0    - /dev/pts
tmpfs           464M   24M  441M   6% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           464M     0  464M   0% /sys/fs/cgroup
cgroup             0     0     0    - /sys/fs/cgroup/systemd
cgroup             0     0     0    - /sys/fs/cgroup/cpu,cpuacct
cgroup             0     0     0    - /sys/fs/cgroup/net_cls
cgroup             0     0     0    - /sys/fs/cgroup/cpuset
cgroup             0     0     0    - /sys/fs/cgroup/devices
cgroup             0     0     0    - /sys/fs/cgroup/freezer
cgroup             0     0     0    - /sys/fs/cgroup/blkio
mqueue             0     0     0    - /dev/mqueue
sunrpc             0     0     0    - /run/rpc_pipefs
debugfs            0     0     0    - /sys/kernel/debug
configfs           0     0     0    - /sys/kernel/config
/dev/mmcblk0p1   41M   22M   19M  54% /boot
tmpfs            93M     0   93M   0% /run/user/999
tmpfs            93M     0   93M   0% /run/user/1000
pi@pi-hole:~ $

Log into the web interface, then open a new tab and go to http://pi.hole/admin/api_db.php?getGraphData

Share the output.

{"domains_over_time":{"1517376600":235,"1517377200":592,"1517377800":1070,"1517378400":642,"1517379000":302,"1517379600":683,"1517381400":115,"1517382000":778,"1517382600":400,"1517383200":210,"1517383800":393,"1517384400":941,"1517385000":557,"1517385600":353,"1517386200":425,"1517386800":407,"1517387400":336,"1517388000":384,"1517388600":429,"1517389200":115,"1517389800":64,"1517390400":153,"1517391000":100,"1517391600":141,"1517392200":631,"1517392800":635,"1517393400":288,"1517394000":111,"1517394600":949,"1517395200":120,"1517395800":397,"1517396400":1389,"1517397000":711,"1517397600":230,"1517398200":288,"1517398800":297,"1517399400":487,"1517400000":266,"1517400600":423,"1517401200":451,"1517401800":508,"1517402400":179,"1517403000":344,"1517403600":347,"1517404200":215,"1517404800":514,"1517405400":425,"1517406000":237,"1517406600":210,"1517407200":379,"1517407800":157,"1517408400":122,"1517409000":118,"1517409600":112,"1517410200":115,"1517410800":111,"1517411400":112,"1517412000":108,"1517412600":113,"1517413200":109,"1517413800":110,"1517414400":112,"1517415000":115,"1517415600":116,"1517416200":116,"1517416800":111,"1517417400":123,"1517418000":121,"1517418600":104,"1517419200":120,"1517419800":114,"1517420400":109,"1517421000":117,"1517421600":112,"1517422200":107,"1517422800":151,"1517423400":143,"1517424000":111,"1517424600":118,"1517425200":126,"1517425800":116,"1517426400":108,"1517427000":126,"1517427600":107,"1517428200":328,"1517428800":148,"1517429400":140,"1517430000":153,"1517430600":152,"1517431200":133,"1517431800":217,"1517432400":201,"1517433000":171,"1517433600":126,"1517434200":154,"1517434800":191,"1517435400":146,"1517436000":143,"1517436600":130,"1517437200":137,"1517437800":138,"1517438400":134,"1517439000":132,"1517439600":144,"1517440200":186,"1517440800":182,"1517441400":196,"1517442000":172,"1517442600":189,"1517443200":251,"1517443800":293,"1517444400":256,"1517445000":174,"1517445600":197,"1517446200":276,"1517446800":339,"1517447400":349,"1517448000":180,"1517448600":285,"1517449200":455,"1517449800":414,"1517450400":437,"1517451000":409,"1517451600":338,"1517452200":454,"1517452800":425,"1517453400":472,"1517454000":325,

Its dozens and dozens of pages of that, so much so that I reach the character limit when trying to post it all. That was the output of the URL you listed. Thanks for the help, hope this means something to you, ha.

Well, it seems to be returning stuff correctly. Open the dev tools (F12) and got to then network tab. Then refresh the tab and try loading some data from the database. Find the network request in the dev tools and see if it completes. Once it completes, it will take a few seconds before the page shows the data because it has to process it still.

This is the output, not sure how useful it will be without looking at it in real time. I've even had an ssh open a dozen or so times when testing, looking at cpu load and sysload, thinking maybe the wee little pi just can't keep up with a big query, and wondering if I can observe the CPU spike while it "thinks" through the database query. But no such CPU activity is observed. As soon as I make the request in the GUI, the CPU load goes flat, back to baseline.

I should add, to rule it out, that I've tried multiple browsers across several PCs and devices, just to rule out that plug-in etc might be preventing some script from running or something. Same issue, even on a machine with a fresh install of a browser I've never used before, and therefore has no add-on software associated with it.

If you're willing to move to the 4.0 branch (where the devs are actively working), on at least one occasion moving to that branch has cleared up a log issue. Plus, it has some new features and improved performance. Here are the commands if you want to go this route.

echo release/v4.0 | sudo tee /etc/pihole/ftlbranch 
pihole checkout core release/v4.0 
pihole checkout web release/v4.0

Done, thanks. FTL is still at 3.0, said no updates were found on Git, not sure that matters or not.

No effect though, still no historical data. Maybe time for a re-install? Still would like to know what happened though, to prevent it from happening in the future.

The devs would probably like to know as well, but to get you up and running properly I think a fresh install is the best option.