Check for update failed

[fralippo]

On a perfectly working 8.3.8, pi4-4gb wifi, I tried to update to the latest version. But I always get the error you can see at the attachment. What could it be? Thanks.

[Tim Curtis]

No issue on my end.

Prolly an issue with your network, or maybe try clearing your Browser cache.

[fralippo]

I see.

I've noticed that the router connecting to this Pi4 has a internal Firewall function activated. Could this be the reason of the problem? Thanks.

[Tim Curtis]

Try rebooting your Router.

You can also verify that you can reach the repo containing the update zip by trying the URL below in your Browser.
https://github.com/moode-player/updates/...ode-player

[bsergiu]

Hi @fralippo , from the other issue you have, it looks very much like network devices inside the Pi network cannot go out. This is why you had to activate the BubbleUpnp Proxy, which enables the Phone in your network to act as a proxy.

I hope this helps

[springle19]

I too have the same 'Check for update failed' error when I check for a software update.

Am on moode 9.01 on a headless Raspberry 4. Install is 'vanilla', bar three added mount entries in my /etc/fstab.  Installed 3 days ago.  Previous moode installs - same pi - have updated their software without issue

Interestingly,  I get the attached/below pop-up before the system takes me back to the Software Update screen

   

As per above, have re-boooted kit (pi, routers, and the aptop from where I am SSHing), but no difference.  As per Tim's suggestion above, have tried opening https://github.com/moode-player/updates/...ode-player . . . and no problems

Two asks

(i) any pointers on where to  probe further on this

(ii) is it possibe to advance the update from the command line

Many thanks, Simon P in rainy Manchester UK

[TheOldPresbyope]

@springle19

Hi, Simon.

That suggested https: check is of limited value if you ran it from the browser on your laptop.




From the command of your moOde player can you ping the github server? E.g., get a response like this one from one of my moOde 9.0.4 players

Code:

rho@sunroom:~ $ ping -c1 github.com
PING github.com (140.82.113.4) 56(84) bytes of data.
64 bytes from lb-140-82-113-4-iad.github.com (140.82.113.4): icmp_seq=1 ttl=47 time=15.6 ms

--- github.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 15.585/15.585/15.585/0.000 ms

Assuming the ping is successful, an alternative to using moOde's webUI is to try this from the command line

Code:

sudo /var/www/util/system-updater.sh moode9

The response should begin with

Code:

Downloading package [update-moode9.zip]

**********************************************************
**
**  This process updates moOde to the latest release.
**  Reboot after the update completes.
**
**********************************************************

Start 2024-07-06 update for moOde

followed by lots of sausage making. (From memory, you might get asked at some point if you want to accept a new configuration file for bluealsa; I just hit <return> for the default action to keep the current one.)


As always, YMMV.

That screenshot you posted shows up on my systems from time to time too. Since it appears to be harmless I've not bothered to trace what is triggering it.

Regards,
Kent

ETA - PS - If the piing test is successful then the webUI check should work. If the ping test works but the webUI check doesn't then we have a dilemma on our hands.

[springle19]

Kent - thanks for the prompt, clear, and fulsome response.

My report back:

> ping to '-c1 github.com' from PI terminal comes back as 'Destination Host Unreachable'.  Subsequent PI CLI instruction 'sudo /var/www/util/system-updater.sh moode9' comes back with 'Package not found, update cancelled'.  So, we have an issue . . .

> however, ping to '-c1 github.com' from my laptop's CLI (on same home network) resolves fine. as does ping from my geriatric PiB+'s CLI.  This implies my overall network set-up is OK and talking to the right places, but the moode pi is not.

Advice on next steps?  I only installed v9.04 a couple of days ago, (and edited fstab to include a couple of mounts), so no hassle to do clean reinstall.  Maybe this is easiest to do before getting into deeper intricacies?

Best, Simon P

[Tim Curtis]

Reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

[springle19]

Tim/Kent

Another happy customer . . . scan of the log showed I had the Gateway setting erroneously as 255.255.255.0, rather 192.168.XXX.XXX.

A silly school-boy error - my apologies for taking your time. Your advice appreciated

Thanks, Simon P