GUI showing no Pihole V5.3.1: Statistics and Error Msg “Undefined %” in “Precent Blocked"

Do a pihole -d and post the token here so that the devs can have a look if needed.

hi there, i had this errors too but only on a x86_64 machine, the pi4b 1g is fine.
i have a script which deletes the database after an update (rm /etc/pihole/pihole-FTL.db) because in the past i had errors with pihole migrating to newer db versions
but it looks like this is the problem
after db recreation i got many of these errors:

[2021-04-18 20:18:38.177 9821M] Resizing "FTL-strings" from 40960 to (81920 * 1) == 81920 (/dev/shm: 720.9KB used, 2.1GB total, FTL uses 708.9KB)
[2021-04-18 20:18:38.178 9821M] SQLite3 message: no such column: aliasclient_id in "SELECT aliasclient_id FROM network WHERE id = (SELECT network_id FROM network_addresses WHERE ip = ? AND aliasclient_id IS NOT NULL GROUP BY ip HAVING max(lastSeen));" (1)
[2021-04-18 20:18:38.178 9821M] getAliasclientIDfromIP("192.168.140.221") - SQL error prepare: SQL logic error
[2021-04-18 20:18:38.178 9821M] New upstream server: 127.0.0.1:5335 (0/512)
[2021-04-18 20:18:39.015 9821/T9825] SQLite3 message: no such column: name in "SELECT name FROM network_addresses WHERE name IS NOT NULL AND ip = ?;" (1)
[2021-04-18 20:18:39.015 9821/T9825] getNameFromIP("192.168.140.221") - SQL error prepare: SQL logic error
[2021-04-18 20:18:39.016 9821/T9825] Compiled 2 whitelist and 9 blacklist regex filters for 1 clients in 3.7 msec
[2021-04-18 20:18:39.808 9821M] SQLite3 message: no such column: name in "SELECT name FROM network_addresses WHERE name IS NOT NULL AND ip = ?;" (1)
[2021-04-18 20:18:39.809 9821M] getNameFromIP("127.0.0.1") - SQL error prepare: SQL logic error
[2021-04-18 20:18:39.810 9821M] SQLite3 message: no such column: aliasclient_id in "SELECT aliasclient_id FROM network WHERE id = (SELECT network_id FROM network_addresses WHERE ip = ? AND aliasclient_id IS NOT NULL GROUP BY ip HAVING max(lastSeen));" (1)
[2021-04-18 20:18:39.810 9821M] getAliasclientIDfromIP("127.0.0.1") - SQL error prepare: SQL logic error
[2021-04-18 20:18:39.811 9821M] New upstream server: 192.168.178.1:23553 (1/512)
[2021-04-18 20:18:42.029 9821M] SQLite3 message: no such column: name in "SELECT name FROM network_addresses WHERE name IS NOT NULL AND ip = ?;" (1)
[2021-04-18 20:18:42.029 9821M] getNameFromIP("192.168.11.22") - SQL error prepare: SQL logic error
[2021-04-18 20:18:42.030 9821M] SQLite3 message: no such column: aliasclient_id in "SELECT aliasclient_id FROM network WHERE id = (SELECT network_id FROM network_addresses WHERE ip = ? AND aliasclient_id IS NOT NULL GROUP BY ip HAVING max(lastSeen));" (1)
[2021-04-18 20:18:42.030 9821M] getAliasclientIDfromIP("192.168.11.22") - SQL error prepare: SQL logic error
[2021-04-18 20:18:42.816 9821/T9827] SQLite3 message: no such column: name in "SELECT name FROM network_addresses WHERE name IS NOT NULL AND ip = ?;" (1)
[2021-04-18 20:18:42.816 9821/T9827] getNameFromIP("192.168.11.22") - SQL error prepare: SQL logic error
[2021-04-18 20:18:46.559 9821M] SQLite3 message: no such column: aliasclient_id in "SELECT aliasclient_id FROM network WHERE id = (SELECT network_id FROM network_addresses WHERE ip = ? AND aliasclient_id IS NOT NULL GROUP BY ip HAVING max(lastSeen));" (1)
[2021-04-18 20:18:46.559 9821M] getAliasclientIDfromIP("192.168.50.13") - SQL error prepare: SQL logic error

but after doing
service pihole-FTL stop
service pihole-FTL start

everything runs fine for now

I've gone through and deleted some posts that had instructions that apparently people will copy/paste and run without knowing what they will do or how they will affect their installations.

Note to all reading this thread. DON'T COPY/PASTE COMMANDS YOU WERE NOT DIRECTLY ASKED TO RUN.

1 Like

There is a known bug where we also already have a bugfix for wit database migrations. However, migration only fails on the first start of FTL on a new database. Any subsequent restart (one suffices) is able to finish the database migration. You should not be seeing any more issues afterwards.

This also applies to @gennaris and probably more in here.

The bug fix is here:

@DL6ER thanks !
I saw the pull request this afternoon, recompiled FTL from source and DB went through all 9 update steps after first re-creation... So far so good

This hotfix will be released to the public soon?

Also, does this bug affect API calls too? Some of us are noticing that API calls also goes down at the same time as the GUI when it happens.

I also have the case that I always have "undefined" flashing under "Percent blocked".
I found out that it might be related to the fact that I installed watchtower in Docker (which is running on my Synology NAS) (following these instructions: https://mariushosting.com/synology-30-second-watchtower-install-using-task-scheduler-docker/). Please let me know if I need to set anything differently or additionally.

Also seen ERROR entries on my pihole-FTL.log file as well, regarding the database.
Looking at the required packages, php-sqlite is only needed when running NGNIX as the default webserver, so could that be causing an issue when using Lighttpd?

php-sqlite is also required when using lightttpd. This is the reason why it is installed when you choose to install the webserver (lighttpd) during installation:

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.