Master branch FPP update failing. Over and Over and Over...

[k6ccc]

Attempting to update both of my PocketBeagle FPP instances today results in the update failing.  Results in the FPPD not found - Rebuild needed  with a button to rebuild.  Trying the rebuild results in the same thing.  Multisync page shows the 399 seen below and the local and GitHub version as the same (did not before first attempt):

FPP-PB-P10 PocketBeagle running P10 matrix

192.168.131.81

BeagleBone Black PocketBeagle

Remote

Idle

FPP: 8.x-341 OS: v2023-12

Local: [color=rgba(var(--bs-link-color-rgb), var(--bs-link-opacity, 1))]3e55e38[/color][/font][/size] Remote: 3e55e38 Branch: master

From:   v8.x-master-341-gdf8567be (master branch)
To:   v8.x-master-399-g3e55e384 (master branch)

This below on the first rebuild attempt:
Pulling in updates...
Upgrading git revision from branch master
Already up to date.
Checking config version
FPP Version: 202312
Config Version: 89
Up to date at config version 89
in Clean stage
Building FPP on 'BeagleBone Black' platform

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upgrade FAILED.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[k6ccc]

Multiple Rebuilds, restarts, reboots, shutdown & power cycles have not helped.  Anything besides pull the µSD card and re-image?

[k6ccc]

upgrade_config.log for today if this helps:

[pre][color=#171720][size=2][font=Verdana, Arial, Helvetica, sans-serif]Fri 02 Aug 2024 01:57:23 PM PDT
Checking config version
FPP Version: 202312
Config Version: 87
Upgrading config to version 88
Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:2 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]
Get:5 https://repos.rcn-ee.com/debian bullseye InRelease [3,077 B]
Get:6 http://security.debian.org/debian-security bullseye-security/main armhf Packages [276 kB]
Get:7 http://deb.debian.org/debian bullseye/main armhf Packages [7,840 kB]
Get:8 http://deb.debian.org/debian bullseye/non-free armhf Packages [56.0 kB]
Get:9 http://deb.debian.org/debian bullseye-backports/contrib Sources [5,000 B]
Get:10 http://deb.debian.org/debian bullseye-backports/main Sources [376 kB]
Get:11 http://deb.debian.org/debian bullseye-backports/non-free Sources [5,032 B]
Get:12 http://deb.debian.org/debian bullseye-backports/main armhf Packages [396 kB]
Get:13 http://deb.debian.org/debian bullseye-backports/non-free armhf Packages [8,872 B]
Get:14 https://repos.rcn-ee.com/debian bullseye/main armhf Packages [1,363 kB]
Fetched 10.6 MB in 20s (517 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libkms++-dev
E: Couldn't find any package by regex 'libkms++-dev'
>>SUCCESS upgraded to config version 88
Upgrading config to version 89
>>SUCCESS upgraded to config version 89
Up to date at config version 89
==========================================================================
Fri 02 Aug 2024 02:07:23 PM PDT
Checking config version
FPP Version: 202312
Config Version: 89
Up to date at config version 89
==========================================================================
Fri 02 Aug 2024 02:17:25 PM PDT
Checking config version
FPP Version: 202312
Config Version: 89
Up to date at config version 89
==========================================================================
Fri 02 Aug 2024 02:23:50 PM PDT
Checking config version
FPP Version: 202312
Config Version: 89
Up to date at config version 89
==========================================================================
Fri 02 Aug 2024 02:32:04 PM PDT
Checking config version
FPP Version: 202312
Config Version: 89
Up to date at config version 89[/font][/size][/color][/pre]

[k6ccc]

This is one of them as while later...

Version Info
FPP Version:	8.x-master-399-g3e55e384
Platform:	BeagleBone Black (PocketBeagle)
FPP OS Build:	v2023-12
OS Version:	Debian GNU/Linux 11 (bullseye)
Hardware Serial Number:	1744GPB50414
Kernel Version:	5.10.168-fpp
System Boot Time:	2024-08-02 14:27:18
fppd Uptime:
Local Git Version:	3e55e38 [color=rgba(var(--bs-link-color-rgb), var(--bs-link-opacity, 1))]ChangeLog[/font][/size][/color]
Remote Git Version:	3e55e38
Upgrade FPP:
FPP Upgrade Source:	[color=var(--bs-body-color)] github.com [/font][/size][/color]
Upgrade OS:	-- Choose an OS Version -- BBB-v4.6.fppos (download)BBB-v4.5.fppos (download)BBB-v4.4.fppos (download)BBB-v4.3.fppos (download)BBB-v4.3.1.fppos (download)BBB-v4.2.fppos (download)BBB-v4.1.fppos (download)BBB-v4.0.fppos (download)BBB-8.0-pre-alpha4_2024-04.fppos (download)BBB-8.0-beta1_2024-07.fppos (download)BBB-8.0-alpha5_2024-06.fppos (download)BBB-7.5_2023-12.fppos (download)BBB-7.4_2023-12.fppos (download)BBB-7.3.1_2023-11.fppos (download)BBB-7.2_2023-08.fppos (download)BBB-7.1_2023-08.fppos (download)BBB-7.0_2023-07.fppos (download)BBB-7.0-beta1_2023-06.fppos (download)BBB-7.0-alpha1_2023-04b.fppos (download)BBB-7.0-alpha1_2023-04.fppos (download)BBB-6.3.fppos (download)BBB-6.2.fppos (download)BBB-6.1.fppos (download)BBB-6.0.fppos (download)BBB-6.0.2.fppos (download)BBB-6.0-beta1.fppos (download)BBB-5.5.fppos (download)BBB-5.4.fppos (download)BBB-5.4.1.fppos (download)BBB-5.3.fppos (download)BBB-5.2.fppos (download)BBB-5.1.fppos (download)BBB-5.0.fppos (download)BBB-5.0.1.fppos (download)BBB-5.0-alpha1.fppos (download)BBB-4.0-beta2.fppos (download)BBB-4.0-beta1.fppos (download)BBB-4.0-alpha4.fppos (download)BBB-4.0-alpha3.fppos (download)  Show All Platforms   Preserve /opt/fpp
System Utilization
CPU Usage:	53.93%
Memory Usage:	18.41%
Sensors:
Uptime
15:06:31 up 39 min, load average: 0.00, 0.00, 0.06

[darylc]

reimage with beta 1, master is not designed to work with the previous alpha images.

[k6ccc]

reimage with beta 1, master is not designed to work with the previous alpha images.

The re-image part I understand, but not sure what you mean by the rest.  Last season I was running 7.something.  When 8 came out it was initially upgraded (presumably via switching to the Master branch), then updated from there.  Did I miss something?

[k6ccc]

I just re-imaged both FPP instances to 7.5 for now...

[darylc]

You can't just switch master branch to get from 7.5 to 8, you need to do a fppos upgrade, or reimage.  See in your post it says "OS:   v2023-12"  It should be saying v2024-07" or similar if you did the upgrade properly.

[k6ccc]

You can't just switch master branch to get from 7.5 to 8, you need to do a fppos upgrade, or reimage.  See in your post it says "OS: v2023-12"  It should be saying v2024-07" or similar if you did the upgrade properly.

I'll have to take your word on that one.  I have NEVER heard that before, and have used Master branch every summer for around 7 years.  As far as I can find, there is no FPPOS or image for Master branch.  Maybe it's well hidden on GitHub - which navigating that might as well be in Greek.

[Poporacer]

I have NEVER heard that before, and have used Master branch every summer for around 7 years

It has been mentioned many times, but maybe not documented well enough. Switching to the Master branch will only update the FPP version and not the OS version as mentioned. The only way the OS version can get updated is through a new image of an fppos upgrade. But, based on what you posted, you had to have either reimaged or used the fppos upgrade late last year.

As far as I can find, there is no FPPOS or image for Master branch.

The Master branch is the working branch for the currently "under development" branch and will typically be switched over to the current major release with an announcement and fppos and image files. Almost every major branch change (7.x to 8.x) will require an OS upgrade.

Maybe it's well hidden on GitHub - which navigating that might as well be in Greek.

It isn't really hidden or in Greek, but maybe the documentation isn't clear. But a FYI every fppos upgrade version will have a tag to indicate what is the associated OS version for that FPP version. For example:
You cannot view this attachment.
Show that v8 Alpha 4 uses OS version 2024-04 and v8 Beta1 uses OS Version 2024-07.
If you are running in the Master Branch, sometimes you have to pay attention to these significant releases to make sure you are on the correct OS version.

We do appreciate people like you that put in the time to help test out the functionality so bugs can fixed before the actual release is made and it helps a lot!

[k6ccc]

Show that v8 Alpha 4 uses OS version 2024-04 and v8 Beta1 uses OS Version 2024-07.
If you are running in the Master Branch, sometimes you have to pay attention to these significant releases to make sure you are on the correct OS version.

You are right that it is not well documented.  But where do you find that information?  Remember that GitHub might as well be written in Greek (unless you are a developer).

[Poporacer]

But where do you find that information?

I am not sure what information you are referring to, but here is the Releases section that shows the OS level information and it has been the same for several years.
You cannot view this attachment.

[k6ccc]

And WHERE IS THAT ?

Remember for people who are not familiar with navigating GitHub, it might as well be written in Greek.  Same issue for something else I deal with where the development is on GitHub and the standard answer is "it's on GitHub".  Hundreds of directories that have names in many cases that are meaningless if you are not involved.  I have tried to guess based on posted links and almost always just get a 404 error.
I am looking at the fpp section on GitHub right now and there is no "Releases" section (I assume it should be a folder).

[Poporacer]

And WHERE IS THAT ?

It is right on the Releases page. That is where you would have gone to get the image if you were re-imaging the card. It is also explained in the FPP Manual (probably not explained very well though) The Manual explains that the OS needs to be the appropriate version for the FPP version. (but probably not very clear.

You cannot view this attachment.

I am looking at the fpp section on GitHub right now and there is no "Releases" section (I assume it should be a folder).

It is right on the front page. No, it won't be in a folder since the folders are the actual development files that get installed onto the SD card. It is here:

You cannot view this attachment.

And there is a link to the page in the FPP Manual.

You cannot view this attachment.

I hope this helps you and others in the future.

[jnealand]

@k6ccc  This is the bookmark that I have when I am looking for releases.  Just scroll down to see what you want.
https://github.com/FalconChristmas/fpp/releases  Click on the word assets if no releases are listed.