Problem with "pihole updatechecker local"

Help
1

Expected Behaviour:

Pi-Hole should be updating

Actual Behaviour:

I did two new installs of Pi-Hole, one yesterday, one today. Now every 10 minutes the cron daemon sends an email with subject "Cron root@rpi-pihole PATH="$PATH:/usr/local/bin/" pihole updatechecker local" and body "fatal: Keine Namen gefunden, kann nichts beschreiben.
fatal: Keine Namen gefunden, kann nichts beschreiben."
Running "sudo pihole updatechecker local" gives the same two lines of "fatal: Keine Namen gefunden, kann nichts beschreiben.
fatal: Keine Namen gefunden, kann nichts beschreiben."

From what I got so far it seems to be a problem in git, Pi-Hole itself is running fine.

Debug Token:

[✓] Your debug token is: https://tricorder.pi-hole.net/x29yfml4se!

2

This is indeed not very helpful...

You are probably right. What is the output of the three comands

cd /etc.pihole && git status
cd /var/www/html/admin && git status
pihole-FTL version

?

3 
pi@rpi-pihole:/ $ cd /etc/.pihole && git status
Auf Branch master
Ihr Branch ist auf dem selben Stand wie 'origin/master'.
nichts zu committen, Arbeitsverzeichnis unverändert
pi@rpi-pihole:/etc/.pihole $ cd /var/www/html/admin && git status
Auf Branch master
Ihr Branch ist auf dem selben Stand wie 'origin/master'.
nichts zu committen, Arbeitsverzeichnis unverändert
pi@rpi-pihole:/var/www/html/admin $ pihole-FTL version
v4.2.3
pi@rpi-pihole:/var/www/html/admin $ pihole -v
  Pi-hole version is Untagged (Latest: v4.2.2)
  AdminLTE version is Untagged (Latest: v4.2)
  FTL version is v4.2.3 (Latest: v4.2.3)

I added a "pihole -v" since I found it odd, that the first two entries say "untagged". Is it supposed to be this way?

German locale, output of the two status commands is "On branch master / Your branch is on same status as 'origin/master'. Nothing to commit, work directory unchanged".

4

It is not supposed to be this way, however, it currently is like this. So your installation is okay.

The reason for this is buried deeply down into git and will be fixed by the next release we hope to get out until next weekend. It is basically done, just awaiting final testing by the core developers which have, unfortunately, been super busy the last days.

5

Thanks. Would this fix my problem with the cron job / updatechecker?

6

Yes, everything will be back in order once we release v4.3 and you update to this version.

2 Likes
7

Thanks again!

8

Any news on this? It has been a while and the emails keep pouring in.

Thanks.

9

A possible solution found on reddit , read here …

10

That worked. Thanks.

11

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