Error message when trying to load all time or 30 days long term data

[zadigre]

I'm running the latest 5.0 beta version.

Problem with Beta 5.0:
when trying to load 30 days long term data (or anything more than that), I have the "An unknown error occurred while loading the data."
I'm running on the RPI 4 with 4GB of ram... I have more than enough free ram (only 13% used now).
everything else is running fine. No corrupted data anywhere.
I believe I removed my database less than 30 days ago to start fresh.
maxdbdays is set to 30

Is this caused by a corrupted database?
I can surely fix this by deleting the database. Anything you want me to do before I proceed?

Debug Token:
https://tricorder.pi-hole.net/572dzzgo0t

[jfb]

The issue is with how PHP allocates memory. PHP is doing the work here inside lighttpd. From your debug log:

 2020-05-05 10:00:05: (mod_fastcgi.c.421) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /var/www/html/admin/api_db.php on line 112
   2020-05-05 10:00:28: (mod_fastcgi.c.421) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /var/www/html/admin/api_db.php on line 112
   2020-05-05 10:02:22: (mod_fastcgi.c.421) FastCGI-stderr: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /var/www/html/admin/api_db.php on line 112

This thread may have some information of interest:

Querying long term data failed due to limited allowed memory for PHP resulting in "An unknown error occurred with loading the data"

I don't think 30 seconds is a bad number at all for 1.4M queries! I'd have actually anticipated this to be much slower. Imagine what you are doing: You are requesting the data from PHP, a high-level language not really meant for data processing. Dividing your 30 seconds by the 1.4M queries means your Pi-hole is only using 21 µs (yes, micro not milli) per query. This is actually very very fast. But I still see your point and server-side pagination is definitely something we already have impleme…

You can delete (or in the example below, move and save the existing copy) a database, although it is likely yours is not corrupted.

sudo service pihole-FTL stop

sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db

sudo service pihole-FTL start

[zadigre]

yeah I saw this thread.
I didn't think it was related.

thank you for your input.

for me, if that doesn't work on the web interface, I'll modify my maxdbdays to a lower number until a better way is implemented on pi-hole (in pi-hole 6+ I guess).