Trying to determine why hlstube quit streaming and returned a 500 Internal Server Error.
Is it a problem with hlstube, or something wrong with youtube.
After streaming the site for about 58 minutes, Channels DVR log says Could not fetch playlist get returned 500 Internal Server Error
Nothing in the hlstube docker container log, other than it stopped reporting streaming https://www.youtube.com/... to <IP>:<PORT> about 36 seconds before Channels DVR logged the 500 error.
This happened once last night and it's been working fine since then.
It has happened a few times in the previous months, so I setup a task a few weeks ago to restart the container every morning.
Any ideas?
Noticed something else in the hlstube container log from three days ago, but it didn't seem to affect that stream.
reconfiguring https://www.youtube.com/...
asking <IP>:<PORT> to retry
Don't know what that means or if it's related to the 500 error I got yesterday, but it's the same site.
Still haven't found the root cause, but according to my router wan dhcp client log, my router lost its network link to my gateway. So the Internet connection dropped for about 3 minutes, resulting in the 500 error. hlstube lost its Internet access.
Trying to troubleshoot why Channels DVR thinks the hlstube stream is not available.
Usually have no issues, but once in awhile this happens.
Channels DVR log shows 138 retry attempts by Channels DVR to stream failing with the same error for 6 minutes, 55 seconds after it started.
2023/03/03 18:59:00.004821 [DVR] Starting job 1677898740-614 TheChannel @ 7PM on ch=[3777]
2023/03/03 18:59:01.070056 [ERR] Failed to start stream on channel 3777 via M3U-TheChannel: M3U: Stream Not Available
... 137 identical failures
2023/03/03 19:05:55.834968 [ERR] Failed to start stream on channel 3777 via M3U-TheChannel: M3U: Stream Not Available
The job never recorded anything.
All that time the hlstube docker log shows it streaming to Channels DVR, with the port# for Channels DVR changing after every 2 lines.
I'm assuming this is because each time Channels DVR retried streaming it used a new port.
2023-03-04T02:59:01.023988788Z stderr 2023/03/03 18:59:01 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:42734
2023-03-04T02:59:01.066539680Z stderr 2023/03/03 18:59:01 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:42734
2023-03-04T02:59:02.161636361Z stderr 2023/03/03 18:59:02 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:42740
2023-03-04T02:59:02.205658224Z stderr 2023/03/03 18:59:02 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:42740
... identical log lines with just time and port# changing
2023-03-04T03:05:49.934834778Z stderr 2023/03/03 19:05:49 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:43336
2023-03-04T03:05:49.977813530Z stderr 2023/03/03 19:05:49 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:43336
2023-03-04T03:05:55.789466487Z stderr 2023/03/03 19:05:55 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:43342
2023-03-04T03:05:55.831966647Z stderr 2023/03/03 19:05:55 streaming https://www.youtube.com/@TheChannel/live to 172.18.0.1:43342
Also, not sure what this means in the hlstube docker log that occurred on the same channel about 4 hours before the above failure.
