co-universes.json does not exist keeps showin up in log

[eatumup]

Im having an issue where FFPD keeps stopping. So far I havent found anything that stands out to me as to why. One suggestion was to review the ffpd.log file. In there I keep seeing

JSON File /home/fpp/media/config/co-universes.json does not exist

So im wondering if maybe its causing FFPD to crash/stop as I have seen a previous post suggesting to make sure the controller is only looking for things that are actually plugged in.

Does anyone know if I should be concerned about this and how to fix it? My system is just a beagle black with a kulp 16-a. Im not running any remote units. everything direct from the hat.

[Poporacer]

So im wondering if maybe its causing FFPD to crash/stop

That by itself wouldn't cause FPP to crash. Do you have any "other" outputs configured like Virtual Matrix?

Does anyone know if I should be concerned about this and how to fix it?

No, you shouldn't be concerned about it. But with almost no information as to what is going on, we can't start to tell you where to look.

What about the FPP Version and OS Version?
What does "FPPD keep Stopping" mean? 
What is happening when this happens?
Does it stop and then come back on by itself, or do you have to restart it?
Does it stop on a regular basis?
Can you watch it and see what time it stops and then wait a couple minutes and then download the fppd.log and attach it and tell us what time it stopped

[eatumup]

I dont have a virtual matrix on it. But i might have found a reference to remote pie I used to have on the system. I got rid of that.  Much appreciated for your input there. 

For your other questions, FFPD just shows stopped with the big red bar showing abnormal conditions. 

The system is on debian BBB 2024-09 fpp 8.1. 
When it does this I have to restart it manually or even full power cycle as sometimes the web client gets hung up. The system does power off nightly. 

Looking at fppd.log powered on tonight at 4:56. It then boots and starts the hour long sequence that is on repeat. 5 minutes later fppd shows main loop compete, shutting down.

Yesterday I installed fppdwatcher to try to keep it running. Ultimately i guess that did not work, but I think fppd watcher kicked in and restarted fppd as the boot log begins right away. then im not sure whats happening.  In the code snippet below you can see the time jump from 17:05 to 19:12. The logs at 19:12 is my manual interaction when I checked on it.

2024-10-09 17:05:18.594 (2520) [Command] /opt/fpp/src/command.cpp:70: Initializing Command Module
2024-10-09 17:05:18.597 (2520) [E131Bridge] /opt/fpp/src/e131bridge.cpp:316: Universe Count = 0
2024-10-09 17:05:18.712 (2520) [General] /opt/fpp/src/fppd.cpp:893: Starting main processing loop
2024-10-09 17:05:59.504 (2520) [General] /opt/fpp/src/fppd.cpp:1092: Not Publishing statistics as mode is 'Disabled'
2024-10-09 19:12:35.300 (2520) [General] /opt/fpp/src/fppd.cpp:1024: Stopping channel output thread.
2024-10-09 19:12:35.452 (2520) [General] /opt/fpp/src/fppd.cpp:1028: Main Loop complete, shutting down.
2024-10-09 19:12:35.680 (2520) [General] /opt/fpp/src/fppd.cpp:785: Performing Restart.
2024-10-09 19:12:38.912 (2520) [General] /opt/fpp/src/log.cpp:353: =========================================
2024-10-09 19:12:38.912 (2520) [General] /opt/fpp/src/log.cpp:354: FPP 8.1
2024-10-09 19:12:38.913 (2520) [General] /opt/fpp/src/log.cpp:355: Branch: v8.1
2024-10-09 19:12:38.913 (2520) [General] /opt/fpp/src/log.cpp:367: Model: TI AM335x BeagleBone Black
2024-10-09 19:12:38.913 (2520) [General] /opt/fpp/src/log.cpp:371: =========================================

Any advice you have would be most appreciated. im not sure what to do at this point. 

[Poporacer]

The system is on debian BBB 2024-09 fpp 8.1.

The correct OS version for 8.1 is 2024-10, not sure if that would cause any issues.

[MikeKrebs]

I try to get back to basic, clean setup. Start by taking some screenshots of your config and make a backup.

Get a new SDCard and image with 2024-10. Do basic setup only. See if your BBB/FPP/K16a stays running.

After a couple of days, start adding back your configuration. If you use xLights, push the config from there. Otherwise do it manually as you did originally.

If that works okay, add your media and schedule and see if it stays up.

[eatumup]

Ill have to give that a shot. clean card, clean try.