Trying gravity again...
pi hole diagnosis lists them all as inaccessable again.|
Output of pihole -g -f:
[β] Deleting existing list cache
[i] Neutrino emissions detected...
[β] Pulling blocklist source list into range
[β] Preparing new gravity database
[β] Creating new gravity databases
[i] Using libz compression
[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[β] Status: Connection Refused
[β] List download failed: no cached list available
[i] Target: https://raw.githubusercontent.com/PolishFiltersTeam/KADhosts/master/KADhosts.txt
[β] Status: Connection Refused
[β] List download failed: no cached list available
[i] Target: https://adaway.org/hosts.txt
[β] Status: Connection Refused
[β] List download failed: no cached list available
[β] Building tree
[β] Swapping databases
[β] The old database remains available
[i] Number of gravity domains: 0 (0 unique domains)
[i] Number of exact blacklisted domains: 0
[i] Number of regex blacklist filters: 0
[i] Number of exact whitelisted domains: 0
[i] Number of regex whitelist filters: 0
[β] Flushing DNS cache
[β] Cleaning up stray matter
[β] FTL is listening on port 53
[β] UDP (IPv4)
[β] TCP (IPv4)
[β] UDP (IPv6)
[β] TCP (IPv6)
[β] Pi-hole blocking is enabled
The first will show the headers (if any) that are being passed and the second will show the exit code for the command, if it fails again then we can see if the reason is a common one.
Hmm, okay, if you don't mind doing some investigating work:
Can you run
sudo bash -x /opt/pihole/gravity.sh
And watch the output, if it's still failing then the reasons should be in the output. I'm guessing it will be after the database routines, which look like CREATE TRIGGER. Might be in the httpCode.
This is what a successful run looks like:
++ curl --connect-timeout 10 -s -L --compressed -z /etc/pihole/list.1.raw.githubusercontent.com.domains -w '%{http_code}' https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts -o /tmp/tmp.dK9SvwkgKF
+ httpCode=200
+ case $url in
+ case "${httpCode}" in
+ echo -e '\r [β] Status: Retrieval successful'
And see if there is any response at all from github? And if you do get the proper list shown can you please show the last few lines of the output, like:
# 'hosts' file format) are appended to the unified hosts file during the
# update process. For example, uncomment the following line to block
# 'example.com':
# 0.0.0.0 example.com
200
That final line, 200 in a good run, is what I am looking for.
It may be possible that writing the file to the /tmp directory is the issue and the output from the commands I have shown above will help us narrow down the possibilities.
[Fri Dec 08] root@sandalpi: ~$ pihole -v
Pi-hole version is v5.17.2 (Latest: v5.17.2)
web version is v5.21 (Latest: v5.21)
FTL version is v5.23 (Latest: v5.23)
[Fri Dec 08] root@sandalpi: ~$
Hope you can shed some light on it please ?
I have attached output of pihole -g -f