Channel Loops

Channels DVR Server
#32

I've noticed that there is one of these lines in the recording log corresponding to each loop:

at=2020-05-30T17:12:59.0193765-07:00 tag="cnn" action="fetch" url="https://turnerlive.akamaized.net/hls/live/586495/cnngo/cnn_slate/VIDEO_0_3564000/1586934423_set_333/VIDEO_0_3564000_666705.ts?hdntl=exp=1590912450~acl=%2Fhls%2Flive%2F*~hmac=fa809e4324c1cb718156ba08495aaecc0ab6caf720c0c9e6baedc66def6f8b20" content_length=2860800 duration=6.006 encrypted=true failed="temporary" failed_while="reading" err="unexpected EOF" body_time="7.5923429s" time="7.6283504s" status="segmentTemporarilyFailed"

So, if a 3 second clip repeats once, then one entry. If it repeats three times, then three of these segmentTemporarilyFailed entries in a row.

1 Like
#33

Everything seemed fixed to me, but last night I had a couple of instances of CNN looping again.

#34

Please press-and-hold on the Check For Updates button in the Settings page of your DVR. I've added additional logging that may shed some light on what is going wrong.

#35

2020.05.31.2323 installed.

#36

Installed. If it occurs again, I'll send a log your way. Thanks for the effort!

#37

I was watching Rick and Morty, looped about 5 times. Logs are below and submitted through the app on my Tivo 4K Stream. Logs were taken right after it occurred.

ca4cdb53-ae6a-4ae1-9828-e91befb31201

#38

Thanks for the diagnostics. That does help to confirm what we were thinking. The way we are truncating the file on an error is not working properly on Windows.

I'll let you know when we have a fix.

#39

Glad I could be of some help! As always, thanks for the quick response!

#40

I’ve just released another build that should fix this issue. Differences between how Linux and Windows handle file access was causing the system to not clear out files that had failed to download and needed to be re-downloaded.

#41

3 posts were split to a new topic: Storage of recording logs for TVE recordings

#44

I'd like to report that the fix is in, but CNN Go is apparently broken. Hopefully that's a coincidence! ;-()

#45

Looks like other people are running into it:

#46

That appears to be fixed now.

This is so typical - reminds me of work; you sweat bullets to find and fix a bug in the code, then when you go to push it to the server, you discover that they have somehow changed the permissions. Then you start troubleshooting the permissions problem, and when you find the culprit, the server stops responding altogether. Then your phone starts ringing... oh my interrupted interruptions...

#47

I'm glad to hear the looping appears to be fixed. For the most part we've been able to ignore the differences between Linux and Windows, but occasionally things crop up that relate to the fundamental differences of how they manage some system interactions and it is very difficult to identify.

2 Likes
#48

I've already seen the "segmentTemporarilyFailed" error without a corresponding loop. Looking good!

2 Likes
#49

Had zero complaints from the family about any looping. Thanks for the fix.

1 Like
#50

Hi, I'm curious if you've seen any segmentTemporarilyFailed on CNN recently and if so can you share those log messages.

#51

What is the location of the full current and previous log files in Windows?

#52

All the log files are in c:\programdata\channelsdvr\data they'll be labelled hls-*.log

#53

There have been a few. I submitted diagnostic logs from the server ( 01d07029-d37e-4a42-afac-b261d9ed2bc8), and attached all of the his-*.log files in a .zip to the support mailbox.

1 Like