# No query log update anymore and no top clients (all and blocked)

**URL:** <https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929>\
**Category:** Beta 6.0\
**Created:** [January 27, 2024, 10:45pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929 "2024-01-27T22:45:30Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 27, 2024, 10:45pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/1 "2024-01-27T22:45:30Z")

</div>

Hi, I just updated to following versions:

- **Core** vDev (development-v6, cc8f9fe0)
- **FTL** vDev (development-v6, ce4407b5)
- **Web interface** vDev (development-v6, 1dcf90bd)

and have no query list updates anymore and also the top clients aren't shown anymore at dashboard.

Numbers are counted and looks like blocking and resolving works fine

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 27, 2024, 10:47pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/2 "2024-01-27T22:47:10Z")

</div>

Flush log didn't change anything  
in dashboard I see 2230 total and 1446 blocked but in query log are only 52

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [January 27, 2024, 11:10pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/3 "2024-01-27T23:10:57Z")

</div>

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:

```auto
pihole -d

```

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 27, 2024, 11:28pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/4 "2024-01-27T23:28:50Z")

</div>

[https://tricorder.pi-hole.net/KndwLFyG/](https://tricorder.pi-hole.net/KndwLFyG/)

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 27, 2024, 11:30pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/5 "2024-01-27T23:30:27Z")

</div>

btw. If I go back to a older version (I use proxmox and used a backup from 21st of January) all works fine:

- **Core** vDev (development-v6, e1c41fe4)
- **FTL** vDev (development-v6, 3341f0e4)
- **Web interface** vDev (development-v6, de5a4b0d)

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [January 28, 2024, 3:21am UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/7 "2024-01-28T03:21:39Z")

</div>

Is your database on the same host as the VM? Which filesystem are you using?

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 28, 2024, 11:02am UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/8 "2024-01-28T11:02:01Z")

</div>

It's a Debian 12 LXC container and PI-hole is all and the only whats running there, No access to other LXC's. Also standard ext4 filesystem and as I told it's running after backup older version I mentioned in prior task fine again.

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 28, 2024, 8:59pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/9 "2024-01-28T20:59:34Z")

</div>

Any idea what the reason can be?

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [January 28, 2024, 9:24pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/10 "2024-01-28T21:24:58Z")

</div>

Your debug log shows two issues - while the first one may or not be the cause for the second one:

1. Your log contains a warning that the database was not closed properly. Maybe the container was restarted abruptly or something else happened that didn't allow the `pihole-FTL` process to handle the database correctly.
2. As a consequence of no. 1 above (or completely independent, we don't know yet), your database got locked. This prevented `pihole-FTL` from reading your gravity database resulting in _many_ warnings in your `/var/log/pihole/FTL.log`. And - apparently - down the line also prevented it from accessing any query data at all.

Please try starting from a fresh database to eliminate a database corruption as cause using:

```auto
sudo service pihole-FTL stop
sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL_broken.db
sudo rm /etc/pihole/pihole-FTL.db*
sudo service pihole-FTL start

```

inside the container.

Also of interesting is the output of:

```auto
pihole-FTL sqlite3 /etc/pihole/pihole-FTL_broken.db "PRAGMA integrity_check;"

```

(this command may take some time to finish, there is no progress reporting)

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 28, 2024, 9:49pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/11 "2024-01-28T21:49:39Z")

</div>

No change at all after doing the recomended steps and:  
pihole-FTL sqlite3 /etc/pihole/pihole-FTL\_broken.db "PRAGMA integrity\_check;"  
ok

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 28, 2024, 10:38pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/12 "2024-01-28T22:38:13Z")

</div>

Back to prior version and all fine again. If I can help further investigation, let me know

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [January 29, 2024, 3:09pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/13 "2024-01-29T15:09:43Z")

</div>

> [@jf62](#):
>
> If I can help further investigation, let me know

Thank for you the offer and sorry for the long delay in responses... First, we should investigate if this is due to the WAL journal or due to some other problem (which will be harder to trace).

Please run

```auto
sudo pihole checkout ftl new/useWAL
sudo pihole-FTL --config database.useWAL false

```

to get an experimental branch which allows controlling the WAL mode and, subsequently, turning it off.

FTL from this branch should be available in a few minutes. Until then, you'd get a harmless error during the `checkout` and nothing happens.

* * *

**edit** Wait, I just had another look into your debug log and see that you have non-empty setting for `webserver.api.excludeClients` and `webserver.api.excludeDomains`. We merged a feature last week that extended these options to also be effective for the Query Log:  
[https://github.com/pi-hole/FTL/pull/1611](https://github.com/pi-hole/FTL/pull/1611)

Could you please check if editing these (e.g. via the web interface's settings -\> all settings page) resolves the issue you are seeing? I see you are using a limited set but - maybe just maybe - if all your queries are either `localhost` or `fritz.box`, then this would easily explain what is happening here.

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 29, 2024, 6:25pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/14 "2024-01-29T18:25:29Z")

</div>

so, removing all entries in `webserver.api.excludeClients` and `webserver.api.excludeDomains` fixed the behavior,

But how can I use this feature in future? And also how will you handle this, if you will once do a upgrade for all users from V5 to V6 which are using this feature in V5?

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [January 29, 2024, 6:42pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/15 "2024-01-29T18:42:49Z")

</div>

There is no issue with using these settings at all. We still don't really know why the settings have been an issue for you. Is that that

> [@DL6ER](#):
>
> all your queries are either `localhost` or `fritz.box`

?

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 29, 2024, 6:44pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/16 "2024-01-29T18:44:20Z")

</div>

exclude clients:  
localhost  
fritz.box  
iobroker.fritz.box  
SKY-IPTV-WZ.fritz.box  
SKY-IPTV-GZ.fritz.box  
DiskStation.fritz.box  
pihole-6.fritz.box

exclude domains:  
www.example.com  
www.example.net  
www.example.org  
ipinfo.io  
cloudsync-tw.synology.com  
checkip.synology.com  
fritz.box  
www.gstatic.com  
connectivitycheck.gstatic.com  
wpad.fritz.box  
connectivity.sky.com

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [January 29, 2024, 6:50pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/17 "2024-01-29T18:50:39Z")

</div>

Yes, I have seen these in your debug log. My point is:

When you have `localhost` and `fritz.box` as clients to be excluded and all your queries either come from `localhost` or `fritz.box` (because you are using the DNS server of your FritzBox instead of distributing the Pi-hole as DNS server), then everything is behaving as expected.

The only bit that was not expected is that the functionality of these settings was extended to the Query Log.

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 29, 2024, 7:00pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/18 "2024-01-29T19:00:31Z")

</div>

ok, but what's the opions then? (Pi-hole as dns doesn't work for me )

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [January 29, 2024, 7:01pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/19 "2024-01-29T19:01:53Z")

</div>

> [@jf62](#):
>
> Pi-hole as dns doesn't work for me

Why?

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 29, 2024, 7:04pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/20 "2024-01-29T19:04:22Z")

</div>

forget it - I use Pi-hole as DNS (I mean as DHCP doesn't work)

---

<div class="post-metadata">

**Author:** ![jf62](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jf62/32/3811_2.png) [@jf62](https://discourse.pi-hole.net/u/jf62)\
**Post date:** [January 29, 2024, 7:07pm UTC](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929/21 "2024-01-29T19:07:42Z")

</div>

Where do you see, that I'm not using Pi-hole as DNS? fritz-box as DHCP sends only the IP of Pi-Hole to the clients (v4 and v6) and also use it by itself

[Next page](https://discourse.pi-hole.net/t/no-query-log-update-anymore-and-no-top-clients-all-and-blocked/67929.md?page=2)