OK I tried it and it returned the word "true". Is that good?
I tried the long press to check for an update already, but it doesn't appear there is one. Do you guys have one about to be released?
Yes, if it returned true it worked. You should see on the Status page how long the DVR has been running.
It doesn't appear that the restart worked. The Uptime should show that it has just restarted.
You issued:
curl -XPUT http://192.168.3.182:8089/updater/force/restart
?
yes
Odd. Can you try it again? I just tested it on my own DVR and it restarted it. Also, could you check the recent DVR logs to see if it did anything?
I did it again and it returned the same "true" response, but this time IT WORKED!!!!!!
You guys I think are the single best support I have ever experienced, thank you!!!
Now let's see if it stays up and working for more than the 10 days I had on the previous version.
1 Like
OK it was working all around and now it isn't again. It only works locally but not remotely. Here are the logs with some errors:
2020/01/07 16:16:55.149491 [DVR] Starting job 1578441540-55 NHL Hockey on ch=[6171 1250]
2020/01/07 16:16:55.149539 [DVR] Waiting 1h12m4.850475047s until next job 1578454140-48 Frontline
2020/01/07 16:16:55.606450 [TNR] Opened connection to 131AEEA1/0 for ch1250 NSPAHD2
2020/01/07 16:16:56.341708 [DVR] Recording for job 1578441540-55 from 131AEEA1 ch1250 into "TV/NHL Hockey/NHL Hockey Philadelphia Flyers at Carolina Hurricanes 2020-01-07-1616.mpg" for 43m4.85041989s
2020/01/07 16:16:56.360873 [IDX] Generating video index for job 1578441540-55
2020/01/07 16:16:58.536460 [SYS] Created database snapshot: backup-20200107.161658
2020/01/07 16:16:58.536881 [SYS] Removing old backup backup-20191215.045615
2020/01/07 16:17:05.422997 [IDX] Pruned 1125 expired airings from USA-PA37648-X in 79.469323ms.
2020/01/07 16:17:05.437114 [IDX] Pruned 170 expired airings from USA-OTA96738 in 14.023646ms.
2020/01/07 16:17:05.499876 [IDX] Pruned 987 expired airings from X-TVE in 62.688541ms.
2020/01/07 16:20:16.962482 [NAT] Successfully mapped port 8090 using natpmp
2020/01/07 16:21:40.459740 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:23:30.180582 [DVR] Waiting 1h5m29.819434156s until next job 1578454140-48 Frontline
2020/01/07 16:30:13.505767 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:38:46.627514 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:42:19.805953 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:42:20.404937 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:42:25.886916 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:42:31.826388 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:42:32.845245 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:47:19.588877 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 16:55:52.662649 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 17:00:00.457170 [TNR] Closed connection to 131AEEA1/0 for ch1250 NSPAHD2
2020/01/07 17:00:00.464320 [SNR] Statistics for "TV/NHL Hockey/NHL Hockey Philadelphia Flyers at Carolina Hurricanes 2020-01-07-1616.mpg": ss=100% snq=100% seq=100% bps=3239616,2034912-5626464 pps=313,203-534
2020/01/07 17:00:00.704378 [DVR] Finished job 1578441540-55 NHL Hockey
2020/01/07 17:00:00.734479 [DVR] Waiting 28m59.265537804s until next job 1578454140-48 Frontline
2020/01/07 17:00:01.032310 [DVR] Processing file-2144: TV/NHL Hockey/NHL Hockey Philadelphia Flyers at Carolina Hurricanes 2020-01-07-1616.mpg
2020/01/07 17:00:02.466907 [DVR] Running commercial detection on file 2144 (TV/NHL Hockey/NHL Hockey Philadelphia Flyers at Carolina Hurricanes 2020-01-07-1616.mpg)
2020/01/07 17:04:27.268007 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 17:13:00.313533 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 17:21:33.368231 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 17:25:40.158996 [DVR] Commercial detection finished with 6 markers.
2020/01/07 17:29:00.014097 [DVR] Starting job 1578454140-48 Frontline on ch=[1033]
2020/01/07 17:29:00.014188 [DVR] Waiting 1h29m59.985821853s until next job 1578459540-ch1215 NFL Football
2020/01/07 17:29:00.470024 [TNR] Opened connection to 131AEEA1/0 for ch1033 WITFDT
2020/01/07 17:29:00.738423 [DVR] Recording for job 1578454140-48 from 131AEEA1 ch1033 into "TV/Frontline/Frontline S38E08 Targeting El Paso 2020-01-07-1729.mpg" for 1h1m59.985750551s
2020/01/07 17:29:00.755004 [IDX] Generating video index for job 1578454140-48
2020/01/07 17:30:08.453601 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 17:38:42.598385 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 17:47:15.650178 [sessions] ERROR! securecookie: expired timestamp
2020/01/07 18:31:00.456028 [TNR] Closed connection to 131AEEA1/0 for ch1033 WITFDT
2020/01/07 18:31:00.475042 [SNR] Statistics for "TV/Frontline/Frontline S38E08 Targeting El Paso 2020-01-07-1729.mpg": ss=100% snq=100% seq=100% bps=7002624,2612448-10740064 pps=670,255-1023
2020/01/07 18:31:00.703153 [DVR] Finished job 1578454140-48 Frontline
2020/01/07 18:31:00.730345 [DVR] Waiting 27m59.26967197s until next job 1578459540-ch1215 NFL Football
2020/01/07 18:31:01.030507 [DVR] Processing file-2145: TV/Frontline/Frontline S38E08 Targeting El Paso 2020-01-07-1729.mpg
2020/01/07 18:31:02.599307 [DVR] Running commercial detection on file 2145 (TV/Frontline/Frontline S38E08 Targeting El Paso 2020-01-07-1729.mpg)
2020/01/07 18:39:19.165926 [NAT] Successfully mapped port 8090 using natpmp
PS - I did get it back working by unchecking and checking the DVR tab in Settings, effectively turning the DVR off and then on again.
It looks like left over issues from when the time on your SHIELD was wrong. You may need to re-select “Connect to Channels DVR” from the iOS/tvOS app as well.
1 Like
It’s locked up again in the same way. Can see all menus except Settings and Logs when accessing it remotely.
PS - Does the same thing when accessing locally as well.
I think this is the important part of the logs where this error was caused the other day (didn't notice until late last night). I was able to access this using the "...log?n=-1" address you gave me earlier.:
2020/01/07 09:10:24.382198 [DVR] Deleting job with expired serial: 1578817740-41 NFL Football (EP000031282352)
2020/01/07 09:10:24.383614 [DVR] Deleting job with expired serial: 1579136340-32 The Goldbergs (EP017396170153)
2020/01/07 09:10:24.389162 [DVR] Deleting job with expired serial: 1579138140-33 Schooled (EP029705760025)
2020/01/07 09:10:24.395192 [DVR] Deleting job with expired serial: 1579309140-57 American Housewife (EP024327770081)
2019/07/23 11:05:10.149741 [SYS] Starting Channels DVR v2020.01.03.0511 (android-arm64 pid:8835) in /data/data/com.getchannels.dvr/files/channels-dvr/data
2019/07/23 11:05:13.996847 [HDR] Found 0 devices
2019/07/23 11:06:09.071975 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com: No address associated with hostname
2019/07/23 11:06:09.088080 [SYS] Started HTTP Server
2019/07/23 11:06:09.909872 [DVR] Recording engine started in /storage/A8E26A9EE26A710C/NVIDIA_SHIELD
2019/07/23 11:06:09.911670 [SYS] Bonjour service running for dvr-shield.local. []
2019/07/23 11:06:09.911828 [ERR] Failed to start fakejour: listen udp 224.0.0.224:8899: setsockopt: no such device
2019/07/23 11:06:09.926499 [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
2019/07/23 11:06:13.134223 [SYS] Created database snapshot: backup-20190723.110612
2019/07/23 11:06:13.134958 [SYS] Removing old backup backup-20190723.110612
2019/07/23 11:06:19.997223 [IDX] Pruned 0 expired airings from X-TVE in 833.542µs.
2019/07/23 11:06:19.999123 [IDX] Pruned 0 expired airings from USA-PA37648-X in 1.073021ms.
2019/07/23 11:18:38.653016 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2019-07-23 11:00AM
2019/07/23 11:18:38.980322 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:18:38.983612 [DVR] Fetching guide data for 124 stations in X-TVE @ 2019-07-23 11:00AM
2019/07/23 11:18:39.113443 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:18:39.120333 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2019-07-23 5:00PM
2019/07/23 11:18:39.249452 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:18:39.252766 [DVR] Fetching guide data for 124 stations in X-TVE @ 2019-07-23 5:00PM
2019/07/23 11:18:39.382513 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:18:39.388850 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2019-07-23 11:00PM
2019/07/23 11:18:39.518729 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:18:39.521954 [DVR] Fetching guide data for 124 stations in X-TVE @ 2019-07-23 11:00PM
2019/07/23 11:18:39.651442 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:18:39.665977 [IDX] Pruned 0 expired airings from X-TVE in 1.455364ms.
2019/07/23 11:18:39.668206 [IDX] Pruned 0 expired airings from USA-PA37648-X in 2.159219ms.
I think this is the culprit, the log that says "Failed to refresh auth: Post"
2019/07/23 11:05:10.149741 [SYS] Starting Channels DVR v2020.01.03.0511 (android-arm64 pid:8835) in /data/data/com.getchannels.dvr/files/channels-dvr/data
2019/07/23 11:05:13.996847 [HDR] Found 0 devices
2019/07/23 11:06:09.071975 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com: No address associated with hostname
This is the wrong date?
Exactly, which is apparently a symptom of the problem!
I’m thinking it has something to do with the remnants of the older DVR Server I had on here before you advised me to move it to a new external USB Hard drive attached to my Shield. I believe you told me this sometime around that date. Coincidence?
When it suddenly starts working correctly, the date and time are correct.
You can see in the logs I posted a few posts up where the date is correct and then it reverts to the 7/23/2019 date when all the issues resurface.
Here is where it transitioned:
Sounds like the clock on the shield is failing. Could be a hardware failure. That explains the other weird issues too.
No I do t think that could be related. It's saying "starting 2020.01" but the date is 2019.07 so the clock on your shield is broken.
OK my daughter got home and she rebooted everything for me. Here is the log for the transition point at which it crashed and then just came back up.:
2020/01/10 16:26:18.875318 [SYS] Bonjour service stopped.
2020/01/10 16:26:18.902433 [DVR] Recording engine stopped.
2019/07/23 11:05:10.880354 [SYS] Starting Channels DVR v2020.01.03.0511 (android-arm64 pid:8981) in /data/data/com.getchannels.dvr/files/channels-dvr/data
2019/07/23 11:05:14.728568 [HDR] Found 0 devices
2019/07/23 11:05:54.832236 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com: No address associated with hostname
2019/07/23 11:05:54.836812 [SYS] Started HTTP Server
2019/07/23 11:05:55.311990 [DVR] Recording engine started in /storage/A8E26A9EE26A710C/NVIDIA_SHIELD
2019/07/23 11:05:55.313404 [SYS] Bonjour service running for dvr-shield.local. []
2019/07/23 11:05:55.313537 [ERR] Failed to start fakejour: listen udp 224.0.0.224:8899: setsockopt: no such device
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
2019/07/23 11:05:58.175451 [SYS] Created database snapshot: backup-20190723.110558
2019/07/23 11:05:58.176157 [SYS] Removing old backup backup-20190723.110558
2019/07/23 11:06:05.345176 [IDX] Pruned 0 expired airings from X-TVE in 1.311406ms.
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
2019/07/23 11:06:12.685548 [ERR] Failed to fetch station 19612: Get http://data.tmsapi.com/v1.1/stations/19612?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF
2019/07/23 11:06:12.688100 [ERR] Failed to fetch station 58646: Get http://data.tmsapi.com/v1.1/stations/58646?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF
2019/07/23 11:06:12.690731 [ERR] Failed to fetch station 64549: Get http://data.tmsapi.com/v1.1/stations/64549?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF
2019/07/23 11:06:12.695053 [ERR] Failed to fetch station 10146: Get http://data.tmsapi.com/v1.1/stations/10146?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF
2019/07/23 11:06:12.698334 [ERR] Failed to fetch station 58515: Get http://data.tmsapi.com/v1.1/stations/58515?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF
2019/07/23 11:06:12.701453 [ERR] Failed to fetch station 67890: Get http://data.tmsapi.com/v1.1/stations/67890?api_key=x26sg2rpk8qyuyn9ddzwmsuu&lineupId=: net/http: HTTP/1.x transport connection broken: unexpected EOF
(****Repeated over and over With different station numbers ****)
What do these errors represent? Could this be caused by a bad clock?
Yes, nothing will work if the clock is in the past.
If you really want to run a dvr remotely I think you should invest in a NAS instead of the SHIELD.