PiHole Web Interface keeps going back to an older version about docker-pi-hole

[rdwebdesign]

When this happens again, DO NOT run updatechecker and generate a debug log.

[gh0sti]

When this happens again, DO NOT run updatechecker and generate a debug log.

Here is the screen shot of it reverting. I will generate a debug log next

[gh0sti]

https://tricorder.pi-hole.net/CaJWYFA2/

[yubiuser]

This is interesting. It does not only revert the web repo, but all Pi-hole components, except the docker tag.

** [ DIAGNOSING ]: Core version
[✓] Version: v5.15
[i] Remotes: origin	https://github.com/pi-hole/pi-hole (fetch)
             origin	https://github.com/pi-hole/pi-hole (push)
[i] Branch: master
[i] Commit: v5.15-0-g9048429b

*** [ DIAGNOSING ]: Web version
[✓] Version: v5.18.1
[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)
             origin	https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.18.1-0-g30668d4d

*** [ DIAGNOSING ]: FTL version
[✓] Version: v5.20.1
[i] Branch: master
[i] Commit: 47128aaf

rw-r--r-- 1 www-data pi 379 Dec 30 14:21 /etc/pihole/versions
   CORE_BRANCH=master
   WEB_BRANCH=master
   FTL_BRANCH=master
   CORE_VERSION=v5.15
   WEB_VERSION=v5.18.1
   FTL_VERSION=v5.20.1
   GITHUB_CORE_VERSION=v5.17.2
   GITHUB_WEB_VERSION=null
   GITHUB_FTL_VERSION=v5.23
   CORE_HASH=9048429b
   GITHUB_CORE_HASH=60b6a101
   WEB_HASH=30668d4d
   GITHUB_WEB_HASH=be05b0f6
   FTL_HASH=47128aaf
   GITHUB_FTL_HASH=1a114133
   DOCKER_VERSION=2023.11.0
   GITHUB_DOCKER_VERSION=2023.11.0

What is also strange is the already taken port

2023-11-28 04:14:46.891 4249M] Successfully accessed setupVars.conf
   [2023-11-28 04:14:46.893 4249M] FATAL ERROR in dnsmasq core: failed to create listening socket for port 53: Address already in use
   [2023-11-28 04:14:46.915 4249M] ########## FTL terminated after 107ms  (code 1)! ##########

There is no way to downgrade the components within the container so I suspect an issue with Portainer. How did you upgrade the image to the latest version? Did you remove the container completely?

[gh0sti]

This is interesting. It does not only revert the web repo, but all Pi-hole components, except the docker tag.

** [ DIAGNOSING ]: Core version

[✓] Version: v5.15

[i] Remotes: origin	https://github.com/pi-hole/pi-hole (fetch)

             origin	https://github.com/pi-hole/pi-hole (push)

[i] Branch: master

[i] Commit: v5.15-0-g9048429b



*** [ DIAGNOSING ]: Web version

[✓] Version: v5.18.1

[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)

             origin	https://github.com/pi-hole/AdminLTE.git (push)

[i] Branch: master

[i] Commit: v5.18.1-0-g30668d4d



*** [ DIAGNOSING ]: FTL version

[✓] Version: v5.20.1

[i] Branch: master

[i] Commit: 47128aaf



rw-r--r-- 1 www-data pi 379 Dec 30 14:21 /etc/pihole/versions

   CORE_BRANCH=master

   WEB_BRANCH=master

   FTL_BRANCH=master

   CORE_VERSION=v5.15

   WEB_VERSION=v5.18.1

   FTL_VERSION=v5.20.1

   GITHUB_CORE_VERSION=v5.17.2

   GITHUB_WEB_VERSION=null

   GITHUB_FTL_VERSION=v5.23

   CORE_HASH=9048429b

   GITHUB_CORE_HASH=60b6a101

   WEB_HASH=30668d4d

   GITHUB_WEB_HASH=be05b0f6

   FTL_HASH=47128aaf

   GITHUB_FTL_HASH=1a114133

   DOCKER_VERSION=2023.11.0

   GITHUB_DOCKER_VERSION=2023.11.0

What is also strange is the already taken port

2023-11-28 04:14:46.891 4249M] Successfully accessed setupVars.conf

   [2023-11-28 04:14:46.893 4249M] FATAL ERROR in dnsmasq core: failed to create listening socket for port 53: Address already in use

   [2023-11-28 04:14:46.915 4249M] ########## FTL terminated after 107ms  (code 1)! ##########

There is no way to downgrade the components within the container so I suspect an issue with Portainer. How did you upgrade the image to the latest version? Did you remove the container completely?

I use watchtower to do any updates when a new container comes out. I actually have a pi5 that I want to image up on 64bit Debian and set up portainer on that with watchtower.

[rdwebdesign]

What is also strange is the already taken port

2023-11-28 04:14:46.891 4249M] Successfully accessed setupVars.conf
   [2023-11-28 04:14:46.893 4249M] FATAL ERROR in dnsmasq core: failed to create listening socket for port 53: Address already in use
   [2023-11-28 04:14:46.915 4249M] ########## FTL terminated after 107ms  (code 1)! ##########

This log is from a month ago (2023-11-28).

Apparently this container is using volumes (even for the logs) and something is overwriting volumes content with older versions of the files.

@gh0sti

Did you configure volumes for this container? Can you please post the compose file or docker run
command used to start the container?

I just noticed your original comment has a compose file.

[gh0sti]

What is also strange is the already taken port

2023-11-28 04:14:46.891 4249M] Successfully accessed setupVars.conf
   [2023-11-28 04:14:46.893 4249M] FATAL ERROR in dnsmasq core: failed to create listening socket for port 53: Address already in use
   [2023-11-28 04:14:46.915 4249M] ########## FTL terminated after 107ms  (code 1)! ##########

This log is from a month ago (2023-11-28).

Apparently this container is using volumes (even for the logs) and something is overwriting volumes content with older versions of the files.

@gh0sti

Did you configure volumes for this container? Can you please post the compose file or docker run command used to start the container?

I just noticed your original comment has a compose file.

Is there anything else I should try before I just switch over to using my Pi5 I got and setting up brand new?

[rdwebdesign]

I don't have a suggestion, because I have no idea how the container files are reverting to previous versions. Apparently even the logs are older files.

As a test, you can try to recreate the container using Portainer interface (stop the stack to remove the container and start it again), create a debug log with the initial state and later (when the issue happens again) you create a second debug log, for comparison.

[gh0sti]

I don't have a suggestion, because I have no idea how the container files are reverting to previous versions. Apparently even the logs are older files.

As a test, you can try to recreate the container using Portainer interface (stop the stack to remove the container and start it again), create a debug log with the initial state and later (when the issue happens again) you create a second debug log, for comparison.

I finished setting up my pi5 with portainer and using this container and it auto updated just fine with watchtower to the latest version and shows current versions. Probably my pi4 container is corrupted and I will be decommissioning it and just using my pi5 going forward. For now I will close this if it happens again on my pi5 I'll bring up more logs.

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/update-error/68973/2