Domains on blocklist gives -2 on qnap docker

antonlamers · March 31, 2020, 1:28pm

Hi,
i installed now pi hole on a qnap docker.
I see by the dashboard domains on blocklist no value.
By my old pi-hole on a raspberry i see there a value.
when i look to the settings i see by by blocklists urls witch are add.

what is wrong?
did i choose a wrong version to install in the docker?

anton

juergen · April 4, 2020, 8:54am

have the same problem. Any ideas?

jfb · April 4, 2020, 5:16pm

If you are seeing close to zero domains on gravity (can be either negative or positive and close to zero), it is likely that your gravity list is empty. A quick check is to dig for a known blocked domain and see the reply.

dig +short flurry.com

The answer should be 0.0.0.0

juergen · April 5, 2020, 7:59am

Hi,

tested it and get following result:

dig +short flurry.com

212.82.100.153

74.6.136.153

98.136.103.26

domains on blocklist is still -2

thx

antonlamers · April 5, 2020, 8:15am

And the pi hole doesn’t work also. I did also an update to the gravity list

jfb · April 5, 2020, 12:58pm

Please post a new debug token.

nico1 · April 23, 2020, 8:19pm

I'm facing the same error but I'm using RPI1 with armel-master image

Stegar · May 1, 2020, 12:29pm

Hi!
I've got the same issue. How do I post a debug token?

Edit: Got the token.
Here it is:
https://tricorder.pi-hole.net/x5ridrpr92

Hopefully it helps.

DanSchaper · May 1, 2020, 6:00pm

github.com/pi-hole/docker-pi-hole

Stopped blocking after upgrade [arm64/aarch64 raspbian]

opened 01:38PM - 28 Feb 20 UTC

Mellbourn

After upgrading to v4.4 my pi hole stopped blocking ads. This is a... … - [ ] Request for a new or modified feature - [x ] Issue trying to run the docker image - [ ] Issue trying to build / test / develop the docker image ## Description I have been using docker-pi-hole without issue for months. Recently I did an upgrade (using `docker-compose pull && docker-compose up -d`, which upgraded to v4.4 After this upgrade, the pi-hole seems to be up and running, the web interface is working, but after running for several days: * "Percent Blocked" shows as 0.0% * "Domains on Blocklist" shows as -2 * It does not seem to block ads anymore * In the Query log, only Status green is listed, nothing blocked. * In the `pihole-FTL.log` file, ** it states `ravityDB_open(): /etc/pihole/gravity.db does not exist` ** further down all rows says `Gravity database not available`! e.g. `domain_in_list(discord.co): Gravity database not available` I'm a bit surprised at the FTL Version, it says `vDev (development, vDev-7dea0f0)` ![Screenshot 2020-02-28 at 14 58 30](https://user-images.githubusercontent.com/1785727/75554606-f5ffb380-5a3a-11ea-8dbd-e6b6e185e957.png) This is starting to sound like I have gotten a 5.0 beta version of the FTL, where you are supposed to have a database rather than a list. But I have not done anything to get a beta, I have just done a normal `docker-compose pull`. Tested doing `pihole checkout ftl master` but that did not help. It didn't even change version number displayed in GUI, so I'm not sure it worked. Tested changing `docker-compose.yml` so that instead of getting `pihole/pihole:latest` it would get `pihole/pihole:release-v4.3.4`, and doing `docker-compose pull` but that didn't really help, it did downgrade the Pi-hole version, but not the FTL version. ## Expected Behavior Ads blocked. ## Actual Behavior No ads blocked. ## Possible Fix Somehow getting the correct FTL version, maybe? ## Steps to Reproduce and debugging done 1. `docker-compose pull` 2. `docker-compose up -d` ## Debug steps I have tried These things did not help: 1. I restarted the pi-hole. 2. I have restarted the docker host. 3. I have done a update gravity through the web gui, it reported no problems. 4. I have checked the contents of `/etc/pihole`, and it looks normal. The `list.*.domains` files are there and are normal size. 5. I have flushed the logs - [x] I have tried destroying my container instance, pulling the newest image version, and re-creating a new container - [ ] I have tried running the nearly stock `docker run` example in the readme (removing any customizations I added) - [ ] I have tried running without my volume data mounts to eliminate volumes as the cause - [x] I have searched this repository for existing issues and pull requests that look similar Debug log: https://tricorder.pi-hole.net/y9e5xygthd I can't think of any workaround, so pi-hole has completely stopped working for me. ## Context and extra information ## Your Environment * Docker Host Operating System and OS Version: Raspbian 4.19.97-v8+ * Docker Version: 19.03.6, build 369ce74 * Hardware architecture: aarch64

github.com/pi-hole/docker-pi-hole

Docker Image Errors - libsystemd.so.0: ELF load command alignment not page-aligned

opened 08:25PM - 10 Feb 19 UTC

PlasmaSoftUK

This is a... - [ ] Request for a new or modified feature - [x] Issue trying… to run the docker image - [ ] Issue trying to build / test / develop the docker image ## Description I have a QNAP TS431XeU with 8Gb RAM, the NAS is running the latest 4.3.6.0805 firmware and the Container Station is the latest 1.9.3950. I've been happily running PiHole in Docker for a good 6 months, this morning I decided I would update the docker image as PiHole's web interface was saying there was an update available. So I did a pull on "pihole/pihole:latest" which retrieved v4.2.1 (Pretty sure I was running 4.0.x before as it said there was an update to 4.1 available). Foolishly I deleted the working container so I could give the new one the same name of "PiHole", and asign the same static IP. Long story short I now cannot get any of the PiHole Docker images to install and run correctly, they install but when running the console spews errors: `pgrep: error while loading shared libraries: libsystemd.so.0: ELF load command alignment not page-aligned kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) Stopping pihole-FTL pgrep: error while loading shared libraries: libsystemd.so.0: ELF load command alignment not page-aligned kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) Stopping pihole-FTL pgrep: error while loading shared libraries: libsystemd.so.0: ELF load command alignment not page-aligned kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Starting pihole-FTL (no-daemon) Stopping pihole-FTL ` I've tried all the armhf versions 4.0.0, 4.1.1, 4.2.1 etc. which I believe are the correct ones for my processor architecture: Annapurna Alpine AL314 quad-core 32bit 1.7 GHz ARM® Cortex-A15 processor All give the same error, even the 4.0 versions that I had installed before. ## Expected Behavior ## Actual Behavior ## Possible Fix ## Steps to Reproduce and debugging done e.g. your docker run command, pages to visit, CLI commands you ran 1. 2. 3. 4. ## Debug steps I have tried - [X] I have tried destroying my container instance, pulling the newest image version, and re-creating a new container - [X] I have tried running the nearly stock `docker run` example in the readme (removing any customizations I added) - [X] I have tried running without my volume data mounts to eliminate volumes as the cause - [X] I have searched this repository for existing issues and pull requests that look similar I've deleted all containers and images, removed Container station and re-installed. Started completely from fresh and I get the same exact error. I read somewhere that the Annapurna ARM uses 64K bytes page size (which is extremely non-standard across the board) instead of the standard 4K byte size and that may be the reason for the error. But why did it work before? At this point I'd be happy to just go back to 4.0 which was working fine until I messed with it. ## Context and extra information ## Your Environment * Docker Host Operating System and OS Version: QNAP TS431XeU with 8Gb RAM, the NAS is running the latest 4.3.6.0805 firmware and the Container Station is the latest 1.9.3950. * Docker Version: 17.09.1-ce * Hardware architecture: Annapurna Alpine AL314 quad-core 32bit 1.7 GHz ARM® Cortex-A15 processor I'm at a loss of how to resolve this and have temporarily moved my PiHole instance to a RaspberryPi, I would dearly like to get it running back on the NAS if anyone has any idea how to resolve the above issue. Thanks in advance! Plasma