What are these Errors?

Channels DVR Server
#82

Here are some from before the crash, leading up to it:

2020/01/09 12:59:00.543210 [TNR] Opened connection to 131AEEA1/0 for ch1250 NSPAHD2
2020/01/09 12:59:00.813666 [DVR] Recording for job 1578610740-1 from 131AEEA1 ch1250 into "TV/Quick Slants/Quick Slants 2020-01-09-1259.mpg" for 31m59.984429351s
2020/01/09 12:59:00.832915 [IDX] Generating video index for job 1578610740-1
2020/01/09 12:59:16.418959 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:07:19.828669 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:07:49.526013 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:08:17.208505 [WRN] Buffer for 131AEEA1 ch1250 is more than 50% full (clients=1, len=16777684)
2020/01/09 13:08:32.976784 [WRN] Buffer for 131AEEA1 ch1250 is more than 75% full (clients=1, len=25165868)
2020/01/09 13:08:45.298607 [WRN] Buffer for 131AEEA1 ch1250 is more than 95% full (clients=1, len=31877468)
2020/01/09 13:08:47.808670 [WRN] Buffer for 131AEEA1 ch1250 is more than 99% full (clients=1, len=33219788)
2020/01/09 13:15:52.959428 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:16:23.594876 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:24:26.040691 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:24:56.687736 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:31:00.528029 [TNR] Closed connection to 131AEEA1/0 for ch1250 NSPAHD2
2020/01/09 13:32:59.280218 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:33:29.894805 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:41:32.369880 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:42:33.003198 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:50:05.334377 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:50:35.940869 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:58:38.563366 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 13:59:00.015148 [DVR] Marking expired job 1578610740-1 Quick Slants
2020/01/09 13:59:00.019982 [DVR] Starting job 1578614340-65 NBA Basketball on ch=[6171]
2020/01/09 13:59:00.020016 [DVR] Waiting 59m59.979992027s until next job 1578617940-51 Superstore
2020/01/09 13:59:09.193927 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:07:11.433194 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:07:42.068965 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:15:44.547186 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:16:15.182313 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:24:17.717926 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:24:48.352145 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:32:50.826223 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:33:21.478124 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:41:24.413004 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:41:55.043601 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:49:57.584088 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 14:50:28.228842 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 15:41:16.118518 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 15:41:46.726334 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 15:49:49.245522 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 15:50:19.872280 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 15:58:22.339998 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 15:58:52.969528 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:06:55.319672 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:07:25.895497 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:15:28.628585 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:15:59.151225 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:24:01.884862 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:24:32.470070 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:32:35.189139 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:33:05.719915 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:41:08.438852 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:41:39.006992 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:49:41.756460 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:50:12.314303 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:58:15.059822 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 16:58:45.593190 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:06:48.257500 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:07:18.853094 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:15:21.481647 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:15:52.076450 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:23:54.840552 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:24:25.465930 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:32:27.800095 [sessions] ERROR! securecookie: expired timestamp
2020/01/09 17:32:58.427197 [sessions] ERROR! securecookie: expired timestamp
2020/01/10 09:28:00.050256 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2020-01-10 9:00AM
2020/01/10 09:28:05.270350 [DVR] indexed 999 airings (138 channels) [1s fetch, 4s index]
2020/01/10 09:28:05.884460 [DVR] indexed 44 movies (21 channels) [0s fetch, 0s index]
2020/01/10 09:28:06.012147 [DVR] pruned 111 replaced airings in 0s.............

#83

Yeah that makes sense. How can just a clock break though? Do you think a full factory reset on the Shield could work?

#84

Could be hardware failure.

A factory reset is a good idea.

1 Like
#85

OK thanks. That’ll be fun trying to walk my daughter through that! :joy:

#86

The above doesn’t seem like a hardware/clock issue though. More like a Channels DVR authorization issue.

#87

SSL/TLS communication requires an accurate clock for security. Certificates are only valid for certain date ranges, and requests tagged with old timestamps are ignored to prevent replay attacks.

The specific "dial tcp: lookup" failure you quoted indicates the DNS server on your network did not respond. This could be because the SHIELD just booted up and was still connecting to your home network when the DVR tried to connect to our servers.

1 Like
#88

What is the most reliable and easiest NAS to setup and use for Channels DVR, especially in a remote environment?

#89

The Synology DS218+ is the most popular NAS amongst Channels users.

1 Like
#90

And cheap! :joy:

#91

I think I may have found the issue. I had tried loading a Channels DVR Server on my Windows PC before I shipped the Shield and HDHR tuner over to the remote location. I unchecked the DVR and Bonjour checkboxes when I decided not to use this DVR Server. The PC was disconnected and moved and when it booted back up I think it logged back in as my main DVR Server for Channels, possibly(?) causing a conflict with the one running remotely on the Shield. Could this have caused those errors shown in the logs above?

I do remember when I had them both up while testing here, it did cause issues and neither one ran correctly.

How can I completely remove the Channels DVR Server/Program from my Windows 10 PC? It doesn't show up in my Apps to be removed.

1 Like
#92

No, they could not. You had two errors in your logs.

1: DNS Resolution problem

2019/07/23 11:05:55.339114 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com: No address associated with hostname

says that the DVR tried to download a file from the remote server and could not reach DNS. It is likely this was just a transient error due to the SHIELD booting up and can be ignored if it doesn't continue.

2: Internal Clock problem

2019/07/23 11:06:12.682757 [ERR] Failed to fetch station 79329: Get http://data.tmsapi.com/v1.1/stations/79329?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF

From the logs we can see that the timestamp on those log messages do not match the current date. Many services on the internet will be unable to talk to clients that have an incorrect date.

The system won't be able to function until the DVR starts after the internal clock is correct.

#93

Run the Windows installer from our website again and select uninstall

1 Like
#94

Are you 100% sure of that? Now that I shut down the Windows DVR Server, my remote DVR Server on the Shield is back up and running perfectly fine again, all without having to jump through the hoops I had to a few days ago to get it up and going again.

Of course you guys know a million times more than I do with this stuff, so I’ll monitor it for a few days and see how she goes!

@tmm1, thanks for the removal info. I’ll do that if it continues to auto login and screw things up for the Shield Server. :+1:t3:

#95

Yes, I am 100% sure of both of those issues and that they could not have been related to the DVR running on another system in your house.

Neither of those issues have anything to do with the Channels DVR and are both system-level things that we do not have control over.

#96

OK well I guess we will just monitor for awhile then. If it’s indeed a Shield issue it should certainly return at some point.

#97

Well, after 3 days my Channels DVR Server is still up and running 100% with virtually no issues whatsoever. My hunch does tell me that running the concurrent DVR servers was causing conflicts between them. I am thinking because they are each in two very different time zones (PA and HI), which could explain the clock errors, no? Plus, I do recall when I first stood the second DVR Server up to test, it did almost the exact same thing and crashed the first server, until I disabled the second one. This is actually what made me think of maybe the second server being the culprit again here, because I remembered that I moved my PC (which hosts the second server) and that it rebooted and was on again. I checked the little Channels DVR icon below in the system tray and right clicked it and it showed something like "restart DVR with reboot" or some such, and there was a check mark next to it. I unchecked it and disabled the Channels DVR Server on this PC and, coincidentally(?) at that exact time, my remote DVR Server on my Shield started working fine again and has been working completely fine ever since!

Another thing I noticed was I looked in the logs of my second dvr server and it showed that it came online at about the EXACT same time as my first DVR server used remotely on the Shield went offline. Another coincidence? I think not.

Anyhow, I will continue to monitor this. I am hesitant to turn on this PC Server again for fear it will permanently break something, but that IS the way to confirm that this indeed was the cause, so maybe I will chance it, idk.

I want to thank the amazing Channels Mods/Developers on here for leading me and helping me finally find the solution! Their support here is second to NONE!!!:call_me_hand::+1:

#98

Remote access would break if the second DVR came online. That part makes sense.

The clock issue on the SHIELD is something else. Maybe it got reset when poking around the Android settings while trying to debug. If the clock stays stable and the second DVR stays off you should be good to go!

#99

I wasn't able to "poke around the Android Settings" remotely. The only thing I did was have someone reboot the entire system that was plugged into a power strip. The first time I tried this it allowed me to get back in and thought it fixed it, but it quickly failed again.

The next time we tried rebooting a few days later when I daughter got back home, it didn't fix anything and I was still unable to see anything in the Settings and Logs portions of the menu. That is when I thought about the second DVR running and checked into that possibility, which has seemed to fix this 100% and has been working fine for days.

When you pay your $8/month, that only allows one DVR Server/Account, correct? What normally happens when you try to stand up two, in two completely different time zones on two completely different pieces of hardware?

I will continue to monitor and update.

#100

Are these errors I got recently anything to worry about?

2020/01/14 13:53:14.444758 [DVR] Waiting 2h5m45.55527087s until next job 1579053540-56 This Is Us
2020/01/14 14:12:49.357739 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8214759608: no such file or directory
2020/01/14 14:18:52.270975 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8027557891: no such file or directory
2020/01/14 14:24:24.172783 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8148243448: no such file or directory
2020/01/14 14:26:10.131176 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8893551152: no such file or directory
2020/01/14 14:37:47.636599 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8209301872: no such file or directory
2020/01/14 14:45:26.759508 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8876332295: no such file or directory
2020/01/14 14:50:23.147178 [M3U8] Generator: err=cannot create temp file: open /storage/A8E26A9EE26A710C/NVIDIA_SHIELD/Streaming/m3u8/2182/stream.m3u8737914284: no such file or directory
2020/01/14 14:51:00.023160 [TNR] Closed connection to 131AEEA1/0 for ch1613 AXSTV

#101

Yes, these errors look like your storage is no longer accessible to the SHIELD.