V6 - query log empty | FTL database error

Hello everyone

After updating to version V6.0.4, there are no entries in the query log.

Expected Behaviour:

As before with the V5 version, the entries are available to be able to understand what is blocked, for example.

Actual Behaviour:

The display is blank. This is from the beginning of the installation.
I have already deleted all browser data - no change.
A different browser does not display anything either.
This is shown in the FTL.log:

2025-02-24 19:14:11.766 INFO Database version is 6
2025-02-24 19:14:11.766 INFO Updating long-term database to version 7
2025-02-24 19:14:11.766 ERROR SQLite3: duplicate column name: additional_info in "ALTER TABLE queries ADD COLUMN additional_info TEXT;" (1)
2025-02-24 19:14:11.766 ERROR ERROR: SQL query "ALTER TABLE queries ADD COLUMN additional_info TEXT;" failed: SQL logic error (SQLITE_ERROR)
2025-02-24 19:14:11.766 ERROR add_additional_info_column() failed!
2025-02-24 19:14:11.766 ERROR Column additional_info not initialized, database not available
2025-02-24 19:14:11.771 ERROR init_memory_database(): Failed to attach disk database
2025-02-24 19:14:11.994 INFO FTL is running as user pihole (UID 999)
2025-02-24 19:14:11.994 INFO Reading certificate from /etc/pihole/tls.pem ...
2025-02-24 19:14:11.996 INFO Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-02-24 19:14:11.997 INFO Web server ports:
2025-02-24 19:14:11.997 INFO - 80 (HTTP, IPv4, optional)
2025-02-24 19:14:11.997 INFO - 443 (HTTPS, IPv4, optional)
2025-02-24 19:14:11.997 INFO - 80 (HTTP, IPv6, optional)
2025-02-24 19:14:11.997 INFO - 443 (HTTPS, IPv6, optional)
2025-02-24 19:14:11.997 INFO Blocking status is enabled
2025-02-24 19:14:11.998 WARNING Connection error (2620:119:35::35#53): failed to send UDP request (Network unreachable)

Debug Token:

My debug token is: https://tricorder.pi-hole.net/3HkM4nXE/

Many thanks for your help and best regards!

Looks like your DB had an issue updating to the new schema. The easiest way to fix this would be to rename the db file located in /etc/pihole and have pihole re-create the db. You would lose your long-term query data, however.

Thank you very much for your answer, @Ladrien :+1:

I will try this out tonight.

Can I simply do this via the GUI and enter a different name for the DB name and save it or what is the correct procedure for renaming the DB?

1 Like

Stop Pi-Hole :

systemctl stop pihole-FTL

Then delete Query Log Database :

rm /etc/pihole/pihole-FTL.db

And then start Pi-Hole again :

systemctl start pihole-FTL

Should do the trick :slight_smile:

1 Like

Perfect, @nero355 :clap:

I created the new FTL database with the help of your instructions.

I found out that the FTL database file needs to be renamed with

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

and then the device needs to be restarted for Pi-hole to generate a new one. This is also possible. Then just with the old DB, which is still available.

2 Likes

Perfect. Thanks for the info, this was driving me nuts!

Hello together,
I have the following problem with pihole v6 (latest update).
When I switch the query log to show me β€žallβ€œ, the website hangs and after I reload I see no entries in the query log.
After deleting the pihole-ftl.db everthings works until I select β€žallβ€œ again.
So I can only viel β€ž10β€œ, β€ž25β€œ, β€ž50β€œ of β€ž100β€œ queres. The option β€žallβ€œ didnβ€˜t work.
Is this a know bug in pihole V6?

Best regards
Bart

I have not noticed this misbehavior in my case. It works for me :+1:
I have installed Core v6.0.5FTL, v6.0.4Web and interface v6.0.2.
Do you have everything up to date, @Bart_Simpson :question:

Yes everything ist update.

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