Only seeing these on my Channels DVR TVE server, not my Channels DVR HDHR Prime server.
One in my log from last night while Channels DVR was completely idle.
[ERR] ULK response: 502 Bad Gateway
Another right before my DNS provider failed for about 4 minutes.
[ERR] ULK failure: Get "https://content-ause1-up-vod1.uplynk.com/session/ping/05b85d6492e24c6880861873e3c78a47.json?v=3&pt=9662": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I imagine "ULK" is a reference to Uplynk, which is a streaming video CDN (akin to Akamai) owned by Verizon. There errors look like either their server was down, or some other network issue.
This was in the log last night when nothing was happening on the Channels DVR server.
So it doesn't make sense to me why an error response is being received if Channels DVR isn't doing anything (at least nothing appearing in the log).
Are you sure no TVE streams were active at that time?
Yep. Had ended a short LIVE viewing of a TVE channel about 8 minutes before that error appeared. Nothing in the logs after it until this morning when a scheduled TVE recording started.
I just now wiped out that installation of v2020.07.22.2038 I was running and did a fresh install of v2020.07.30.2221
Still would like to know what ULK stands for if anyone knows.
[ERR] ULK response: 502 Bad Gateway
Last four entries in the DVR log
2021/01/03 17:47:05.852347 [TNR] Closed connection to TVE-Comcast_SSO for ch6111 AHC
2021/01/03 19:18:50.299767 [SYS] Created database snapshot: backup-20210103.191850
2021/01/03 19:18:50.300126 [SYS] Removing old backup backup-20201209.131143
2021/01/04 06:03:50.721054 [ERR] ULK response: 502 Bad Gateway
Diagnostics Logs have been submitted as 0e4a88eb-9b3f-4835-9249-7130e76823ce.
Looking back in the log I see three other instances on 2020/09/07, 2020/09/29 and 2020/10/29
2020/09/07 11:24:26.084407 [TNR] Closed connection to TVE-Comcast_SSO for ch6101 DISCOVERY
2020/09/07 12:49:58.416799 [SYS] Created database snapshot: backup-20200907.124958
2020/09/07 12:49:58.417116 [SYS] Removing old backup backup-20200813.103922
2020/09/07 13:14:15.512574 [ERR] ULK response: 502 Bad Gateway
2020/09/07 13:28:33.522398 [TNR] Opened connection to 1323AADB/0 for ch52 TVLANDP
2020/09/28 21:31:10.348188 [DVR] Waiting 10h28m49.651828016s until next job 1601391600-ch6750 Manual Recordings
2020/09/29 01:33:01.888178 [ERR] ULK response: 502 Bad Gateway
2020/09/29 08:00:00.007674 [DVR] Starting job 1601391600-ch6750 Manual Recordings on ch=[6750 6000]
2020/10/28 22:00:30.913194 [TNR] Closed connection to TVE-Comcast_SSO for ch6004 KVIE
2020/10/28 22:00:30.913297 [DVR] Finished job 1603943990-10 NOVA
2020/10/28 22:00:31.013400 [DVR] Skipping job 1604015940-28 Alaskan Bush People
2020/10/28 22:00:31.142007 [DVR] Processing file-1728: TV/NOVA/NOVA S47E15 Can We Cool the Planet 2020-10-28-2059.mpg
2020/10/29 01:44:26.027863 [ERR] ULK response: 502 Bad Gateway
2020/10/29 09:25:00.025506 [DVR] Fetching guide data for 139 stations in X-TVE @ 2020-10-29 9:00AMMore questions than answers.
Any idea what this means?
Did the Diagnostic Logs I submitted help any?
What is it in response to that's not being logged?
ULK == U Like Know?
Can you reply or are you under orders not to talk about it?
Come on, at least admit you have no idea what it means either.
I’m not a dev but I’ll admit I have no idea what it means!
@racameron's answer was correct. There is a keepalive used while watching some TVE streams so they don't expire. It sounds like it's not noticing that you stopped watching after a while.
Since you use TVE infrequently, perhaps you can submit diagnostics after having finished using TVE and the dvr is completely idle so I can see if there are background processes still running when they should have been stopped.
Thank you.
Is it only used for some particular TVE channels?
Since it happens so infrequently (not every time I use TVE) is there anything I can check on after closing out a TVE connection?
Otherwise I'd have to be submitting diagnostics everytime a TVE recording completes and everytime after I'm done viewing a TVE channel.
My only concern is if it's keeping me logged in to my provider or a TVE website.
If you tell me it's not, then I wont be concerned about it and will just ignore the errors in the log.
Last TVE connection (recording) was closed 17 hrs ago and Channels DVR is currently idle.
Logs have been submitted as d6b27560-2676-4d6c-871e-be0ae9cdffc3.
Two back-back recordings sharing the same TVE channel finished a few minutes ago and Channels DVR is currently idle.
Logs have been submitted as 37fdaff5-d63d-49bb-9f85-90d1b86934f6.
Channel surfed a few TVE channels watching live.
Channels DVR is currently idle.
Logs have been submitted as 1c64a485-eea8-49b3-bda8-667036f2d40a.
Channel surfed some TVE channels watching live.
Channels DVR is currently idle.
Logs have been submitted as c74a2f2a-ad15-4a2d-a19a-4b257395ddf5.
Two TVE recordings on different channels at different times completed.
Channels DVR is currently idle.
Logs have been submitted as 53bec2df-97e6-4f6a-878e-395372690807.
This could take 3 months or more before it happens again.
I wont be able to submit diagnostics every time I watch TVE or record it.
The NAS I'm running it on only has TVE as a source and is lightly used.
My other NAS uses my HDHR Prime and does most of my recordings.
OK, so I setup a scheduled task to run every 30 minutes on my NAS that's using TVE.
It captures the time/date and looks for active tcp sessions from the channels-dvr process.
task
bash /volume1/arkives/netwstat.sh
netwstat.sh
#!/bin/sh
date >> /volume1/arkives/netstat.txt
netstat -eenptvW | grep 'latest/cha' >> /volume1/arkives/netstat.txt
netstat.txt
Mon Jan 11 20:59:50 PST 2021-American Experience recording until-Mon Jan 11 22:00:10 PST 2021
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
Mon Jan 11 15:55:04 PST 2021
tcp 0 0 192.168.1.3:47498 54.183.91.17:443 ESTABLISHED 0 94104223 14605/../latest/cha
tcp 0 0 192.168.1.3:53868 34.213.0.154:443 ESTABLISHED 0 94108986 14605/../latest/cha
tcp 0 0 192.168.1.3:56317 54.183.244.104:443 ESTABLISHED 0 94104237 14605/../latest/cha
tcp 0 0 192.168.1.3:49846 192.229.210.181:443 ESTABLISHED 0 94112910 14605/../latest/cha
tcp 0 0 192.168.1.3:36470 104.24.121.199:443 ESTABLISHED 0 94104216 14605/../latest/cha
tcp 0 0 192.168.1.3:50702 13.227.73.64:443 ESTABLISHED 0 94112906 14605/../latest/cha
tcp6 0 0 192.168.1.3:8089 192.168.1.2:33340 ESTABLISHED 0 94104178 14605/../latest/cha
tcp6 0 0 192.168.1.3:8089 192.168.1.2:33333 ESTABLISHED 0 94104166 14605/../latest/cha
tcp6 0 0 192.168.1.3:8089 192.168.1.2:33332 ESTABLISHED 0 94104165 14605/../latest/cha
tcp6 0 0 127.0.0.1:8089 127.0.0.1:59766 ESTABLISHED 0 94108994 14605/../latest/cha
tcp6 0 0 192.168.1.3:8089 192.168.1.2:33331 ESTABLISHED 0 94104163 14605/../latest/cha
tcp6 0 0 192.168.1.3:8089 192.168.1.2:33330 ESTABLISHED 0 94104162 14605/../latest/cha
Mon Jan 11 16:00:02 PST 2021
I was watching Discovery from 15:54:25 to 15:56:16
At 16:00:02 all the connections had closed.
I'll check the log each day and if any connections are active when nothing is being watched/recorded I'll submit diagnostics.
Sound like a plan?
Just pinging to see if you read my replies and if I'm on the right track.
Haven't seen any lingering TCP connections (assuming the 'keepalive' is one, you haven't replied if it's a periodic ping or what) or [ERR] ULK in the logs lately.
I've been putting off updating to a new version since I thought we were working on this issue, but I've only heard crickets.
Nothing obvious in the logs. This is a harmless message related to background ping and has no effect on any of your accounts or logins. I will have to try to recreate it myself because your diagnostics are not giving me the information I need to figure out whats happening.