Gravity Count is 0

I've noticed that PiHole is no longer blocking any domains. I've updated to latest version (5.15.5) and have ensured my DNS server in DHCP is set to my PiHole. I haven't made any changes that I can remember.

PiHole running on RPi3 with DietPi v8.5.1

Here's my debug URL: https://tricorder.pi-hole.net/zDf6BHHN/

When I manually update gravity, I see this line of interest: [i] Number of gravity domains: 0 (0 unique domains)

Any insight would be appreciated.

Do you think DietPi is a supported OS ?

Been running it for 3 years without an issue. :person_shrugging:

Ended up solving this by adding a domain to the Blocklist manually, which for some reason allowed gravity update to add all the adlist domains to the database. Result after running latest pihole -g:
[i] Number of gravity domains: 193783 (186438 unique domains)

Just wanted to update here in case anyone runs into a similar issue. I'm back to blocking ads!

Yeah, it actually is.

1 Like

Likely unrelated coincidence. Your logs show:

   [2023-03-10 09:31:49.015 27365/T27390] ADLIST WARNING: Adlist with ID 2 (https://mirror1.malwaredomains.com/files/justdomains) was inaccessible during last gravity run
   [2023-03-10 09:31:49.036 27365/T27390] Blocking status is enabled
   [2023-03-10 09:31:59.326 27365M] Reloading DNS cache
   [2023-03-10 09:31:59.350 27365/T27390] SQLite3 message: file renamed while open: /etc/pihole/gravity.db (28)
   [2023-03-10 09:31:59.354 27365/T27390] Compiled 0 whitelist and 0 blacklist regex filters for 13 clients in 0.6 msec
   [2023-03-10 09:31:59.354 27365/T27390] ADLIST WARNING: Adlist with ID 2 (https://mirror1.malwaredomains.com/files/justdomains) was inaccessible during last gravity run
   [2023-03-10 09:31:59.383 27365/T27390] Blocking status is enabled
   [2023-03-10 09:36:35.306 27365M] Reloading DNS cache
   [2023-03-10 09:36:35.366 27365/T27390] SQLite3 message: file renamed while open: /etc/pihole/gravity.db (28)
   [2023-03-10 09:36:35.369 27365/T27390] Compiled 0 whitelist and 0 blacklist regex filters for 14 clients in 0.6 msec
   [2023-03-10 09:36:35.370 27365/T27390] ADLIST WARNING: Adlist with ID 2 (https://mirror1.malwaredomains.com/files/justdomains) was inaccessible during last gravity run
   [2023-03-10 09:36:35.401 27365/T27390] Blocking status is enabled

This should be visible as a warning on your web admin interface:

*** [ DIAGNOSING ]: Pi-hole diagnosis messages
   count   last timestamp       type                  message                                                       blob1                 blob2                 blob3                 blob4                 blob5               
   ------  -------------------  --------------------  ------------------------------------------------------------  --------------------  --------------------  --------------------  --------------------  --------------------
   1       2023-03-10 09:36:35  ADLIST                https://mirror1.malwaredomains.com/files/justdomains          2                                             

And the database integrity check shows:

*** [ DIAGNOSING ]: Pi-hole FTL Query Database
-rw-rw-r-- 1 pihole pihole 2.7G Mar 10 09:41 /etc/pihole/pihole-FTL.db
[i] Checking integrity of /etc/pihole/pihole-FTL.db ... (this can take several minutes)
[✗] Integrity errors in /etc/pihole/pihole-FTL.db found.

    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info
    TEXT value in query_storage.additional_info

The network connectivity check shows that IPv4 is not working locally, and IPv6 is not working at all.


*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  on lo (127.0.0.1)
[✗] Failed to resolve  on eth0 (192.168.19.25)
[✓] doubleclick.com is 172.217.2.46 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  on lo (::1)
[✗] Failed to resolve  on eth0 (fe80::ba27:ebff:fe36:5cf5)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

The DHCP server is handing out DNS servers that are not Pi-hole, you will get clients using the non-Pi-hole server and will bypass any blocking.

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 300 bytes from eth0:192.168.19.2
     Offered IP address: 192.168.19.49
     Server IP address: 192.168.19.2
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.19.2
      lease-time: 86200 ( 23h 56m 40s )
      renewal-time: 43100 ( 11h 58m 20s )
      rebinding-time: 75425 ( 20h 57m 5s )
      netmask: 255.255.255.0
      broadcast: 192.168.19.255
>     dns-server: 192.168.19.25 <
>     dns-server: 192.168.19.2 <
      router: 192.168.19.2
      --- end of options ---

Thank you for the detailed response.

I did end up finding a tricksy little setting in my ASUS router DHCP options that I did not previously see called "Advertise router's IP in addition to user-specified DNS", which is now disabled.

Strange about you not seeing that ipv4 was working locally, as I was able to update PiHole and DietPi both from my RPi over the Internet.

I did notice that one of the 2 adlists installed was not responding. I removed the one that wasn't reachable (as you saw in the logs), but gravity update would still not place the default adlist domains into the db. As you said, whatever I did was likely just a coincidence.

Appreciate you taking the time to walk me through the debug logs, and the work you guys do. Cheers.

If you want to run another debug log and post the token URL now that things are working then we can compare the results and see if the networking issues are resolved.

I think it's good now, appreciate the offer though. Take care.

1 Like