Open tfabris opened 5 months ago
With checkin 1f98a91 I have reduced the number of hysteresis loops in Test_Stream from 4 to 2 and reduced the pause between tests from 15 to 7. That means that if the stream is bad, instead of waiting a whole minute to bounce it, it's now only waiting 14 seconds.
This still isn't perfect though, because the program doesn't re-query the stream throughout the entire run of the CrowCam.sh program. Instead the program currently works like this:
Checkin 1f98a91 improves the hysteresis at steps 2 and 4, but still leaves a five minute "hole" during step 3 where the stream isn't being queried at all. A worst-case scenario would look like this:
Options to fix this:
To do in the meantime:
The error seemed to recur on April 14th, so, need to continue investigating this further:
2024-04-14 18:21:10 CrowCam Controller - The streamStatus is not active. Value retrieved was: inactive.
2024-04-14 18:21:10 CrowCam Controller - The healthStatus is not good. Value retrieved was: noData.
2024-04-14 18:21:18 CrowCam Controller - The streamStatus is not active. Value retrieved was: inactive.
2024-04-14 18:21:18 CrowCam Controller - The healthStatus is not good. Value retrieved was: noData.
2024-04-14 18:21:18 CrowCam Controller - Bouncing the YouTube stream for 4 seconds, because the stream was unexpectedly down in the main code after the Test_Stream function.
2024-04-14 18:22:21 CrowCam Controller - The lifeCycleStatus is not good. Value retrieved was: complete.
2024-04-14 18:22:21 CrowCam Controller - The recordingStatus is not good. Value retrieved was: recorded.
2024-04-14 18:22:21 CrowCam Controller - The lifeCycleStatus and recordingStatus indicate that it's time to create a new livestream from scratch. Creating a new livestream now.
I observed a behavior several times on 2024-04-01 where:
Relevant log entries: