Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to upgrade player firmware

See original GitHub issue

Issue Description

I am running the latest version of open source server though docker-compose.

It shows as version hash: 85008a, Aug 4 2021

I have a test Pi4 client currently running ver: 2.9.8/buster_10.8_admin_2021-02-25

If I press the upgrade button it shows a dialogue “Do you want to update Software from 2.9.8 to” with no version to upgrade to. Pressing OK shows the upgrading screen on the player display, but it reboots into the same version.

I can see that the player is requesting the file “/releases/piimageundefined-v14.zip”.

Looking in the docker volume I can see a number of release files:

-rw-r--r-- 1 root root     711 Aug 21 01:00 package.json
-rw-r--r-- 1 root root 3778087 Jul  9 10:46 piimage2.9.9-v14.zip
-rw-r--r-- 1 root root 3778088 Jul  9 10:46 piimage2.9.9-v6.zip
-rw-r--r-- 1 root root 3778028 Jul  9 10:46 piimage2.9.9.zip
lrwxrwxrwx 1 root root      34 Jul  9 10:46 piimage2-v6.zip -> /data/releases/piimage2.9.9-v6.zip
-rw-r--r-- 1 root root 3778394 Jul 22 01:00 piimage3.0.0-v14.zip
-rw-r--r-- 1 root root 3778393 Jul 22 01:00 piimage3.0.0-v6.zip
-rw-r--r-- 1 root root 3778333 Jul 22 01:00 piimage3.0.0.zip
-rw-r--r-- 1 root root 3778409 Jul 23 01:00 piimage3.0.1-v14.zip
-rw-r--r-- 1 root root 3778406 Jul 23 01:00 piimage3.0.1-v6.zip
-rw-r--r-- 1 root root 3778347 Jul 23 01:00 piimage3.0.1.zip
-rw-r--r-- 1 root root 3778443 Jul 27 01:00 piimage3.0.2-v14.zip
-rw-r--r-- 1 root root 3778440 Jul 27 01:00 piimage3.0.2-v6.zip
-rw-r--r-- 1 root root 3778380 Jul 27 01:00 piimage3.0.2.zip
-rw-r--r-- 1 root root 3778419 Jul 28 01:00 piimage3.0.3-v14.zip
-rw-r--r-- 1 root root 3778420 Jul 28 01:00 piimage3.0.3-v6.zip
-rw-r--r-- 1 root root 3778360 Jul 28 01:00 piimage3.0.3.zip
-rw-r--r-- 1 root root 3779129 Aug 21 01:00 piimage3.0.4-v14.zip
-rw-r--r-- 1 root root 3779127 Aug 21 01:00 piimage3.0.4-v6.zip
-rw-r--r-- 1 root root 3779068 Aug 21 01:00 piimage3.0.4.zip
lrwxrwxrwx 1 root root      34 Aug 21 01:00 piimage3-v6.zip -> /data/releases/piimage3.0.4-v6.zip
lrwxrwxrwx 1 root root      35 Aug 21 01:00 pi-image-v14.zip -> /data/releases/piimage3.0.4-v14.zip
lrwxrwxrwx 1 root root      34 Aug 21 01:00 pi-image-v6.zip -> /data/releases/piimage3.0.4-v6.zip
lrwxrwxrwx 1 root root      31 Aug 21 01:00 pi-image.zip -> /data/releases/piimage3.0.4.zip
-rw-r--r-- 1 root root     711 Sep 10 11:28 server-package.json

I have tried to issue an upgrade command via the api without a version string and it fails in the same way (it looks like it should be picking up the version from a config file), but if I set explicitly set the version to piimage3.0.4.zip it will happily download /releases/piimage3.0.4-v14.zip and perform the upgrade.

Issue Analytics

State:
Created a year ago
Comments:12

Top GitHub Comments

1reaction

udo1tonicommented, Apr 2, 2022

My bad. I guess I had a typo in my posting, path should be /pisignage-server/data/ so please try ln -s /data/releases/ /pisignage-server/data/releases (but first move all files from /pisignage-server/data/releases to /data/releases/ and remove /pisignage-server/data/releases/

0reactions

tamahau30494commented, May 10, 2022

I am now getting the exact messages in my log as @vectisventuresltd after converting my install from native to Docker. The Symlink did not work for me either.