tfabris / CrowCam

A set of Bash scripts to control and maintain a YouTube live cam from a Synology NAS.
GNU General Public License v3.0
4 stars 3 forks source link

KeepAlive doesn't seem to be working, 2019-06-09 #39

Closed tfabris closed 5 years ago

tfabris commented 5 years ago

Nothing unusual is in the logs, but the DVR feed is jumping around, and the times where it jumps seems to be related to when I logged in to watch the stream. In other words, the gaps in the DVR stream are in areas before I watched the stream, and then it starts DVR'ing again at the moments I watched the stream. Two jumps I know about in the DVR stream are:

2019-06-09 - Jump from 1:53pm (about 30-40 mins after the midday bounce) to 3:29 pm (a time when I tried to log in and look at the stream on YouTube). 2019-06-09 - Jump from 3:55 pm (about 30 mins after that last look) to 4:10pm (when I logged on again).

I won't know until I review the full archive tomorrow, but I suspect the archive will look fine and only the DVR will have had the jumps in it.

I think that YouTube-DL might not be working correctly again. Check it when you get a chance.

tfabris commented 5 years ago

On the morning of 2019-06-10 it all seemed to be working fine, no repeat of the problem. Stream DVR history was visible from 5am to 10am (more than four hours!).

Checked YouTube-DL versioning, and its last release on its download page was 2019-06-08, though I can't tell what time of day or what timezone. This indicates to me that, unless their actual file releases lag behind their versioning, then this wasn't a case of YouTube-DL malfunctioning and needing to be updated.

Checked video archive of the video on 2019-06-09 and the results were what I expected to see: Both places which had a "jump" in the DVR were fine in the archive. So this is definitely a case of the DVR keep-alive being needed yet failing to succeed at its job on this particular day/time.

To do:

tfabris commented 5 years ago

Looked at the logs again (attached). I see:

Closing this bug as "cannot reproduce".

Logs: 2019-06-09 Logs.txt