TVE TNT Connection Failures 01/09/2024

Channels DVR Server Troubleshooting
#1

Hello.

I’m increasingly getting “Connection Lost” error messages for TNT (6035 and 6036) within 5-10 minutes of initial viewing. Once this begins, the buffering and lost connection error messages begin with more frequency at shorter intervals - within 1 to 2 minutes.

I actually began noticing this about 2 weeks ago - but the holidays kept me pretty busy. I didn’t pay much attention - until last night. I performed a rescan of both TNT Channels. Both checked fine. I checked the General Troubleshooting Tab - all green. To be sure, I re-scanned the General Troubleshooting Tab - again, all green.

Other channels work fine. It seems to be isolated to TNT.

I run Channels on an Intel(R) Client Systems NUC8i5BEHS
Windows Microsoft Windows 11 Pro 10.0.22621.2861 Build 22621.2861 (kernel: 10.0.22621.2861 Build 22621.2861) CPU 8 cores / Intel(R) Core(TM) i5-8260U CPU @ 1.60GHz. My clients are 2022 Apple TV 4Ks.

Log submitted as 13f7908c-b791-410d-8832-976cf63caa48. The timeframe for the issue in question is 01/09/2024 starting around 2100. Here's that area of the log:

2024/01/09 20:32:29.786346 [TVE] stream timestamps: tntp: start_at=2024-01-09T20:22:19-06:00 end_at=2024-01-09T20:32:13-06:00 live_delay=9.9313469s
2024/01/09 20:32:29.786346 [TNR] Opened connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:00:00.001959 [DVR] Starting job 1704855600-64 Fargo on ch=[6080]
2024/01/09 21:00:00.001959 [DBG] Scheduling wake timer for scheduled recording in 23h58m30s
2024/01/09 21:00:02.181508 [TVE] stream timestamps: fx: start_at=2024-01-09T20:59:03-06:00 end_at=2024-01-09T20:59:32-06:00 live_delay=25.7575087s
2024/01/09 21:00:02.181508 [TNR] Opened connection to TVE-frontier_auth-gateway_net for ch6080 FX
2024/01/09 21:00:02.182035 [DVR] Recording for job 1704855600-64 from TVE-frontier_auth-gateway_net ch6080 into "TV\Fargo\Fargo S05E09 The Useless Hand 2024-01-09-2100.mpg" for 1h3m59.9980401s
2024/01/09 21:00:02.378765 [IDX] Generating video index for job 1704855600-64
2024/01/09 21:05:28.000255 [SNR] Rewriter statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=1956.778333
2024/01/09 21:05:28.000255 [SNR] Buffer statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: buf=0% drop=0%
2024/01/09 21:05:28.000907 [SNR] Streaming statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: timeouts=17 segment_timeouts=17 playlist_timeouts=0
2024/01/09 21:05:28.007596 [TNR] Closed connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:05:28.007596 [TNR] Error during live stream for ch6036 TNTP: failed after 32.0060211s: hls: temporary failure while downloading: hls: timeout while waiting for data
2024/01/09 21:05:42.561414 [TVE] stream timestamps: tntp: start_at=2024-01-09T20:55:31-06:00 end_at=2024-01-09T21:05:26-06:00 live_delay=9.9484148s
2024/01/09 21:05:42.561414 [TNR] Opened connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:08:00.450210 [SNR] Rewriter statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=108.170233
2024/01/09 21:08:00.450210 [SNR] Buffer statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: buf=0% drop=0%
2024/01/09 21:08:00.452225 [SNR] Streaming statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: timeouts=7 segment_timeouts=7 playlist_timeouts=0
2024/01/09 21:08:00.460538 [TNR] Closed connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:08:00.460538 [TNR] Error during live stream for ch6036 TNTP: failed after 40.6611353s: hls: temporary failure while downloading: hls: timeout while waiting for data
2024/01/09 21:08:11.557239 [TVE] stream timestamps: tntp: start_at=2024-01-09T20:58:02-06:00 end_at=2024-01-09T21:07:56-06:00 live_delay=8.7942397s
2024/01/09 21:08:11.557239 [TNR] Opened connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:09:11.610120 [SNR] Rewriter statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=30.084233
2024/01/09 21:09:11.610120 [SNR] Buffer statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: buf=0% drop=0%
2024/01/09 21:09:11.610120 [SNR] Streaming statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: timeouts=3 segment_timeouts=3 playlist_timeouts=0
2024/01/09 21:09:11.615722 [TNR] Closed connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:09:11.615722 [TNR] Error during live stream for ch6036 TNTP: failed after 38.9079575s: hls: temporary failure while downloading: hls: timeout while waiting for data
2024/01/09 21:09:23.514400 [TVE] stream timestamps: tntp: start_at=2024-01-09T20:59:14-06:00 end_at=2024-01-09T21:09:08-06:00 live_delay=8.6794005s
2024/01/09 21:09:23.514970 [TNR] Opened connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:10:20.818708 [SNR] Rewriter statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=30.076233
2024/01/09 21:10:20.818708 [SNR] Buffer statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: buf=0% drop=0%
2024/01/09 21:10:20.818708 [SNR] Streaming statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: timeouts=5 segment_timeouts=5 playlist_timeouts=0
2024/01/09 21:10:20.824410 [TNR] Closed connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:10:20.824410 [TNR] Error during live stream for ch6036 TNTP: failed after 38.4986353s: hls: temporary failure while downloading: hls: timeout while waiting for data
2024/01/09 21:10:27.359656 [TVE] stream timestamps: tntp: start_at=2024-01-09T21:00:20-06:00 end_at=2024-01-09T21:10:14-06:00 live_delay=6.457656s
2024/01/09 21:10:27.359656 [TNR] Opened connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:11:10.202841 [SNR] Rewriter statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=12.074233
2024/01/09 21:11:10.202841 [SNR] Buffer statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: buf=0% drop=0%
2024/01/09 21:11:10.203388 [SNR] Streaming statistics for 192.168.1.73 (Entertainment Room) for ch6036 TNTP: timeouts=4 segment_timeouts=4 playlist_timeouts=0
2024/01/09 21:11:10.212453 [TNR] Closed connection to TVE-frontier_auth-gateway_net for ch6036 TNTP
2024/01/09 21:11:10.212453 [TNR] Error during live stream for ch6036 TNTP: failed after 41.2358536s: hls: temporary failure while downloading: hls: timeout while waiting for data
2024/01/09 21:12:13.775112 [TRS] DNS: OK: Resolved host via system DNS
2024/01/09 21:12:13.775112 [TRS]     DBG: Provider: "Allo Communications LLC" (ACL-99) from 72.46.62.70
2024/01/09 21:12:14.036619 [TRS] Cloud Reachable: OK: Connected to community.getchannels.com
2024/01/09 21:12:14.137625 [TRS] Local Time: OK: Local clock is accurate
2024/01/09 21:12:14.176354 [TRS] TV Everywhere: OK: Chrome version up to date: 120.0.6099.131
2024/01/09 21:12:14.182500 [TRS] TV Everywhere DNS: OK: Resolved TVE authenticator via system DNS
#2

definitely not an issue with TNT itself, it works fine. something on your network? network path to tve? change dns?

2024/01/10 11:48:30.321462 [TNR] Opened connection to TVE-Cablevision for ch6035 TNT
2024/01/10 11:48:39.003846 [SNR] Rewriter statistics for 192.168.6.4 (iPad) for ch6035 TNT: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=19.087133
2024/01/10 11:48:39.004266 [SNR] Buffer statistics for 192.168.6.4 (iPad) for ch6035 TNT: buf=0% drop=0%
2024/01/10 11:48:39.004385 [SNR] Streaming statistics for 192.168.6.4 (iPad) for ch6035 TNT: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/01/10 11:48:39.021906 [TNR] Closed connection to TVE-Cablevision for ch6035 TNT
2024/01/10 11:50:18.016581 [TVE] stream timestamps: tnt: start_at=2024-01-10T11:39:59-05:00 end_at=2024-01-10T11:49:56-05:00 live_delay=15.416579s
2024/01/10 11:50:18.017261 [TNR] Opened connection to TVE-Cablevision for ch6035 TNT
2024/01/10 11:56:26.911364 [SNR] Rewriter statistics for 192.168.6.2 (iPhone) for ch6035 TNT: discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=389.288900
2024/01/10 11:56:26.912825 [SNR] Buffer statistics for 192.168.6.2 (iPhone) for ch6035 TNT: buf=0% drop=0%
2024/01/10 11:56:26.913055 [SNR] Streaming statistics for 192.168.6.2 (iPhone) for ch6035 TNT: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/01/10 11:56:26.914773 [TNR] Closed connection to TVE-Cablevision for ch6035 TNT
#3

I'm not an expert at this but - wouldn't a network, path to tve, or dns issue affect the other channels as well? I'm only experiencing this issue when viewing TNT. :man_shrugging:t2:

#4

Watching a different channel (6035 vs 6036) for a few seconds or minutes doesn't prove anything.
The OP is getting timeouts downloading playlist segments from his local TNT Pacific CDN Server.

#5

it aint for a few minutes chief, count again. i watch it all the time, so the problem is on his side of the planet. i didnt give definite solutions, only probable solutions with a ? at the end.

#6

East coast feed (ch6035 TNT)
19 seconds (highest_pts=19.087133)

East coast feed (ch6035 TNT)
6 minutes, 29 seconds (highest_pts=389.288900)

OP
West coast feed (ch6036 TNTP)
32 minutes, 36 seconds (highest_pts=1956.778333)
timeouts=17 segment_timeouts=17

#7

you're like the other guy who likes to watch himself type. where is your assistance in this thread? help or leave and stop being a hall monitor and go click around your 7 CHDVR docker containers.

@MisterMustang don't know what to tell you, tnt works for more than 6 minutes for me without any issue. maybe the hall monitor can help better than i with his ridiculous Wheel of Fortune watching setup. good luck, ill be watching hockey later on TNT without issues :person_shrugging:

#8

I can't offer any assistance other than interpreting the logs he posted.
He did the right thing by submitting diagnostics and the devs will respond to him.

I'm not going to derail this thread replying to your inaccurate statements.
Enjoy your Hockey.

#9

you already did

#10

TVE is not a monolithic source of video streams. It is a specification that allows different TV networks to serve their own content from their own video sources and use a standardized authentication mechanism.

This means that some channels will use the same video sources and other channels will use different ones.

There are a lot of reasons why you could be getting timeouts and a good way to think about it is like freeways.

Say you want to get to Target. There are a lot of things that can go into how long it takes to go. Which location did your phone maps decide was closest to you? How busy are the freeways and roads to get there? Is there traffic? Is it rush hour?

This is the same sort of stuff that is impacting if you're getting timeouts or not. The DNS servers you're using impact what the system decides is the "closest" location. The time of day can be when everyone else is trying to get to the same place and your ISP could not have enough available capacity.

The unfortunate thing is that, unlike in your car, you don't really have control to say, "okay, I want to go to the location that's 2 miles further away but doesn't have any traffic". You're left up to whatever the streaming provider decides is the best location, which isn't taking into account what the traffic looks like.

Once we rule out that there's nothing locally going wrong, there's not much more that you can do to resolve these sorts of issues.

#11

I appreciate the feedback. If I am understanding correctly, it may have something to do with the West Coast feed (???). I've had it tuned into TNT since (about) 11:00 CST (East Coast feed I believe). And of course, no issues at all - so far. But I swear it happens :upside_down_face: - just not now when I need it to. Again, thanks for the replies

#12

Thank you for the example. That actually (kinda) helps - a lot! I appreciate it.

#13

No, the different feeds for the same channel (and same channel network) generally come from the same source, so it is more likely an issue of the time of day you are watching being a busy time for your ISP, and not which TNT channel you're watching.

1 Like
#14

Thank you.

1 Like
#15

@MisterMustang now that another adult chimed in :point_up: yup. change your dns and test, or install your own on your local network like I do. unbound, fast, local and no shenanigans. I know that having your own DNS is blasmephy here because they want you to use your ISP's DNS so they can easily troubleshoot but I stopped having DNS problems as soon as I installed unbound.

#16

Knock it off with the snark, @AeroR1.

As he’s already using ISP DNS, it’s unlikely that changing any DNS settings will provide different results. It’s theoretically possible it would make a difference, but not likely worth the effort.

1 Like
#17

A post was merged into an existing topic: Experimental lab for audio driver testing

#18

And if you use something like unbound be sure to enable the subnetcache features and send the proper EDNS0/ECS strings unbound.conf(5) — Unbound 1.19.0 documentation or you will have issues with anything geolocated or behind a CDN.