A Few issues with the beta on a fresh install

Vexira · February 15, 2020, 1:41pm

From mobile screen shot, chrome browser.

DL6ER · February 15, 2020, 2:08pm

Okay, it is still a bit confusing, so the -2 on the number of blocked domains is gone and replaced by the correct number, but the rest is still not working (guessing from your photo of your screen).

No, the number of blocking domains is mostly irrelevant and we're commonly seeing that Pi-hole works with such large numbers even on low-end hardware.

What is the output of

sudo getenforce
sudo aa-status

? This will check SELinux and AppArmor. If any error pops up, this may be okay as that might just show that this respective thing is not even installed.

Did you point any device at the Pi-hole? If not, please perform a few queries on the device locally, e.g. using

dig discourse.pi-hole.net @127.0.0.1

Vexira · February 15, 2020, 2:14pm

The photos is from the 4.0 installation before I updated to 5.0 after I updated to 5 I lost a few domains due to the gravity error.

I pointed my phone at it at one point, but not recently.

DL6ER · February 15, 2020, 3:37pm

Okay, so next question is: What is the output of
http://192.168.50.47/admin/api.php

edit Also, could you tell me what blocking lists you're using? I will try to reproduce this.

sqlite3 /etc/pihole/gravity.db "SELECT address FROM vw_adlist;"

should tell you

Vexira · February 15, 2020, 3:51pm

{"domains_being_blocked":-2,"dns_queries_today":0,"ads_blocked_today":0,"ads_percentage_today":0,"unique_domains":0,"queries_forwarded":0,"queries_cached":0,"clients_ever_seen":0,"unique_clients":0,"dns_queries_all_types":0,"reply_NODATA":0,"reply_NXDOMAIN":0,"reply_CNAME":0,"reply_IP":0,"privacy_level":0,"status":"disabled","gravity_last_updated":{"file_exists":true,"absolute":0,"relative":{"days":18307,"hours":15,"minutes":50}}}

DL6ER · February 15, 2020, 4:14pm

Thanks, please also see my edit. I think I need to try to reproduce this locally.

Do you still see the same when disabling all but one standard blocking list and running pihole -g thereafter?

DanSchaper · February 16, 2020, 12:54am

I don't have a Rock64, I had an old Pine that just never worked with the stock OS. This looks like Armbian and that should be fine.

Vexira · February 16, 2020, 4:29am

Results for dig and se linux

Vexira · February 16, 2020, 4:30am

DL6ER · February 16, 2020, 7:03am

First try reducing the lists to the first few:

https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt

to check if this restores the basic Pi-hole functionality. Then, we know where to go forward.

You do not need to delete the others, you can simply disable them.

Vexira · February 16, 2020, 7:16am

well that fixes the error with gravity

scottydaman · February 16, 2020, 7:32am

Some of those lists aren't in pihole format - probably choking somewhere.

Vexira · February 16, 2020, 7:41am

Odd pihole 4 has no issues with the lists seems that it's an issue in 5 with SQL having issues.

DL6ER · February 16, 2020, 7:45am

Yes, Pi-hole v4.0 accepted invalid domains to some degree (containing quotation marks, etc.). It'd be enormously helpful if you could find out which of these domains is causing the issue. We can then adjust the domains parser to work with them.

Let me be honest: Getting Pi-hole to work isn't highest priority with all the other beta things going on. However, if you can help us identify which list is the culprit, I promise to make the necessary adjustments to let gravity run through. I'll look at some of them but given the large number, it is unlikely that I'll find it by just cherry-picking random domains.

Vexira · February 16, 2020, 8:03am

I'll check my main concern is to fix the database locking error that is preventing me for using the GUI, gravity is secondary also thank you for the help I greatly appreciate it, I'm considering wiping it and seeing if it work or if all else fails just buy a pi 4.

DL6ER · February 16, 2020, 8:22am

So is this still present with the reduced set of lists? It could have been due to the gravity errors before. We've already checked all the permissions for the web user, the database folder and file and they all seemed file so there should be nothing left causing this.

Vexira · February 16, 2020, 8:32am

gravity parsing error is gone but the database is still locked, ill have to look at the lists to see which have issues being parsed.

i might have to nuke it again see if it works this time, only issue i can see is that all the domains are 0 on gravity.

DL6ER · February 16, 2020, 9:36am

What is the output of

ps aux | grep sqlite3

?

The only thing that could be causing this when all the permissions are fine may be a still running sqlite3 transaction, not sure how to resolve this.

You could also try a selective nuke option:

rm /etc/pihole/gravity.db
pihole -g -r

but please ensure first that /etc/pihole/migration_backup/adlists.list (path may actually be slightly different) does contain only the few domains you've seen Pi-hole working correctly with.

Vexira · February 16, 2020, 9:41am

vexira@WonderBoom2:~$ ps aux | grep sqlite3
vexira 4859 0.0 0.0 5820 664 pts/0 S+ 20:40 0:00 grep sqlite3

DL6ER · February 16, 2020, 9:49am

Okay, so no running gravity process. I really hope that the restored/newly created database will fix this issue for you.