• PiHole docker error after update to Unraid OS version 6.10.0-rc8


    CODEG33K
    • Closed Minor

    Still investigating what have happened, but after updating from *rc7 to *rc8 my Pihole DoT-DoH docker won't start correctly. It just keeps outputting "Starting pihole-FTL (no-daemon) as pihole" and then "

    Stopping pihole-FTL pihole-FTL: no process found"

     

    Other than that one issue the update went fine.

    today at 20:51:48[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    today at 20:51:48[s6-init] ensuring user provided files have correct perms...exited 0.
    today at 20:51:48[fix-attrs.d] applying ownership & permissions fixes...
    today at 20:51:48[fix-attrs.d] 01-resolver-resolv: applying... 
    today at 20:51:48[fix-attrs.d] 01-resolver-resolv: exited 0.
    today at 20:51:48[fix-attrs.d] done.
    today at 20:51:48[cont-init.d] executing container initialization scripts...
    today at 20:51:48[cont-init.d] 05-changer-uid-gid.sh: executing... 
    today at 20:51:48[cont-init.d] 05-changer-uid-gid.sh: exited 0.
    today at 20:51:48[cont-init.d] 20-start.sh: executing... 
    today at 20:51:48 ::: Starting docker specific checks & setup for docker pihole/pihole
    today at 20:51:48
    today at 20:51:48  [i] Installing configs from /etc/.pihole...
    today at 20:51:48  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
    today at 20:51:48  [i] Installing /etc/dnsmasq.d/01-pihole.conf...
    today at 20:51:48  [i] Installing /etc/.pihole/advanced/06-rfc6761.conf...
    today at 20:51:48Converting DNS1 to PIHOLE_DNS_
    today at 20:51:48Converting DNS2 to PIHOLE_DNS_
    today at 20:51:48Setting DNS servers based on PIHOLE_DNS_ variable
    today at 20:51:48::: Pre existing WEBPASSWORD found
    today at 20:51:48DNSMasq binding to default interface: eth0
    today at 20:51:48Added ENV to php:
    today at 20:51:48			"TZ" => "Europe/Copenhagen",
    today at 20:51:48			"PIHOLE_DOCKER_TAG" => "2022.04.3",
    today at 20:51:48			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
    today at 20:51:48			"ServerIP" => "192.168.1.6",
    today at 20:51:48			"CORS_HOSTS" => "",
    today at 20:51:48			"VIRTUAL_HOST" => "192.168.1.6",
    today at 20:51:48Using IPv4
    today at 20:51:48::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
    today at 20:51:48https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
    today at 20:51:48::: Testing lighttpd config: Syntax OK
    today at 20:51:48::: All config checks passed, cleared for startup ...
    today at 20:51:48::: Enabling Query Logging
    today at 20:51:48  [i] Enabling logging...
    today at 20:51:48
    today at 20:51:48 ::: Docker start setup complete
    today at 20:51:48  Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
    today at 20:51:48  Pi-hole version is v5.10 (Latest: v5.10)
    today at 20:51:48  AdminLTE version is v5.12 (Latest: v5.12)
    today at 20:51:48  FTL version is v5.15 (Latest: v5.15)
    today at 20:51:48  Container tag is: 2022.04.3
    today at 20:51:48[cont-init.d] 20-start.sh: exited 0.
    today at 20:51:48[cont-init.d] done.
    today at 20:51:48[services.d] starting services
    today at 20:51:48Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:48Starting lighttpd
    today at 20:51:48Starting crond
    today at 20:51:48[services.d] done.
    today at 20:51:48Starting stubby
    today at 20:51:49[18:51:49.034940] STUBBY: Stubby version: Stubby 0.3.0
    today at 20:51:49[18:51:49.052317] STUBBY: Read config from file /config/stubby.yml
    today at 20:51:49Starting cloudflared
    today at 20:51:492022-05-10T18:51:49Z INF Version 2022.5.0
    today at 20:51:492022-05-10T18:51:49Z INF GOOS: linux, GOVersion: go1.17.5, GoArch: amd64
    today at 20:51:492022-05-10T18:51:49Z INF Settings: map[config:/config/cloudflared.yml proxy-dns:true proxy-dns-address:127.1.1.1 proxy-dns-port:5153 proxy-dns-upstream:[https://1.1.1.1/dns-query https://1.0.0.1/dns-query]]
    today at 20:51:492022-05-10T18:51:49Z INF Adding DNS upstream url=https://1.1.1.1/dns-query
    today at 20:51:492022-05-10T18:51:49Z INF Adding DNS upstream url=https://1.0.0.1/dns-query
    today at 20:51:492022-05-10T18:51:49Z INF Starting DNS over HTTPS proxy server address=dns://127.1.1.1:5153
    today at 20:51:492022-05-10T18:51:49Z INF cloudflared will not automatically update if installed by a package manager.
    today at 20:51:49Stopping pihole-FTL
    today at 20:51:49pihole-FTL: no process found
    today at 20:51:49Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:49Stopping pihole-FTL
    today at 20:51:49pihole-FTL: no process found
    today at 20:51:50Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:51Stopping pihole-FTL
    today at 20:51:51pihole-FTL: no process found
    today at 20:51:51Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:52Stopping pihole-FTL
    today at 20:51:52pihole-FTL: no process found
    today at 20:51:52Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:52Stopping pihole-FTL
    today at 20:51:52pihole-FTL: no process found
    today at 20:51:53Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:53Stopping pihole-FTL
    today at 20:51:53pihole-FTL: no process found
    today at 20:51:54Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:54Stopping pihole-FTL
    today at 20:51:54pihole-FTL: no process found
    today at 20:51:55Starting pihole-FTL (no-daemon) as pihole
    today at 20:51:56Stopping pihole-FTL

     




    User Feedback

    Recommended Comments

    Rolled back to rc7 - didn't help.

     

    Back on rc8 and tried adding the DNSMASQ_USER=root bit as an environment variable after some google investigation which didn't help either. So just removed the docker installation and cleaned appdata folder and all is working again. 

     

    Will close the report as I still don't know what caused it.

    Link to comment

    I am running 12 pihole containers in total, each of my networks have their own designated dns server pair. Never had any issue with the rc versions.

     

    Perhaps you experienced some database corruption. Clearing the appdata folder would solve that.

     

    Link to comment

    I'm experiencing the exact same issue with docker: "PiHol-DoT-DoH"

    upgrade from 6.9 to 6.10.3

     

    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
    [09:00:35.289898] STUBBY: Stubby version: Stubby 0.3.0
    [09:00:35.293064] STUBBY: Read config from file /config/stubby.yml
    2022-06-20T09:00:37Z INF Version 2022.5.1
    2022-06-20T09:00:37Z INF GOOS: linux, GOVersion: go1.17.5, GoArch: amd64
    2022-06-20T09:00:37Z INF Settings: map[config:/config/cloudflared.yml proxy-dns:true proxy-dns-address:127.1.1.1 proxy-dns-port:5153 proxy-dns-upstream:[https://1.1.1.1/dns-query https://1.0.0.1/dns-query]]
    2022-06-20T09:00:37Z INF Adding DNS upstream url=https://1.1.1.1/dns-query
    2022-06-20T09:00:37Z INF Adding DNS upstream url=https://1.0.0.1/dns-query
    2022-06-20T09:00:37Z INF Starting DNS over HTTPS proxy server address=dns://127.1.1.1:5153
    2022-06-20T09:00:37Z INF cloudflared will not automatically update if installed by a package manager.
    2022-06-20T09:00:42Z WRN Your version 2022.5.1 is outdated. We recommend upgrading it to 2022.6.2
    2022-06-21T06:59:59Z ERR failed to connect to an HTTPS backend "https://1.1.1.1/dns-query" error="failed to perform an HTTPS request: Post \"https://1.1.1.1/dns-query\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
    2022-06-21T07:00:04Z ERR failed to connect to an HTTPS backend "https://1.0.0.1/dns-query" error="failed to perform an HTTPS request: Post \"https://1.0.0.1/dns-query\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
    2022-06-21T07:00:11Z ERR failed to connect to an HTTPS backend "https://1.1.1.1/dns-query" error="failed to perform an HTTPS request: Post \"https://1.1.1.1/dns-query\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
    2022-06-21T09:00:42Z WRN Your version 2022.5.1 is outdated. We recommend upgrading it to 2022.6.3
    2022-06-22T09:00:42Z WRN Your version 2022.5.1 is outdated. We recommend upgrading it to 2022.6.3
    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 lighttpd
    Stopping cron
    Stopping pihole-FTL
    Stopping stubby
    Stopping cloudflared
    [cont-finish.d] executing container finish scripts...
    [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.
    [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!
      [✓] Installed /etc/dnsmasq.d/01-pihole.conf
      [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
    Converting DNS1 to PIHOLE_DNS_
    Converting DNS2 to PIHOLE_DNS_
    Setting DNS servers based on PIHOLE_DNS_ variable
    ::: Pre existing WEBPASSWORD found
    DNSMasq binding to custom interface: br0
    Added ENV to php:
                            "TZ" => "America/Toronto",
                            "PIHOLE_DOCKER_TAG" => "2022.04.3",
                            "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
                            "ServerIP" => "10.0.10.10",
                            "CORS_HOSTS" => "",
                            "VIRTUAL_HOST" => "10.0.10.10",
    Using IPv4
    ::: 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.10 (Latest: v5.10)
      AdminLTE version is v5.12 (Latest: v5.12)
      FTL version is v5.15 (Latest: v5.15)
      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 lighttpd
    Starting pihole-FTL (no-daemon) as pihole
    [services.d] done.
    Starting stubby
    Starting cloudflared
    Stopping stubby
    Stopping cron
    Stopping pihole-FTL
    Stopping lighttpd
    Stopping cloudflared
    [cont-finish.d] executing container finish scripts...
    [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.
    
    ** Press ANY KEY to close this window ** 

     

     

    I will try deleting the dicker and starting from scratch.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.