Not a major issue, but a recording job for a locast channel could not start (locast issue, which I have contacted them about),. This is fine, but the job kept trying to start even 2 hours after it began (well after them program would have ended).
The logs are full of entries like:
2020/12/15 10:59:25.122378 [DVR] Starting job 1608055200-17 Rachael Ray on ch=[5920]
2020/12/15 10:59:25.495606 [ERR] Failed to start stream on channel 5920 via LOCAST-819: Locast: get: https://xxxxxx
2020/12/15 10:59:25.495728 [DVR] Error running job 1608055200-17 Rachael Ray: could not start stream on channels=[5920]: Locast: get: https://xxxx
(I truncated the url's here, as it doesn't matter for this issue).
These were repeated over and over in the logs until I manually killed the recording.
Could you maybe setup to recognize when such failures occur AND the current time is past the expected run time of the recording to auto-end these attempts?
Again, not a major issue (and the actual issue is with Locast), but would be nice not having these hung like this (and fill logs)?
Keep up the great work!