Update visible via web config, but not via console

Expected Behaviour:

Update state identical on web config as via console

Actual Behaviour:

Web config show's that there is an update available:
update_avail

But If I connect to console and start the update, it tells me that there is no update:
console

Suspected cause:

I wanted to update pihole via SSH from a mobile Android device. But during the Update the mobile device was disconnected. Since this happened, the issue occures. I'm not sure if this is the cause and how it can be fixed.

Debug Token:

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

You are running the latest versions.

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

*** [ DIAGNOSING ]: Web version
[✓] Version: v5.20.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.20.1-0-g3a11976e

*** [ DIAGNOSING ]: FTL version
[✓] Version: v5.23
[i] Branch: master
[i] Commit: d201776e

I't only the web interface that reports it wrongly. Reason is, that your /etc/pihole/versions file is out-of-date

-rw-r--r-- 1 root root 321 May 31 00:01 /etc/pihole/versions
   CORE_BRANCH=master
   WEB_BRANCH=master
   FTL_BRANCH=master
   CORE_VERSION=v5.17.1
   WEB_VERSION=v5.19
   FTL_VERSION=v5.22
   GITHUB_CORE_VERSION=v5.17
   GITHUB_WEB_VERSION=v5.20.1
   GITHUB_FTL_VERSION=v5.23
   CORE_HASH=6a45c6a8
   GITHUB_CORE_HASH=bea63f9d
   WEB_HASH=d7f18428
   GITHUB_WEB_HASH=3a11976e
   FTL_HASH=eb197891
   GITHUB_FTL_HASH=d201776e

Please run pihole updatechecker and see if the content of that file changed.

1 Like

oh, that was easy.
Thanks a lot for the fast help! :slight_smile:

btw.: is there any way to update pihole without gravity? I mean, just update pihole, and leave all blocklists as they are?
Why do I ask: sometime I've had the case that I get blocked from vendors if update occur's too often.

1 Like

sometime I've had the case that I get blocked from vendors if update occur's too often.

Usually gravity runs only once a week and after updates.

Are you running a custom script to update gravity more often?

No, there is none. The reason is, that we might change the database schema with an update of the core repo and the gravity database needs to be rebuild to reflect the changes.

2 Likes

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.