Did the the latest upgrade tonight and it failed.

[MikeKrebs]

ccache g++ -shared  channeloutput/MQTTOutput.o -L. -lfpp -ljsoncpp -lrt -lpthread  -o libfpp-co-MQTTOutput.so
ccache g++ -shared  channeloutput/PCA9685.o -L. -lfpp -ljsoncpp -lfpp_capeutils  -Wl,-rpath=/opt/fpp/src/:. -lrt -lpthread  -o libfpp-co-PCA9685.so
/usr/bin/ld: cannot find -lfpp_capeutils: No such file or directory
collect2: error: ld returned 1 exit status
make: *** [/opt/fpp/src//makefiles/libfpp-co-PCA9685.mk:8: libfpp-co-PCA9685.so] Error 1
make: *** Waiting for unfinished jobs....
----------------------
Elapsed Time: 00:01:00
==========================================================================
Restarting fppd...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upgrade FAILED.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Had to "rebuild" which appears to have worked.

FPP Version:	8.x-master-292-g4ebd4168
Platform:	Raspberry Pi (Pi 3 Model B)
FPP OS Build:	v2024-03
OS Version:	Raspbian GNU/Linux 12 (bookworm)
Hardware Serial Number:	00000000f08f3424
Kernel Version:	6.6.21-v7+
System Boot Time:	2024-05-18 22:17:33
fppd Uptime:	00:56
Local Git Version:	4ebd416 ChangeLog
Remote Git Version:	4ebd416

 

[JonB256]

Both of mine that I leave online failed (Master branch update).
Had to use the Rebuild button offered on both. Acting fine now. Very fast rebuild.
Spent zero time troubleshooting, though. Just did the rebuild.

[JerryPlak]

Same Here Had to use the Rebuild button.

[k6ccc]

Read this and figured I would try.  It worked normally.

Started with:
Version Info
FPP Version:             8.x-master-290-g429970c2-dirty
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-06-14 08:11:57
fppd Uptime:             01:22
Local Git Version:       429970c ChangeLog (Update is available)
Remote Git Version:      17b32a2 Preview Changes


Ended up with FPP Version: 8.x-master-302-g17b32a21-dirty

[Poporacer]

Ended up with FPP Version: 8.x-master-302-g17b32a21-dirty

the -dirty flag usually indicates that there was an internal file that was modified outside of the normal upgrade process. Installing an upgrade will not usually fix this. The internal file needs to be fixed first before the device will upgrade properly.

[k6ccc]

I wonder if that is a leftover from a recovery I had to do when I went from 7x to 8x a few weeks ago.
Just looked, only the P10 matrix had the dirty flag.  P5 did not.
Any idea how find the issue?  Or just re-image it?  Yes, I have backups.

[Poporacer]

Any idea how find the issue?

I don't know how to find the issue

Or just re-image it?

You probably do not need to re-image it. Go to FPP Settings and change your UI>User Interface Level to Developer and then go to the Developer tab and click on the Reset Local Changes. This should get rid of the -dirty flag and set it to a clean state.

[k6ccc]

Go to FPP Settings and change your UI>User Interface Level to Developer and then go to the Developer tab and click on the Reset Local Changes. This should get rid of the -dirty flag and set it to a clean state.

I already was on Developer, so did the "Reset Local Changes".  That did not help, but it did note that I was two commits behind (since yesterday - them developers keep busy!).  So I did an update from the MultiSync page on both PocketBeagles.  That gave the advantage that I could see any difference between the two updating.  Sure enough, the P-10 that had the dirty flag took 47 seconds longer to do the update (1:37 vs 2:24).  After the update, now the dirty flag is removed on the P-10.

I am seeing something odd, but I will start a new thread.