Pi-hole diagnosis errors

Help docker
1

Hi everyone,

i've been running into these errors repeatedly, so I’ve put together a debug-log to help diagnose the issue.

grafik
grafik874×193 12.3 KB

2

Where is the token for your debug log?

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 if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

3

Thanks for the quick reply. :slight_smile:
https://tricorder.pi-hole.net/RaDyvP6T/

4

Which line are you questioning? The LIST error or the DNSMASQ_WARN warning? If the latter, then you will have to ignore it for now, it's just a warning from the underlying dnsmasq process and it is being worked on by that packages author.

5

The list error

6

What does the output from a pihole -g run show for that list processing?

7 
  [✓] DNS resolution is available

  [i] Neutrino emissions detected...

  [✓] Preparing new gravity database
  [✓] Creating new gravity databases
  [✓] Pulling blocklist source list into range
  [i] Using libz compression

  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: No changes detected
  [✓] Parsed 247166 exact domains and 0 ABP-style domains (allowing, ignored 1 non-domain entries)
      Sample of non-domain entries:
        - fe80::1%lo0

  [✓] Building tree
  [i] Number of gravity domains: 0 (0 unique domains)
  [i] Number of exact denied domains: 0
  [i] Number of regex denied filters: 1
  [i] Number of exact allowed domains: 1
  [i] Number of regex allowed filters: 0
  [✓] Optimizing database
  [✓] Swapping databases
  [✓] The old database remains available
  [✓] Cleaning up stray matter

  [✓] Done.
8

What could be the reason ?

9

This particular list was unavailable at the time the gravity update was run.