This is a: Run Issue (running Pi-hole container failing)

Details

On my Ubuntu 20.04.4 LTS with Docker version 20.10.14 The container won't start up using the official latest image

Related Issues

[ x] I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

I did not find anything similar

How to reproduce the issue

Environment data

Operating System: Ubuntu 20.04.4 LTS
Hardware: PC
Kernel Architecture: x86/amd64
Docker Install Info and version:
- Software source: official docker-ce
- Supplimentary Software: portainer
Hardware architecture: amd64

docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
any additional info to help reproduce

These common fixes didn't work for my issue

[x ] I have tried removing/destroying my container, and re-creating a new container
[ x] I have tried fresh volume data by backing up and moving/removing the old volume data
[ x] I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
[ ] I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
[ ] I have tried running without my volume data mounts to eliminate volumes as the cause

If the above debugging / fixes revealed any new information note it here. Add any other debugging steps you've taken or theories on root cause that may help.

[i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [i] Installing /etc/dnsmasq.d/01-pihole.conf... [✓] Installed /etc/dnsmasq.d/01-pihole.conf [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf Existing DNS servers detected in setupVars.conf. Leaving them alone [✓] New password set DNSMasq binding to default interface: eth0 Added ENV to php: "TZ" => "Estonia/Tallinn", "PIHOLE_DOCKER_TAG" => "2022.04.2", "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "0.0.0.0", "CORS_HOSTS" => "", "VIRTUAL_HOST" => "0.0.0.0", Using IPv4 and IPv6 ::: setup_blocklists now setting default blocklists up: ::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot ::: Blocklists (/etc/pihole/adlists.list) now set to: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging...

[✓] Logging has been enabled! ::: Docker start setup complete Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf Pi-hole version is v5.9.1 (Latest: v5.9.1) AdminLTE version is v5.11 (Latest: v5.11) FTL version is v5.14 (Latest: v5.14) Container tag is: 2022.04.2 [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting pihole-FTL (no-daemon) as pihole Starting lighttpd Starting crond [services.d] done. [2022-04-19 01:33:04.183 522M] Using log file /var/log/pihole-FTL.log [2022-04-19 01:33:04.183 522M] ########## FTL started on 73c24eed5c14! ########## [2022-04-19 01:33:04.184 522M] FTL branch: master [2022-04-19 01:33:04.184 522M] FTL version: v5.14 [2022-04-19 01:33:04.184 522M] FTL commit: 52e6b95 [2022-04-19 01:33:04.184 522M] FTL date: 2022-02-12 19:58:34 +0000 [2022-04-19 01:33:04.184 522M] FTL user: pihole [2022-04-19 01:33:04.184 522M] Compiled for x86_64 (compiled on CI) using gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 [2022-04-19 01:33:04.185 522M] Creating mutex [2022-04-19 01:33:04.185 522M] Creating mutex [2022-04-19 01:33:04.186 522M] Starting config file parsing (/etc/pihole/pihole-FTL.conf) [2022-04-19 01:33:04.186 522M] SOCKET_LISTENING: only local [2022-04-19 01:33:04.187 522M] AAAA_QUERY_ANALYSIS: Show AAAA queries [2022-04-19 01:33:04.187 522M] MAXDBDAYS: max age for stored queries is 365 days [2022-04-19 01:33:04.187 522M] RESOLVE_IPV6: Resolve IPv6 addresses [2022-04-19 01:33:04.187 522M] RESOLVE_IPV4: Resolve IPv4 addresses [2022-04-19 01:33:04.187 522M] DBINTERVAL: saving to DB file every minute [2022-04-19 01:33:04.187 522M] DBFILE: Using /etc/pihole/pihole-FTL.db [2022-04-19 01:33:04.187 522M] MAXLOGAGE: Importing up to 24.0 hours of log data [2022-04-19 01:33:04.188 522M] PRIVACYLEVEL: Set to 0 [2022-04-19 01:33:04.188 522M] IGNORE_LOCALHOST: Show queries from localhost [2022-04-19 01:33:04.188 522M] BLOCKINGMODE: Null IPs for blocked domains [2022-04-19 01:33:04.188 522M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries [2022-04-19 01:33:04.188 522M] DBIMPORT: Importing history from database [2022-04-19 01:33:04.188 522M] PIDFILE: Using /run/pihole-FTL.pid [2022-04-19 01:33:04.188 522M] PORTFILE: Using /run/pihole-FTL.port [2022-04-19 01:33:04.189 522M] SOCKETFILE: Using /run/pihole/FTL.sock [2022-04-19 01:33:04.189 522M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf [2022-04-19 01:33:04.189 522M] MACVENDORDB: Using /etc/pihole/macvendor.db [2022-04-19 01:33:04.189 522M] GRAVITYDB: Using /etc/pihole/gravity.db [2022-04-19 01:33:04.189 522M] PARSE_ARP_CACHE: Active [2022-04-19 01:33:04.189 522M] CNAME_DEEP_INSPECT: Active [2022-04-19 01:33:04.189 522M] DELAY_STARTUP: No delay requested. [2022-04-19 01:33:04.190 522M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain} [2022-04-19 01:33:04.190 522M] NICE: Cannot change niceness to -10 (permission denied) [2022-04-19 01:33:04.190 522M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days [2022-04-19 01:33:04.190 522M] NAMES_FROM_NETDB: Enabled, trying to get names from network database [2022-04-19 01:33:04.190 522M] EDNS0_ECS: Overwrite client from ECS information [2022-04-19 01:33:04.190 522M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names [2022-04-19 01:33:04.190 522M] RATE_LIMIT: Rate-limiting client making more than 1000 queries in 60 seconds [2022-04-19 01:33:04.190 522M] LOCAL_IPV4: Automatic interface-dependent detection of address [2022-04-19 01:33:04.191 522M] LOCAL_IPV6: Automatic interface-dependent detection of address [2022-04-19 01:33:04.191 522M] BLOCK_IPV4: Automatic interface-dependent detection of address [2022-04-19 01:33:04.191 522M] BLOCK_IPV6: Automatic interface-dependent detection of address [2022-04-19 01:33:04.191 522M] REPLY_ADDR4: Using IPv4 address 0.0.0.0 instead of automatically determined IP address [2022-04-19 01:33:04.191 522M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries [2022-04-19 01:33:04.191 522M] MOZILLA_CANARY: Enabled [2022-04-19 01:33:04.191 522M] PIHOLE_PTR: internal PTR generation enabled (pi.hole) [2022-04-19 01:33:04.191 522M] ADDR2LINE: Enabled [2022-04-19 01:33:04.191 522M] REPLY_WHEN_BUSY: Permit queries when the database is busy [2022-04-19 01:33:04.192 522M] BLOCK_TTL: 2 seconds [2022-04-19 01:33:04.192 522M] BLOCK_ICLOUD_PR: Enabled [2022-04-19 01:33:04.192 522M] CHECK_LOAD: Enabled [2022-04-19 01:3Stopping pihole-FTL Stopping cron Stopping lighttpd s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening [cont-finish.d] executing container finish scripts... s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

I went to s6 folks and they pointed out that I have s6 overlay v3 and the container possibly uses v2. What can I do to get it up and running?

Apr 19 '22 01:04 Falenone

Same thing on latest ubuntu server with brand new installation

Apr 20 '22 01:04 Falenone

The version of s6 shouldn't matter. We use v2 inside the container and that's what will drive the container daemons. The host version doesn't come in to play.

We need to see the docker run or the docker-compose file you are using to start things up.

Apr 20 '22 02:04 dschaper

Same issue here running on Raspbian 10 after updating to the latest docker image (2022.04.3). Downgrading back to version 2022.02.1 seems to solve the issue.

How I fixed it:

Edit docker-compose.yml and change the line image: pihole/pihole:latest to image: pihole/pihole:2022.02.1
Run docker-compose pull to download the old version (if you don't have it yet)
Run docker-compose stop pihole to stop pihole
Run docker-compose rm pihole to remove the previous image
Run docker-compose up -d to start the pihole daemon again

Apr 24 '22 09:04 Bauxitedev

Same issue here running on Raspbian 10

Are you sure it is the same issue? Please see the upgrade notes on the Readme for information about buster based operating systems

Apr 24 '22 14:04 PromoFaux

@PromoFaux I'm pretty sure this is the same issue, since the error message I get is exactly the same as OP's:

s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening

Apr 24 '22 15:04 Bauxitedev

What is the s6 version installed on your host system? What is the return of:

apt list s6*

As pointed above, the s6 version installed on your system shouldn't matter, but sometimes we find weird cases...

Apr 24 '22 16:04 rdwebdesign

Can we also get your docker-compose or run scripts please, so that we know exactly how you're starting it.

Just going by the error message, have you got the env variable WEBLOGS_STDOUT set to 1?

Edit: That said, I have just tried on :latest with that env var set and am not seeing the issue on windows... will try on my rpi

Double edit: Same thing on Rpi (Raspbian Buster) - works with no issue...

Apr 25 '22 16:04 PromoFaux

Ah hold on. Both @Falenone and @Bauxitedev - I think this is another side-effect of the outdated libseccomp issue

@Bauxitedev, as you're on Raspbian Buster - take a look at this comment here to see if that fixes things https://github.com/pi-hole/docker-pi-hole/issues/1042#issuecomment-1086728157

@Falenone : I'm not sure if there is a similar solution for Ubuntu 20.04, but the original issue on the moby repo is probably worth a read in your case

Edit: TL;DR you need to be running libseccomp2 version >=2.5 in order for latest to work properly. This is available through backports on Debian buster, and updates on Ubuntu. Personally I would recommend you upgrade the whole OS if you can - updating libseccomp2 via backports/updates should be OK - but there is no telling whether or not it will break something else on your system

https://pkgs.org/download/libseccomp2

Apr 25 '22 16:04 PromoFaux

I am also getting this error every time I am restarting or stopping container after I updated pihole to the latest version. I am on Bullseye.

2022-04-27T16:59:33Z INF Autoupdate frequency is set autoupdateFreq=86400000 Stopping cron Stopping pihole-FTL Stopping Stubby Stopping Cloudflared [cont-finish.d] executing container finish scripts... Stopping lighttpd [cont-finish.d] done. [s6-finish] waiting for services. s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 05-changer-uid-gid.sh: executing... [cont-init.d] 05-changer-uid-gid.sh: exited 0. [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [i] Installing /etc/dnsmasq.d/01-pihole.conf... [✓] Installed /etc/dnsmasq.d/01-pihole.conf [i] Installing /etc/.pihole/advanced/06-rfc6761.conf... [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf Setting DNS servers based on PIHOLE_DNS_ variable

Apr 27 '22 17:04 iAmSaugata

What is your docker run or your docker-compose.yml file please?

Apr 27 '22 17:04 dschaper

Please find my docket-compose.yml file bellow. (I am using DHCP helper).

version: "3"
services:
  pihole:
    build: ./pihole-doh-dot
    container_name: pihole-doh-dot-dhcp
    hostname: pihole-svr
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "8008:80/tcp"
    restart: unless-stopped
    cap_add:
        - NET_ADMIN
        - SYS_NICE
    environment:
      TZ: 'Asia/Kolkata'
      WEBPASSWORD: "PASSWORD"
      ServerIP: "192.168.0.114"
      VIRTUAL_HOST:  "pihole.dns"
      PIHOLE_DNS_: "127.0.0.1#5053;127.0.0.1#5153"
      IPv6: "false"
      DNSMASQ_LISTENING: "all"
      PIHOLE_DOMAIN: "local"
      DNSMASQ_USER: "root"
    volumes:
      - '/home/pi/pihole-doh-dot-install/pihole/:/etc/pihole/'
      - '/home/pi/pihole-doh-dot-install/dnsmasq.d/:/etc/dnsmasq.d/'
      - '/home/pi/pihole-doh-dot-install/config/:/config/'
    depends_on:
      - dhcphelper
    networks:
      backend:
        ipv4_address: '172.33.0.100'
  dhcphelper:
    build: ./dhcp-helper
    container_name: pihole-dhcp-helper
    hostname: dhcp-helper-svr
    restart: unless-stopped
    network_mode: "host"
    command: -s 172.33.0.100
    cap_add:
      - NET_ADMIN
networks:
  backend:
    ipam:
      config:
        - subnet: 172.33.0.0/16

Apr 28 '22 04:04 iAmSaugata

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.

May 28 '22 20:05 github-actions[bot]

This issue still there.

Jun 01 '22 16:06 iAmSaugata

What is the output of apt list -a libseccomp2?

And docker version?

Jun 01 '22 16:06 rdwebdesign

Host:

Listing... Done libseccomp2/stable,now 2.5.1-1+deb11u1 arm64 [installed]

libseccomp2/stable 2.5.1-1+deb11u1 armhf

Pihole:

Listing... Done libseccomp2/stable,now 2.5.1-1+deb11u1 arm64 [installed,automatic]

Docker

Client: Docker Engine - Community Version: 20.10.16 API version: 1.41 Go version: go1.17.10 Git commit: aa7e414 Built: Thu May 12 09:15:56 2022 OS/Arch: linux/arm64 Context: default Experimental: true

Server: Docker Engine - Community Engine: Version: 20.10.16 API version: 1.41 (minimum version 1.12) Go version: go1.17.10 Git commit: f756502 Built: Thu May 12 09:14:19 2022 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.4 GitCommit: 212e8b6fa2f44b9c21b2798135fc6fb7c53efc16 runc: Version: 1.1.1 GitCommit: v1.1.1-0-g52de29d docker-init: Version: 0.19.0 GitCommit: de40ad0

Jun 01 '22 17:06 iAmSaugata

What is the dockerfile for the image you are building?

Jun 01 '22 19:06 dschaper

I re-read this whole issue.

You said you are receiving this error message:

s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening

Do you have other problems besides this message? Is your container running pi-hole correctly?

Jun 01 '22 20:06 rdwebdesign

Yes, I am only getting this message while rebooting the container, and this started from the latest version of pihole, other than getting this message, pihole itself running fine.

today at 5:25:31 PMStopping cron today at 5:25:31 PMStopping lighttpd today at 5:25:31 PMStopping pihole-FTL today at 5:25:31 PM[cont-finish.d] executing container finish scripts... today at 5:25:31 PMs6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening today at 5:25:31 PM[cont-finish.d] done. today at 5:25:31 PM[s6-finish] waiting for services. today at 5:25:31 PMs6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening today at 5:25:31 PM[s6-finish] sending all processes the TERM signal. today at 5:25:34 PM[s6-finish] sending all processes the KILL signal and exiting. today at 5:25:34 PMContainer stopped today at 5:25:36 PMContainer started today at 5:25:34 PM[s6-finish] sending all processes the KILL signal and exiting. today at 5:25:36 PM[s6-init] making user provided files available at /var/run/s6/etc...exited 0. today at 5:25:36 PM[s6-init] ensuring user provided files have correct perms...exited 0.

Jun 02 '22 11:06 iAmSaugata

So you don't have an issue.

Note: We are aware of this message. This message only appears when the container is stopped and some processes are killed before these 2 services. The services are probably already finished, but the script sends an error message. This message is harmless.

Jun 02 '22 16:06 rdwebdesign

Yes, I don't have any issue other than those messages in the longs.

Jun 05 '22 12:06 iAmSaugata

Same problems here. Seeing the same errors.

Turns out that an underlying OS update had re-enabled systemd-resolve.

A quick

systemctl disable systemd-resolved.service
systemctl stop systemd-resolved

and were back to normal

Jun 27 '22 08:06 ausfestivus

I have the same issue, container start fails with the same error message. I am using OpenSuse 15.4 (latest packages installed) and have the latest libseccomp2 version installed. Using latest pihole docker image. Systemd-resoved is disabled. Any ideas?

Jul 05 '22 10:07 JohnyJack01

I found (by accident) that my Pi-hole installations running in docker container on OpenSUSE 15.3 also shows this message - but not my other installations running in docker container on Ubuntu LTS 22.04… 🤔

Docker Tag 2022.05 Pi-hole v5.10 FTL v5.15 Web Interface v5.12

2022-06-26T07:20:07.153833780Z [cont-finish.d] executing container finish scripts...
2022-06-26T07:20:07.153530700Z s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening
2022-06-26T07:20:07.154413156Z s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening
2022-06-26T07:20:07.154437636Z [cont-finish.d] done.
2022-06-26T07:20:07.154481434Z [s6-finish] waiting for services.
2022-06-26T07:20:07.384785922Z [s6-finish] sending all processes the TERM signal.

But Pi-hole is up and running 👍🏻

But is this hourly stopping+starting related to this?

…
2022-07-07T06:03:04.088400999Z Stopping pihole-FTL
2022-07-07T06:03:04.501757604Z Starting pihole-FTL (no-daemon) as pihole
2022-07-07T07:03:04.648493997Z Stopping pihole-FTL
2022-07-07T07:03:05.059152086Z Starting pihole-FTL (no-daemon) as pihole```

Jul 07 '22 07:07 thomasmerz

I have no idea if this will make a difference to folk here, but we've upgraded the version of S6 inside the container to v3, which is currently in the dev branch.

Please can you try the :dev tag and let us know how you get on?

Jul 15 '22 17:07 PromoFaux

This is much worse now: docker container is crash-looping-forever 😢


$ docker logs -tf pihole
2022-07-18T09:10:49.760131874Z s6-rc: info: service cron: starting
2022-07-18T09:10:49.760604849Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:10:49.762721559Z s6-rc: info: service cron successfully started
2022-07-18T09:10:49.764263076Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:10:49.766818904Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:10:49.766829968Z s6-rc: info: service 1-startup: starting
2022-07-18T09:10:49.771727652Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:10:49.773193924Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:10:49.773211195Z Starting crond
2022-07-18T09:10:49.773323939Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:10:49.773668939Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:10:49.776341620Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:10:49.778155631Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:10:49.778711281Z s6-rc: info: service legacy-cont-init successfully started
2022-07-18T09:10:49.786727410Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:10:49.794080954Z
2022-07-18T09:10:49.794096634Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:10:49.800519722Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:10:49.856390391Z
  [✓] Installing latest logrotate script
2022-07-18T09:10:50.075955807Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:10:50.077167725Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:10:50.081211377Z FTL binding to default interface: eth0
2022-07-18T09:10:50.085782902Z ::: Enabling Query Logging
2022-07-18T09:10:50.121473992Z ::: Assigning password defined by Environment Variable
2022-07-18T09:10:50.146079966Z   [✓] New password set
2022-07-18T09:10:50.146520477Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:10:50.164383285Z Added ENV to php:
2022-07-18T09:10:50.165019498Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:10:50.165033859Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:10:50.165038484Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:10:50.165057946Z 			"CORS_HOSTS" => "",
2022-07-18T09:10:50.165062896Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:10:50.165770569Z Using IPv4 and IPv6
2022-07-18T09:10:50.186667581Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:10:50.187329305Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:10:50.232674003Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:10:50.232692357Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:10:50.234489224Z ::: Docker start setup complete
2022-07-18T09:10:50.256531125Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:10:50.286687934Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:10:50.293702083Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:10:50.293712348Z   Container tag is: dev
2022-07-18T09:10:50.293666883Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:10:50.293722258Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:10:50.319829266Z s6-rc: info: service pihole-FTL successfully started
2022-07-18T09:10:50.319848356Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:10:50.320119904Z s6-rc: info: service lighttpd: starting
2022-07-18T09:10:50.322330117Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:10:50.324736285Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:10:50.337929962Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:10:50.344205435Z Starting lighttpd
2022-07-18T09:10:54.519138670Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:10:54.535538915Z
  [✓] Preparing new gravity database
2022-07-18T09:10:54.575070356Z   [i] Using libz compression
2022-07-18T09:10:54.575090426Z
2022-07-18T09:10:54.575125609Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
2022-07-18T09:10:54.764329646Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2022-07-18T09:10:54.764373168Z s6-rc: fatal: timed out
2022-07-18T09:10:54.768055494Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
2022-07-18T09:10:54.768097896Z prog: fatal: stopping the container.
2022-07-18T09:10:54.775282169Z s6-rc: info: service legacy-cont-init: stopping
2022-07-18T09:10:54.776481191Z s6-rc: info: service lighttpd: stopping
2022-07-18T09:10:54.777556842Z s6-rc: info: service cron: stopping
2022-07-18T09:10:54.785628796Z   [i] Status: Pending...Stopping lighttpd
2022-07-18T09:10:54.795304894Z Stopping cron
2022-07-18T09:10:54.800022295Z s6-rc: info: service cron successfully stopped
2022-07-18T09:10:54.801014733Z s6-rc: info: service legacy-cont-init successfully stopped
2022-07-18T09:10:54.801195017Z s6-rc: info: service fix-attrs: stopping
2022-07-18T09:10:54.802764786Z s6-rc: info: service fix-attrs successfully stopped
2022-07-18T09:10:54.809806323Z s6-rc: info: service lighttpd successfully stopped
2022-07-18T09:10:54.810178243Z s6-rc: info: service pihole-FTL: stopping
2022-07-18T09:10:54.813092225Z Stopping pihole-FTL
2022-07-18T09:10:54.816466186Z s6-rc: info: service pihole-FTL successfully stopped
2022-07-18T09:10:54.816786959Z s6-rc: info: service 1-startup: stopping
2022-07-18T09:10:54.817651336Z s6-rc: info: service 1-startup successfully stopped
2022-07-18T09:10:54.817899629Z s6-rc: info: service s6rc-oneshot-runner: stopping
2022-07-18T09:10:54.820773286Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2022-07-18T09:11:00.723721649Z s6-rc: info: service cron: starting
2022-07-18T09:11:00.723884715Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:11:00.725870441Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:11:00.728368799Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:11:00.731795075Z s6-rc: info: service 1-startup: starting
2022-07-18T09:11:00.732841501Z s6-rc: info: service cron successfully started
2022-07-18T09:11:00.736389535Z Starting crond
2022-07-18T09:11:00.738243677Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:11:00.746599537Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:11:00.746646860Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:11:00.749134643Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:11:00.749153837Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:11:00.762365971Z
2022-07-18T09:11:00.762390717Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:11:00.762407518Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:11:00.762412070Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:11:00.765191079Z s6-rc: info: service legacy-cont-init successfully started
2022-07-18T09:11:00.809473303Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:11:00.833913900Z
2022-07-18T09:11:00.836982531Z   [i] Installing latest logrotate script...
2022-07-18T09:11:00.837000336Z 	[i] Existing logrotate file found. No changes made.
2022-07-18T09:11:00.868125709Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:11:00.870158219Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:11:00.877872906Z FTL binding to default interface: eth0
2022-07-18T09:11:00.882910411Z ::: Enabling Query Logging
2022-07-18T09:11:00.921158062Z ::: Assigning password defined by Environment Variable
2022-07-18T09:11:00.951381757Z   [✓] New password set
2022-07-18T09:11:00.951402492Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:11:00.968200285Z Added ENV to php:
2022-07-18T09:11:00.969328706Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:11:00.969340607Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:11:00.969345537Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:11:00.969349640Z 			"CORS_HOSTS" => "",
2022-07-18T09:11:00.969353367Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:11:00.969872690Z Using IPv4 and IPv6
2022-07-18T09:11:00.988901083Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:11:00.989298463Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:11:01.008343459Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:11:01.008642597Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:11:01.008956663Z ::: Docker start setup complete
2022-07-18T09:11:01.020494263Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:11:01.026296845Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:11:01.030683151Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:11:01.030877620Z   Container tag is: dev
2022-07-18T09:11:01.031361733Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:11:01.031533955Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:11:01.033049917Z s6-rc: info: service pihole-FTL successfully started
2022-07-18T09:11:01.033248432Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:11:01.033417955Z s6-rc: info: service lighttpd: starting
2022-07-18T09:11:01.034681139Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:11:01.034870912Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:11:01.036613012Z Starting lighttpd
2022-07-18T09:11:01.044782390Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:11:05.116833796Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:11:05.148590853Z
  [✓] Preparing new gravity database
2022-07-18T09:11:05.188874569Z   [i] Using libz compression
2022-07-18T09:11:05.189008818Z
2022-07-18T09:11:05.189457602Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
2022-07-18T09:11:05.728102952Z s6-rc: fatal: timed out
2022-07-18T09:11:05.728123159Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2022-07-18T09:11:05.730107361Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
2022-07-18T09:11:05.730147757Z prog: fatal: stopping the container.
2022-07-18T09:11:05.735556617Z s6-rc: info: service legacy-cont-init: stopping
2022-07-18T09:11:05.737670726Z s6-rc: info: service lighttpd: stopping
2022-07-18T09:11:05.738140953Z s6-rc: info: service cron: stopping
2022-07-18T09:11:05.743773287Z Stopping lighttpd
2022-07-18T09:11:05.746670967Z Stopping cron
2022-07-18T09:11:05.748668257Z s6-rc: info: service legacy-cont-init successfully stopped
2022-07-18T09:11:05.748793268Z s6-rc: info: service fix-attrs: stopping
2022-07-18T09:11:05.749734762Z s6-rc: info: service fix-attrs successfully stopped
2022-07-18T09:11:05.751538488Z s6-rc: info: service cron successfully stopped
2022-07-18T09:11:05.755189532Z s6-rc: info: service lighttpd successfully stopped
2022-07-18T09:11:05.755384266Z s6-rc: info: service pihole-FTL: stopping
2022-07-18T09:11:05.758105064Z Stopping pihole-FTL
2022-07-18T09:11:05.760206659Z s6-rc: info: service pihole-FTL successfully stopped
2022-07-18T09:11:05.760428931Z s6-rc: info: service 1-startup: stopping
2022-07-18T09:11:05.761503922Z s6-rc: info: service 1-startup successfully stopped
2022-07-18T09:11:05.761705266Z s6-rc: info: service s6rc-oneshot-runner: stopping
2022-07-18T09:11:05.763217482Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2022-07-18T09:11:11.759668967Z s6-rc: info: service cron: starting
2022-07-18T09:11:11.759767212Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:11:11.765525831Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:11:11.768179607Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:11:11.771472464Z Starting crond
2022-07-18T09:11:11.776595867Z s6-rc: info: service 1-startup: starting
2022-07-18T09:11:11.777114181Z s6-rc: info: service cron successfully started
2022-07-18T09:11:11.778885958Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:11:11.791467069Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:11:11.791602658Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:11:11.791619201Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:11:11.792571652Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:11:11.796812626Z
2022-07-18T09:11:11.796833653Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:11:11.816620005Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:11:11.816645368Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
2022-07-18T09:11:11.843157320Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:11:11.848296183Z s6-rc: info: service legacy-cont-init successfully started
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:11:11.862173404Z
2022-07-18T09:11:11.864562898Z   [i] Installing latest logrotate script...
2022-07-18T09:11:11.864582590Z 	[i] Existing logrotate file found. No changes made.
2022-07-18T09:11:11.894037176Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:11:11.895894375Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:11:11.902693273Z FTL binding to default interface: eth0
2022-07-18T09:11:11.908075972Z ::: Enabling Query Logging
2022-07-18T09:11:11.944159532Z ::: Assigning password defined by Environment Variable
2022-07-18T09:11:11.967854050Z   [✓] New password set
2022-07-18T09:11:11.968541178Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:11:11.985047940Z Added ENV to php:
2022-07-18T09:11:11.985948492Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:11:11.985963651Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:11:11.985968943Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:11:11.985973105Z 			"CORS_HOSTS" => "",
2022-07-18T09:11:11.985976784Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:11:11.986260782Z Using IPv4 and IPv6
2022-07-18T09:11:12.005356281Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:11:12.005948806Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:11:12.022901442Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:11:12.023030994Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:11:12.023119046Z ::: Docker start setup complete
2022-07-18T09:11:12.034383144Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:11:12.040182475Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:11:12.044543894Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:11:12.044784353Z   Container tag is: dev
2022-07-18T09:11:12.045333401Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:11:12.045624761Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:11:12.047164851Z s6-rc: info: service pihole-FTL successfully started
2022-07-18T09:11:12.047412317Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:11:12.048312560Z s6-rc: info: service lighttpd: starting
2022-07-18T09:11:12.049189884Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:11:12.049981123Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:11:12.051501367Z Starting lighttpd
2022-07-18T09:11:12.054524206Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:11:16.124574772Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:11:16.137937842Z
  [✓] Preparing new gravity database
2022-07-18T09:11:16.158206492Z   [i] Using libz compression
2022-07-18T09:11:16.158435722Z
2022-07-18T09:11:16.158723799Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
2022-07-18T09:11:16.764462978Z s6-rc: fatal: timed out
2022-07-18T09:11:16.765737250Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
2022-07-18T09:11:16.765803046Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2022-07-18T09:11:16.765932139Z prog: fatal: stopping the container.
2022-07-18T09:11:16.767811029Z s6-rc: info: service legacy-cont-init: stopping
2022-07-18T09:11:16.767940454Z s6-rc: info: service lighttpd: stopping
2022-07-18T09:11:16.768271199Z s6-rc: info: service cron: stopping
2022-07-18T09:11:16.770881645Z Stopping lighttpd
2022-07-18T09:11:16.771613547Z Stopping cron
2022-07-18T09:11:16.772618853Z s6-rc: info: service legacy-cont-init successfully stopped
2022-07-18T09:11:16.773529106Z s6-rc: info: service fix-attrs: stopping
2022-07-18T09:11:16.774185147Z s6-rc: info: service cron successfully stopped
2022-07-18T09:11:16.775019919Z s6-rc: info: service fix-attrs successfully stopped
2022-07-18T09:11:16.779625314Z s6-rc: info: service lighttpd successfully stopped
2022-07-18T09:11:16.779906178Z s6-rc: info: service pihole-FTL: stopping
2022-07-18T09:11:16.782763129Z Stopping pihole-FTL
2022-07-18T09:11:16.784827043Z s6-rc: info: service pihole-FTL successfully stopped
2022-07-18T09:11:16.784933277Z s6-rc: info: service 1-startup: stopping
2022-07-18T09:11:16.785914830Z s6-rc: info: service 1-startup successfully stopped
2022-07-18T09:11:16.785966786Z s6-rc: info: service s6rc-oneshot-runner: stopping
2022-07-18T09:11:16.787871351Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
🦎🖥  ✔ ~/dev/docker-pi-hole [master|…6]
11:11 $ docker logs -tf pihole
2022-07-18T09:10:49.760131874Z s6-rc: info: service cron: starting
2022-07-18T09:10:49.760604849Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:10:49.762721559Z s6-rc: info: service cron successfully started
2022-07-18T09:10:49.764263076Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:10:49.766818904Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:10:49.766829968Z s6-rc: info: service 1-startup: starting
2022-07-18T09:10:49.771727652Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:10:49.773193924Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:10:49.773211195Z Starting crond
2022-07-18T09:10:49.773323939Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:10:49.773668939Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:10:49.776341620Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:10:49.778155631Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:10:49.778711281Z s6-rc: info: service legacy-cont-init successfully started
2022-07-18T09:10:49.786727410Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:10:49.794080954Z
2022-07-18T09:10:49.794096634Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:10:49.800519722Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:10:49.856390391Z
  [✓] Installing latest logrotate script
2022-07-18T09:10:50.075955807Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:10:50.077167725Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:10:50.081211377Z FTL binding to default interface: eth0
2022-07-18T09:10:50.085782902Z ::: Enabling Query Logging
2022-07-18T09:10:50.121473992Z ::: Assigning password defined by Environment Variable
2022-07-18T09:10:50.146079966Z   [✓] New password set
2022-07-18T09:10:50.146520477Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:10:50.164383285Z Added ENV to php:
2022-07-18T09:10:50.165019498Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:10:50.165033859Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:10:50.165038484Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:10:50.165057946Z 			"CORS_HOSTS" => "",
2022-07-18T09:10:50.165062896Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:10:50.165770569Z Using IPv4 and IPv6
2022-07-18T09:10:50.186667581Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:10:50.187329305Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:10:50.232674003Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:10:50.232692357Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:10:50.234489224Z ::: Docker start setup complete
2022-07-18T09:10:50.256531125Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:10:50.286687934Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:10:50.293702083Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:10:50.293712348Z   Container tag is: dev
2022-07-18T09:10:50.293666883Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:10:50.293722258Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:10:50.319829266Z s6-rc: info: service pihole-FTL successfully started
2022-07-18T09:10:50.319848356Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:10:50.320119904Z s6-rc: info: service lighttpd: starting
2022-07-18T09:10:50.322330117Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:10:50.324736285Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:10:50.337929962Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:10:50.344205435Z Starting lighttpd
2022-07-18T09:10:54.519138670Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:10:54.535538915Z
  [✓] Preparing new gravity database
2022-07-18T09:10:54.575070356Z   [i] Using libz compression
2022-07-18T09:10:54.575090426Z
2022-07-18T09:10:54.575125609Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
2022-07-18T09:10:54.764329646Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2022-07-18T09:10:54.764373168Z s6-rc: fatal: timed out
2022-07-18T09:10:54.768055494Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
2022-07-18T09:10:54.768097896Z prog: fatal: stopping the container.
2022-07-18T09:10:54.775282169Z s6-rc: info: service legacy-cont-init: stopping
2022-07-18T09:10:54.776481191Z s6-rc: info: service lighttpd: stopping
2022-07-18T09:10:54.777556842Z s6-rc: info: service cron: stopping
2022-07-18T09:10:54.785628796Z   [i] Status: Pending...Stopping lighttpd
2022-07-18T09:10:54.795304894Z Stopping cron
2022-07-18T09:10:54.800022295Z s6-rc: info: service cron successfully stopped
2022-07-18T09:10:54.801014733Z s6-rc: info: service legacy-cont-init successfully stopped
2022-07-18T09:10:54.801195017Z s6-rc: info: service fix-attrs: stopping
2022-07-18T09:10:54.802764786Z s6-rc: info: service fix-attrs successfully stopped
2022-07-18T09:10:54.809806323Z s6-rc: info: service lighttpd successfully stopped
2022-07-18T09:10:54.810178243Z s6-rc: info: service pihole-FTL: stopping
2022-07-18T09:10:54.813092225Z Stopping pihole-FTL
2022-07-18T09:10:54.816466186Z s6-rc: info: service pihole-FTL successfully stopped
2022-07-18T09:10:54.816786959Z s6-rc: info: service 1-startup: stopping
2022-07-18T09:10:54.817651336Z s6-rc: info: service 1-startup successfully stopped
2022-07-18T09:10:54.817899629Z s6-rc: info: service s6rc-oneshot-runner: stopping
2022-07-18T09:10:54.820773286Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2022-07-18T09:11:00.723721649Z s6-rc: info: service cron: starting
2022-07-18T09:11:00.723884715Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:11:00.725870441Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:11:00.728368799Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:11:00.731795075Z s6-rc: info: service 1-startup: starting
2022-07-18T09:11:00.732841501Z s6-rc: info: service cron successfully started
2022-07-18T09:11:00.736389535Z Starting crond
2022-07-18T09:11:00.738243677Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:11:00.746599537Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:11:00.746646860Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:11:00.749134643Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:11:00.749153837Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:11:00.762365971Z
2022-07-18T09:11:00.762390717Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:11:00.762407518Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:11:00.762412070Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:11:00.765191079Z s6-rc: info: service legacy-cont-init successfully started
2022-07-18T09:11:00.809473303Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:11:00.833913900Z
2022-07-18T09:11:00.836982531Z   [i] Installing latest logrotate script...
2022-07-18T09:11:00.837000336Z 	[i] Existing logrotate file found. No changes made.
2022-07-18T09:11:00.868125709Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:11:00.870158219Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:11:00.877872906Z FTL binding to default interface: eth0
2022-07-18T09:11:00.882910411Z ::: Enabling Query Logging
2022-07-18T09:11:00.921158062Z ::: Assigning password defined by Environment Variable
2022-07-18T09:11:00.951381757Z   [✓] New password set
2022-07-18T09:11:00.951402492Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:11:00.968200285Z Added ENV to php:
2022-07-18T09:11:00.969328706Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:11:00.969340607Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:11:00.969345537Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:11:00.969349640Z 			"CORS_HOSTS" => "",
2022-07-18T09:11:00.969353367Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:11:00.969872690Z Using IPv4 and IPv6
2022-07-18T09:11:00.988901083Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:11:00.989298463Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:11:01.008343459Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:11:01.008642597Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:11:01.008956663Z ::: Docker start setup complete
2022-07-18T09:11:01.020494263Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:11:01.026296845Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:11:01.030683151Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:11:01.030877620Z   Container tag is: dev
2022-07-18T09:11:01.031361733Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:11:01.031533955Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:11:01.033049917Z s6-rc: info: service pihole-FTL successfully started
2022-07-18T09:11:01.033248432Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:11:01.033417955Z s6-rc: info: service lighttpd: starting
2022-07-18T09:11:01.034681139Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:11:01.034870912Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:11:01.036613012Z Starting lighttpd
2022-07-18T09:11:01.044782390Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:11:05.116833796Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:11:05.148590853Z
  [✓] Preparing new gravity database
2022-07-18T09:11:05.188874569Z   [i] Using libz compression
2022-07-18T09:11:05.189008818Z
2022-07-18T09:11:05.189457602Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
2022-07-18T09:11:05.728102952Z s6-rc: fatal: timed out
2022-07-18T09:11:05.728123159Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2022-07-18T09:11:05.730107361Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
2022-07-18T09:11:05.730147757Z prog: fatal: stopping the container.
2022-07-18T09:11:05.735556617Z s6-rc: info: service legacy-cont-init: stopping
2022-07-18T09:11:05.737670726Z s6-rc: info: service lighttpd: stopping
2022-07-18T09:11:05.738140953Z s6-rc: info: service cron: stopping
2022-07-18T09:11:05.743773287Z Stopping lighttpd
2022-07-18T09:11:05.746670967Z Stopping cron
2022-07-18T09:11:05.748668257Z s6-rc: info: service legacy-cont-init successfully stopped
2022-07-18T09:11:05.748793268Z s6-rc: info: service fix-attrs: stopping
2022-07-18T09:11:05.749734762Z s6-rc: info: service fix-attrs successfully stopped
2022-07-18T09:11:05.751538488Z s6-rc: info: service cron successfully stopped
2022-07-18T09:11:05.755189532Z s6-rc: info: service lighttpd successfully stopped
2022-07-18T09:11:05.755384266Z s6-rc: info: service pihole-FTL: stopping
2022-07-18T09:11:05.758105064Z Stopping pihole-FTL
2022-07-18T09:11:05.760206659Z s6-rc: info: service pihole-FTL successfully stopped
2022-07-18T09:11:05.760428931Z s6-rc: info: service 1-startup: stopping
2022-07-18T09:11:05.761503922Z s6-rc: info: service 1-startup successfully stopped
2022-07-18T09:11:05.761705266Z s6-rc: info: service s6rc-oneshot-runner: stopping
2022-07-18T09:11:05.763217482Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2022-07-18T09:11:11.759668967Z s6-rc: info: service cron: starting
2022-07-18T09:11:11.759767212Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:11:11.765525831Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:11:11.768179607Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:11:11.771472464Z Starting crond
2022-07-18T09:11:11.776595867Z s6-rc: info: service 1-startup: starting
2022-07-18T09:11:11.777114181Z s6-rc: info: service cron successfully started
2022-07-18T09:11:11.778885958Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:11:11.791467069Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:11:11.791602658Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:11:11.791619201Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:11:11.792571652Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:11:11.796812626Z
2022-07-18T09:11:11.796833653Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:11:11.816620005Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:11:11.816645368Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
2022-07-18T09:11:11.843157320Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:11:11.848296183Z s6-rc: info: service legacy-cont-init successfully started
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:11:11.862173404Z
2022-07-18T09:11:11.864562898Z   [i] Installing latest logrotate script...
2022-07-18T09:11:11.864582590Z 	[i] Existing logrotate file found. No changes made.
2022-07-18T09:11:11.894037176Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:11:11.895894375Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:11:11.902693273Z FTL binding to default interface: eth0
2022-07-18T09:11:11.908075972Z ::: Enabling Query Logging
2022-07-18T09:11:11.944159532Z ::: Assigning password defined by Environment Variable
2022-07-18T09:11:11.967854050Z   [✓] New password set
2022-07-18T09:11:11.968541178Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:11:11.985047940Z Added ENV to php:
2022-07-18T09:11:11.985948492Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:11:11.985963651Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:11:11.985968943Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:11:11.985973105Z 			"CORS_HOSTS" => "",
2022-07-18T09:11:11.985976784Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:11:11.986260782Z Using IPv4 and IPv6
2022-07-18T09:11:12.005356281Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:11:12.005948806Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:11:12.022901442Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:11:12.023030994Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:11:12.023119046Z ::: Docker start setup complete
2022-07-18T09:11:12.034383144Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:11:12.040182475Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:11:12.044543894Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:11:12.044784353Z   Container tag is: dev
2022-07-18T09:11:12.045333401Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:11:12.045624761Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:11:12.047164851Z s6-rc: info: service pihole-FTL successfully started
2022-07-18T09:11:12.047412317Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:11:12.048312560Z s6-rc: info: service lighttpd: starting
2022-07-18T09:11:12.049189884Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:11:12.049981123Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:11:12.051501367Z Starting lighttpd
2022-07-18T09:11:12.054524206Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:11:16.124574772Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:11:16.137937842Z
  [✓] Preparing new gravity database
2022-07-18T09:11:16.158206492Z   [i] Using libz compression
2022-07-18T09:11:16.158435722Z
2022-07-18T09:11:16.158723799Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
2022-07-18T09:11:16.764462978Z s6-rc: fatal: timed out
2022-07-18T09:11:16.765737250Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
2022-07-18T09:11:16.765803046Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2022-07-18T09:11:16.765932139Z prog: fatal: stopping the container.
2022-07-18T09:11:16.767811029Z s6-rc: info: service legacy-cont-init: stopping
2022-07-18T09:11:16.767940454Z s6-rc: info: service lighttpd: stopping
2022-07-18T09:11:16.768271199Z s6-rc: info: service cron: stopping
2022-07-18T09:11:16.770881645Z Stopping lighttpd
2022-07-18T09:11:16.771613547Z Stopping cron
2022-07-18T09:11:16.772618853Z s6-rc: info: service legacy-cont-init successfully stopped
2022-07-18T09:11:16.773529106Z s6-rc: info: service fix-attrs: stopping
2022-07-18T09:11:16.774185147Z s6-rc: info: service cron successfully stopped
2022-07-18T09:11:16.775019919Z s6-rc: info: service fix-attrs successfully stopped
2022-07-18T09:11:16.779625314Z s6-rc: info: service lighttpd successfully stopped
2022-07-18T09:11:16.779906178Z s6-rc: info: service pihole-FTL: stopping
2022-07-18T09:11:16.782763129Z Stopping pihole-FTL
2022-07-18T09:11:16.784827043Z s6-rc: info: service pihole-FTL successfully stopped
2022-07-18T09:11:16.784933277Z s6-rc: info: service 1-startup: stopping
2022-07-18T09:11:16.785914830Z s6-rc: info: service 1-startup successfully stopped
2022-07-18T09:11:16.785966786Z s6-rc: info: service s6rc-oneshot-runner: stopping
2022-07-18T09:11:16.787871351Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2022-07-18T09:11:22.703900623Z s6-rc: info: service cron: starting
2022-07-18T09:11:22.703922100Z s6-rc: info: service s6rc-oneshot-runner: starting
2022-07-18T09:11:22.713302079Z s6-rc: info: service cron successfully started
2022-07-18T09:11:22.714776450Z Starting crond
2022-07-18T09:11:22.715041868Z s6-rc: info: service s6rc-oneshot-runner successfully started
2022-07-18T09:11:22.715527155Z s6-rc: info: service fix-attrs: starting
2022-07-18T09:11:22.715540928Z s6-rc: info: service 1-startup: starting
2022-07-18T09:11:22.719145199Z fix-attrs: info: applying /etc/fix-attrs.d/01-resolver-resolv
2022-07-18T09:11:22.720821043Z fix-attrs: warning: fix-attrs is deprecated, please fix volume permissions in your container manager instead
2022-07-18T09:11:22.721312217Z s6-rc: info: service fix-attrs successfully started
2022-07-18T09:11:22.721528128Z s6-rc: info: service legacy-cont-init: starting
2022-07-18T09:11:22.726306817Z cont-init: info: running /etc/cont-init.d/05-changer-uid-gid.sh
2022-07-18T09:11:22.728199895Z  ::: Starting docker specific checks & setup for docker pihole/pihole
2022-07-18T09:11:22.728229583Z cont-init: info: /etc/cont-init.d/05-changer-uid-gid.sh exited 0
2022-07-18T09:11:22.728654708Z s6-rc: info: service legacy-cont-init successfully started
2022-07-18T09:11:22.730213788Z
2022-07-18T09:11:22.730225965Z   [i] Installing configs from /etc/.pihole...
2022-07-18T09:11:22.732055331Z   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
2022-07-18T09:11:22.775399725Z
2022-07-18T09:11:22.775419367Z   [i] Installing latest logrotate script...
2022-07-18T09:11:22.775435643Z 	[i] Existing logrotate file found. No changes made.
2022-07-18T09:11:22.799913763Z Existing DNS servers detected in setupVars.conf. Leaving them alone
2022-07-18T09:11:22.801874891Z Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
2022-07-18T09:11:22.809027622Z FTL binding to default interface: eth0
2022-07-18T09:11:22.813674868Z ::: Enabling Query Logging
2022-07-18T09:11:22.849337621Z ::: Assigning password defined by Environment Variable
2022-07-18T09:11:22.872258321Z   [✓] New password set
2022-07-18T09:11:22.872603819Z Setting Web Theme based on WEBTHEME variable, using value default-light
2022-07-18T09:11:22.888772570Z Added ENV to php:
2022-07-18T09:11:22.889846114Z 			"TZ" => "Europe/Berlin",
2022-07-18T09:11:22.889860189Z 			"PIHOLE_DOCKER_TAG" => "dev",
2022-07-18T09:11:22.889865178Z 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
2022-07-18T09:11:22.889869123Z 			"CORS_HOSTS" => "",
2022-07-18T09:11:22.889872889Z 			"VIRTUAL_HOST" => "0.0.0.0",
2022-07-18T09:11:22.890020503Z Using IPv4 and IPv6
2022-07-18T09:11:22.908837411Z   [✓] Setting admin contact to [email protected]
2022-07-18T09:11:22.909310136Z ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
2022-07-18T09:11:22.926184092Z ::: Testing lighttpd config: Syntax OK
2022-07-18T09:11:22.926391519Z ::: All config checks passed, cleared for startup ...
2022-07-18T09:11:22.926402912Z ::: Docker start setup complete
2022-07-18T09:11:22.937415474Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-18T09:11:22.943137129Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-18T09:11:22.947482776Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-18T09:11:22.947653021Z   Container tag is: dev
2022-07-18T09:11:22.948223015Z s6-rc: info: service 1-startup successfully started
2022-07-18T09:11:22.948359159Z s6-rc: info: service pihole-FTL: starting
2022-07-18T09:11:22.949949689Z s6-rc: info: service pihole-FTL successfully started

Jul 18 '22 09:07 thomasmerz

@thomasmerz is that a fresh container with empty volume mounts? Looks like the gravity on boot one-shot is timing out... I've not seen that in my testing so far

2022-07-18T09:11:12.047412317Z s6-rc: info: service 1-gravityonboot: starting
2022-07-18T09:11:12.048312560Z s6-rc: info: service lighttpd: starting
2022-07-18T09:11:12.049189884Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-18T09:11:12.049981123Z s6-rc: info: service lighttpd successfully started
2022-07-18T09:11:12.051501367Z Starting lighttpd
2022-07-18T09:11:12.054524206Z Starting pihole-FTL (no-daemon) as pihole
2022-07-18T09:11:16.124574772Z   [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range
2022-07-18T09:11:16.137937842Z
  [✓] Preparing new gravity database
2022-07-18T09:11:16.158206492Z   [i] Using libz compression
2022-07-18T09:11:16.158435722Z
2022-07-18T09:11:16.158723799Z   [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [✓] Status: Retrieval successful
2022-07-18T09:11:16.764462978Z s6-rc: fatal: timed out

The key here being:

2022-07-18T09:11:16.764462978Z s6-rc: fatal: timed out

I wonder what, if anything, is causing gravity to timeout. Can you try seeing the SKIPGRAVITYONBOOT env var to 1 and seeing if that makes a diff, please?

Jul 18 '22 10:07 PromoFaux

To troubleshoot start problems I 've added in dockerfile ENV S6_BEHAVIOUR_IF_STAGE2_FAILS 1 ENV S6_CMD_WAIT_FOR_SERVICES_MAXTIME=30000

You could set theese in docker-compose env. On a RPI3, I still have S6-rc time out but the container continue to boot thanks to S6_BEHAVIOUR_IF_STAGE2_FAILS 1. I'm not sure the Wait maxtime is high enough to allow the service not being in timeout. on a laptop, no timeout problem.

pihole-pihole-1  |   [i] List stayed unchanged
pihole-pihole-1  | s6-rc: fatal: timed out
pihole-pihole-1  | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
pihole-pihole-1  | s6-sudoc: fatal: unable to get exit status from server: Operation timed out
pihole-pihole-1  | 
pihole-pihole-1  |   [i] Target: https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
....
pihole-pihole-1  |   [✓] Pi-hole blocking is enabled

Jul 18 '22 15:07 edgd1er

on a laptop, no timeout problem.

This may be where i was going wrong with my testing - it was on my desktop :D

Jul 18 '22 16:07 PromoFaux

Existing DNS servers detected in setupVars.conf. Leaving them alone
::: Pre existing WEBPASSWORD found
DNSMasq binding to default interface: eth0
Added ENV to php:
			"TZ" => "",
			"PIHOLE_DOCKER_TAG" => "2022.04.3",
			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
			"ServerIP" => "0.0.0.0",
			"CORS_HOSTS" => "",
			"VIRTUAL_HOST" => "0.0.0.0",
Using IPv4 and IPv6
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Enabling Query Logging
  [i] Enabling logging...

  [✓] Logging has been enabled!
 ::: Docker start setup complete
  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
  Pi-hole version is v5.11.4 (Latest: v5.11.4)
  AdminLTE version is v5.13 (Latest: v5.13)
  FTL version is v5.16.1 (Latest: v5.16.1)
  Container tag is: 2022.04.3
[cont-init.d] 20-start.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting lighttpd
Starting pihole-FTL (no-daemon) as pihole
Starting crond
[services.d] done.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
Stopping lighttpd
s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening
s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening
Stopping pihole-FTL
Stopping cron
s6-svwait: fatal: supervisor died
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 05-changer-uid-gid.sh: executing... 
[cont-init.d] 05-changer-uid-gid.sh: exited 0.
[cont-init.d] 20-start.sh: executing... 
 ::: Starting docker specific checks & setup for docker pihole/pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [i] Installing /etc/dnsmasq.d/01-pihole.conf...
  [✓] Installed /etc/dnsmasq.d/01-pihole.conf
  [i] Installing /etc/.pihole/advanced/06-rfc6761.conf...
  [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
Applying pihole-FTL.conf setting REPLY_ADDR4=0.0.0.0
Existing DNS servers detected in setupVars.conf. Leaving them alone
::: Pre existing WEBPASSWORD found
DNSMasq binding to default interface: eth0
Added ENV to php:
			"TZ" => "",
			"PIHOLE_DOCKER_TAG" => "2022.04.3",
			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
			"ServerIP" => "0.0.0.0",
			"CORS_HOSTS" => "",
			"VIRTUAL_HOST" => "0.0.0.0",
Using IPv4 and IPv6
::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
::: Testing lighttpd config: Syntax OK
::: All config checks passed, cleared for startup ...
::: Enabling Query Logging
  [i] Enabling logging...

  [✓] Logging has been enabled!
 ::: Docker start setup complete
  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
  Pi-hole version is v5.11.4 (Latest: v5.11.4)
  AdminLTE version is v5.13 (Latest: v5.13)
  FTL version is v5.16.1 (Latest: v5.16.1)
  Container tag is: 2022.04.3
[cont-init.d] 20-start.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting crond
Starting pihole-FTL (no-daemon) as pihole
Starting lighttpd
[services.d] done.
Stopping lighttpd
Stopping cron
Stopping pihole-FTL
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening
s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

If I restart the Pi then the container does not start with the message in the log

s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-access-log: supervisor not listening
s6-svc: fatal: unable to control /var/run/s6/services/lighttpd-error-log: supervisor not listening

Jul 21 '22 18:07 SnakeEater96

@SnakeEate98r, please try the :dev tag once the following job has completed building:

https://github.com/pi-hole/docker-pi-hole/runs/7456030015?check_suite_focus=true

Jul 21 '22 18:07 PromoFaux

[✓] Pi-hole blocking is enabled s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service _gravityonboot: stopping s6-rc: info: service lighttpd: stopping s6-rc: info: service cron: stopping s6-rc: info: service _gravityonboot successfully stopped Stopping lighttpd Stopping cron s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service cron successfully stopped s6-rc: info: service lighttpd successfully stopped s6-rc: info: service pihole-FTL: stopping Stopping pihole-FTL s6-rc: info: service pihole-FTL successfully stopped s6-rc: info: service _startup: stopping s6-rc: info: service _startup successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

Not Working

Jul 21 '22 19:07 SnakeEater96

How long after seeing [✓] Pi-hole blocking is enabled do things start stopping? Please open a new issue as this might be something different (include logs from /var/log/pihole if you can, please. (you might need to mount that directory to the host)

Jul 21 '22 19:07 PromoFaux

the problem occurred when I changed the dev channel and then completely restarted the server

Jul 21 '22 19:07 SnakeEater96

@thomasmerz can you try again on latest dev, please?

Jul 22 '22 09:07 PromoFaux

I tried with this:

Docker Tag dev Pi-hole v5.11.4 FTL v5.16.1 Web Interface v5.13

$ docker images|grep pihole pihole/pihole dev a8ce65e0ac18 19 hours ago 305MB pihole/pihole latest 2b580d272b6c 12 days ago 303MB

Result:

[x] GUI is up and running (also https)
[x] last message in docker logs -tf pihole is 2022-07-22T14:07:23.767315319Z [✓] Pi-hole blocking is enabled

Jul 22 '22 14:07 thomasmerz

Running with latest again because this is my "production" Pi-hole at home running in Docker on OpenSUSE 15.3 <- this is the only case where this problem arose, but not on my other Pi-hole instances running on Ubuntu 22.04 LTS… 🤷🏼‍♂️

Docker Tag 2022.07.1 Pi-hole v5.11.4 FTL v5.16.1 Web Interface v5.13

Last messages:

…
2022-07-22T14:14:26.189659887Z  ::: Docker start setup complete
2022-07-22T14:14:26.190096461Z   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2022-07-22T14:14:26.207493690Z   Pi-hole version is v5.11.4 (Latest: v5.11.4)
2022-07-22T14:14:26.215472553Z   AdminLTE version is v5.13 (Latest: v5.13)
2022-07-22T14:14:26.222750375Z   FTL version is v5.16.1 (Latest: v5.16.1)
2022-07-22T14:14:26.223148161Z   Container tag is: 2022.07.1
2022-07-22T14:14:26.224206725Z [cont-init.d] 20-start.sh: exited 0.
2022-07-22T14:14:26.225515748Z [cont-init.d] done.
2022-07-22T14:14:26.226989639Z [services.d] starting services
2022-07-22T14:14:26.236832957Z Starting lighttpd
2022-07-22T14:14:26.237030980Z Starting crond
2022-07-22T14:14:26.237093908Z Starting pihole-FTL (no-daemon) as pihole
2022-07-22T14:14:26.239469474Z [services.d] done.

Waiting for…?!

…
2022-07-22T08:03:04.284896549Z Starting pihole-FTL (no-daemon) as pihole
2022-07-22T09:03:04.856634220Z Stopping pihole-FTL
2022-07-22T09:03:05.269458682Z Starting pihole-FTL (no-daemon) as pihole
2022-07-22T10:03:04.257280630Z Stopping pihole-FTL
2022-07-22T10:03:04.672792940Z Starting pihole-FTL (no-daemon) as pihole
2022-07-22T11:03:04.546169681Z Stopping pihole-FTL
2022-07-22T11:03:04.970292507Z Starting pihole-FTL (no-daemon) as pihole
2022-07-22T12:03:04.654210476Z Stopping pihole-FTL
2022-07-22T12:03:05.078003680Z Starting pihole-FTL (no-daemon) as pihole
2022-07-22T13:03:04.619979617Z Stopping pihole-FTL
…

Jul 22 '22 14:07 thomasmerz

2022-07-22T15:03:04.676500960Z Stopping pihole-FTL 
2022-07-22T15:03:05.088685699Z Starting pihole-FTL (no-daemon) as pihole

Jul 22 '22 15:07 thomasmerz

Anything interesting in /var/log/pihole/FTL.log?

Jul 22 '22 15:07 PromoFaux

If you mean that "errors" or "warnings" are "interesting": no.

root@pihole-merz-nimbus:/var/log/pihole# grep WARN FTL.log
[2022-07-22 17:03:04.942 539M] WARNING: Unable to remove PORT file: Permission denied
[2022-07-22 17:03:04.942 539M] WARNING: Unable to remove PID file: Permission denied
[2022-07-22 18:03:04.837 9083M] WARNING: Unable to remove PORT file: Permission denied
[2022-07-22 18:03:04.837 9083M] WARNING: Unable to remove PID file: Permission denied
root@pihole-merz-nimbus:/var/log/pihole# grep ERR FTL.log
[2022-07-22 16:40:06.065 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.105 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.105 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.915 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.915 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.916 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.916 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.917 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.917 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43

Jul 22 '22 16:07 thomasmerz

The warnings can be ignored, and will be sorted on the next FTL release https://github.com/pi-hole/FTL/pull/1384

The Err's however, that is a new one to me! @DL6ER ?

Jul 22 '22 16:07 PromoFaux

We've seen them before, it's a bug in dnsmasq and we already submitted a patch upstream: https://github.com/pi-hole/dnsmasq/pull/10

However, there may be more similar bugs in the Dnsmasq code. @thomasmerz could you find the exact lines in pihole.log? If it is too noisy, we can enable debugging output (DEBUG_QUERIES=true) in FTL to make this a lot easier. Does it happen often (grep -c ...)?

Jul 22 '22 16:07 DL6ER

12 times grep ERR FTL.log -ic
Did you really want the file numbers? 🤔

$ grep ERR -n FTL.log
108:[2022-07-22 16:40:06.065 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
109:[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
110:[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
111:[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
112:[2022-07-22 16:40:06.105 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
113:[2022-07-22 16:40:06.105 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43re 
115:[2022-07-22 16:45:07.915 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
116:[2022-07-22 16:45:07.915 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
117:[2022-07-22 16:45:07.916 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
118:[2022-07-22 16:45:07.916 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
119:[2022-07-22 16:45:07.917 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
120:[2022-07-22 16:45:07.917 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43

there is no "ERR" or "WARN" in pihole.log - we were talking about FTL.log.

Jul 22 '22 16:07 thomasmerz

Sorry, I could have been clearer. These warning have been triggered by queries happening at that time. The queries causing these errors have been logged in pihole.log as FTL.log does not contain any debugging information without debugging mod enabled. That's why I asked for the "exact lines" over there.

Jul 22 '22 17:07 DL6ER

I got you and focussed on "2022-07-22 16:40:0x":

root@pihole-merz-nimbus:/var/log/pihole# grep ERR FTL.log
[2022-07-22 16:40:06.065 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.066 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.105 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:40:06.105 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.915 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.915 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.916 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.916 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.917 539M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 16:45:07.917 539M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 20:40:10.875 27492M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 20:40:10.875 27492M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43
[2022-07-22 21:21:43.490 1182M] ERR: Port mismatch for 45.90.28.39: we derived 53, dnsmasq told us 43
[2022-07-22 21:21:43.490 1182M] ERR: Port mismatch for 45.90.30.39: we derived 53, dnsmasq told us 43

root@pihole-merz-nimbus:/var/log/pihole# grep "Jul 22 16:40:0" pihole.log | grep "45.90"
…
Jul 22 16:40:05 dnsmasq[539]: forwarded de.m.wikipedia.org to 45.90.28.39
Jul 22 16:40:05 dnsmasq[539]: forwarded de.m.wikipedia.org to 45.90.28.39
Jul 22 16:40:05 dnsmasq[539]: forwarded de.m.wikipedia.org to 45.90.28.39
Jul 22 16:40:05 dnsmasq[539]: dnssec-query[DS] wikipedia.org to 45.90.28.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-retry[DS] wikipedia.org to 45.90.28.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-retry[DS] wikipedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-retry[DS] wikipedia.org to 45.90.28.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-retry[DS] wikipedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-retry[DS] wikipedia.org to 45.90.28.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-retry[DS] wikipedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: dnssec-query[DS] wikimedia.org to 45.90.28.39
Jul 22 16:40:06 dnsmasq[539]: forwarded dyna.wikimedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: forwarded upload.wikimedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: forwarded upload.wikimedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: forwarded upload.wikimedia.org to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: forwarded itunes.apple.com to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: forwarded itunes.apple.com to 45.90.30.39
Jul 22 16:40:06 dnsmasq[539]: forwarded itunes.apple.com to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded login.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded login.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded login.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded meta.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded meta.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded meta.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded meta.m.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded meta.m.wikimedia.org to 45.90.30.39
Jul 22 16:40:07 dnsmasq[539]: forwarded meta.m.wikimedia.org to 45.90.30.39
Jul 22 16:40:08 dnsmasq[539]: forwarded meta.wikimedia.org to 45.90.28.39
Jul 22 16:40:08 dnsmasq[539]: forwarded meta.wikimedia.org to 45.90.30.39
root@pihole-merz-nimbus:/var/log/pihole#

Jul 22 '22 19:07 thomasmerz

~16:45

…
Jul 22 16:45:06 dnsmasq[539]: dnssec-query[DS] eu to 45.90.28.39
Jul 22 16:45:06 dnsmasq[539]: dnssec-query[DS] amazon.eu to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded arcus-uswest.amazon.com to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded c.amazon-adsystem.com to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded mads.amazon-adsystem.com to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded mads-eu.amazon.com to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded d1ykf07e75w7ss.cloudfront.net to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded d1ykf07e75w7ss.cloudfront.net to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: forwarded mads.amazon.com to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-retry[DS] amazon.eu to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-retry[DS] amazon.eu to 45.90.30.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-retry[DS] amazon.eu to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-retry[DS] amazon.eu to 45.90.30.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-retry[DS] amazon.eu to 45.90.28.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-retry[DS] amazon.eu to 45.90.30.39
Jul 22 16:45:07 dnsmasq[539]: dnssec-query[DNSKEY] eu to 45.90.30.39

Jul 22 '22 19:07 thomasmerz

~20:40:10

Jul 22 20:40:10 dnsmasq[27492]: dnssec-query[DS] fsit.com to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: forwarded diefsspeed001.fsit.com to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: forwarded speedtest.iway.ch to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: dnssec-query[DS] iway.ch to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: dnssec-query[DNSKEY] iway.ch to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: forwarded speedtest.iway.ch to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: dnssec-retry[DS] azure.com to 45.90.28.39
Jul 22 20:40:10 dnsmasq[27492]: dnssec-retry[DS] azure.com to 45.90.30.39
Jul 22 20:40:10 dnsmasq[27492]: forwarded pexsucpeu02.westeurope.cloudapp.azure.com to 45.90.28.39

Jul 22 '22 19:07 thomasmerz

~21:21:43:

Jul 22 21:21:43 dnsmasq[1182]: dnssec-retry[DS] app to 45.90.28.39
Jul 22 21:21:43 dnsmasq[1182]: dnssec-retry[DS] app to 45.90.30.39
Jul 22 21:21:43 dnsmasq[1182]: forwarded lbnew.consentmanager.net to 45.90.28.39
Jul 22 21:21:43 dnsmasq[1182]: forwarded lbnew.consentmanager.net to 45.90.30.39
Jul 22 21:21:43 dnsmasq[1182]: forwarded 1376624012.rsc.cdn77.org to 45.90.28.39
Jul 22 21:21:43 dnsmasq[1182]: forwarded 1376624012.rsc.cdn77.org to 45.90.30.39
Jul 22 21:21:43 dnsmasq[1182]: dnssec-query[DS] permutive.app to 45.90.28.39
Jul 22 21:21:43 dnsmasq[1182]: dnssec-query[DNSKEY] app to 45.90.28.39
Jul 22 21:21:43 dnsmasq[1182]: dnssec-query[DNSKEY] permutive.app to 45.90.28.39

Jul 22 '22 19:07 thomasmerz

Okay, so nothing unexpected, these errors all come from dnssec-retry queries and this has already been fixed in the upstream dnsmasq code (which has not been released, so far). You can safely ignore these errors for now, FTL knows that there is an issue and uses the correct values nonetheless. It just informs you that something is off and might be worth reporting to us. But this one is already fixed.

Jul 23 '22 06:07 DL6ER

docker-pi-hole
docker-pi-hole copied to clipboard

s6 overlay v2? supervisor not listening

Details

Related Issues

How to reproduce the issue

These common fixes didn't work for my issue

Host:

Pihole:

Docker

I tried with this:

Result:

docker-pi-hole docker-pi-hole copied to clipboard

s6 overlay v2? supervisor not listening

Details

Related Issues

How to reproduce the issue

These common fixes didn't work for my issue

Host:

Pihole:

Docker

I tried with this:

Result:

docker-pi-hole
docker-pi-hole copied to clipboard