I need to be sure, so I will keep an eye on it, but I think there is something wrong now. With the same regex and the same lists I now get 2% whereas with Pi-hole 5.8.1||FTL 5.13||Web 5.10.1 I was getting ~24%. What could be the reason?
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Sure thing, here it is:
Your debug token is: https://tricorder.pi-hole.net/t67TkEO4/
And this is a pic of the old setup with the high percentage -> https://ibb.co/hKJPMjY
And this is a pic from half of te day of the new setup with the low perce -> https://ibb.co/GsKLWdM
Something is kinda off..
Your debug log suggest you have enabled DNSSEC:
*** [ DIAGNOSING ]: Setup variables
DNSSEC=true
Pi-hole-FTL v5.9 introduced extended logging of DNSSEC requests in September 2021 (jump to "Show automatically generated DNSSEC queries").
As a few of those happen for every domain lookup, it of course would have an impact on the blocking quote. Note that they did happen pre-5.9 as well, there were simply not logged before.
The release announcement did also refer to how to disable that via SHOW_DNSSEC, if you'd prefer not to see them.
not sure I follow. What kind of an impact in the blocking percentage?
Since it is enabled, the quota should take them into consideration as well, no?
So, basically, pi-hole does the job, but it does not look that good, right?
You defined a some clients and a lot of adlists which are not assigned to any group. If any of those clients queries a domain from one of those adlists it won't be blocked at all. Make sure you assign each client and adlist to a group (by default it's the "Default group")
In your log I see some more errors that should not happen:
[2022-03-20 00:05:00.035 1107/T1111] Keeping queries in memory for later new attempt
[2022-03-20 00:06:00.540 1107/T1111] SQLite3 message: cannot modify queries because it is a view in "INSERT INTO queries VALUES (NULL,?,?,?,?,?,?,?)" (1)
[2022-03-20 00:06:00.540 1107/T1111] ERROR: Storing queries in long-term database failed: SQL logic error
[2022-03-20 00:06:00.541 1107/T1111] Keeping queries in memory for later new attempt
[2022-03-20 00:07:00.034 1107/T1111] SQLite3 message: cannot modify queries because it is a view in "INSERT INTO queries VALUES (NULL,?,?,?,?,?,?,?)" (1)
[2022-03-20 00:07:00.035 1107/T1111] ERROR: Storing queries in long-term database failed: SQL logic error
[2022-03-20 00:07:00.035 1107/T1111] Keeping queries in memory for later new attempt
[2022-03-20 00:08:00.569 1107/T1111] SQLite3 message: cannot modify queries because it is a view in "INSERT INTO queries VALUES (NULL,?,?,?,?,?,?,?)" (1)
[2022-03-20 00:08:00.569 1107/T1111] ERROR: Storing queries in long-term database failed: SQL logic error
[2022-03-20 00:08:00.569 1107/T1111] Keeping queries in memory for later new attempt
[2022-03-20 00:09:00.075 1107/T1111] SQLite3 message: cannot modify queries because it is a view in "INSERT INTO queries VALUES (NULL,?,?,?,?,?,?,?)" (1)
[2022-03-20 00:09:00.075 1107/T1111] ERROR: Storing queries in long-term database failed: SQL logic error
This is unexpected because INSERT INTO queries VALUES (NULL,?,?,?,?,?,?,?) should not happen at all. The code was changed by Optimize queries table by DL6ER · Pull Request #1255 · pi-hole/FTL · GitHub and the former table queries was transformed to a view and replaced by the table query_storage.
Did you perform the update to FTL v5.14 after 2022-03-20 00:09:00?
Can I skip the client assignment to a group? Basically I wish that all clients are blocked.
As for the adlists, I have moved them to the default group, thanks for that. No idea if the update changed this behavior.
As for the update it did happen yesterday morning indeed, I cannot remember exactly the time tbh. Plus, I live in Central Europe (CET). I can rerun the upgrade if you wish.
Yes. If you don't define any client in particular all clients will be assigned to the "Default group" by default - same as every adlist and black/whitelist entry.
Awesome, I have now assigned all the adlists to the default and I have removed the clients from any group. It seems I am back to the previous behavior! Thank you for the help!
If there is anything with regards to the SQLite, I am happy to help debugging.
Keep an eye on /var/log/pihole-FTL.log if those messages still appear.
Will do; so far cannot see such messages.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.