By threads, I meant Linux OS threads. I was able to see them in the diagnostic email you sent in. It's fine you don't understand this level of detail — that's what we're here to understand.
1 Like
FYI, I added a PS to my post above.
Yes, I am testing these updates before I post any of them.
I'll be able to rule out more situations once you are able to send those logs via email to support.
With a Shield as DVR Server, in and out of home?
No. We do not test every release on every device we support in every scenario that it is used.
To give you some context: We are three developers. We have years of history developing the DVR service and have a fairly good understanding of how it behaves and what sort of problems are platform-specific and what sort of problems are general.
Until you can email me the logs from your DVR, my ability to give you a better understanding of what exactly is going on with your DVR is limited, but here are some data points I can give you:
- We have a lot of customers who use the Shield
- You are the only one who has reported issues with the DVR hanging
- The functions in the DVR that are hanging have nothing to do with transcoding
- The functions that are hanging should never hang on a working Linux computer
- In my experience Linux systems that exhibit this sort of hanging are having either hardware or operating system issues
Based on what you've sent so far, it seems likely that at the very least you will need to reboot the Shield and that you may have a bad drive.
1 Like
I’ve been unable to successfully copy over the ?n=-1 logs because they’re SO HUGE and it takes forever for them to fully download in my browser so I can copy them. It times out. Any ideas?
From an iOS device try to long press on http://192.168.3.182:8089/log?n=-1 and select “Download Linked File”. Then from the Files app you can email the file.
1 Like
Awesome suggestion! I tried sending via email as an attachment but it said it may not work since it’s 24mb+. If that doesn’t work I’ll drop it into iCloud for you.
PS - Keep in mind that I moved the server and all the associated equipment (Shield, HDHR Prime, etc.) from my primary location here locally over to my daughter’s place remotely sometime in the middle of what those logs encompass.
Did you get my logs via email? If not as I said I will drop to iCloud.
They came through fine. I’ll review them in a bit.
Could you send me another email with the contents of http://192.168.3.182:8089/debug/stack ?
Also, does http://192.168.3.182:8089/ still not complete loading for you?
Do you have access to something that can reach your SHIELD that can run curl?
OK I was able to have my cousin go in and do a power reset on all the equipment. I am now able to see the log and bring up all the menu sections including Settings and Log. It still isn't working properly though. It shows a DVR date of 7/23/2019 for some reason, even though the software is on the 1/03/2020 version that I downloaded right before this crash.
It won't download any guide data either. I get an error in the logs and something about a certificate expiring, which you can see here:
2019/07/23 11:19:43.472557 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/prerelease.json: x509: certificate has expired or is not yet valid
2019/07/23 11:19:51.918244 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: x509: certificate has expired or is not yet valid
2019/07/23 11:21:17.536897 [DVR] Recording engine stopped.
2019/07/23 11:21:33.345247 [DVR] Recording engine started in /storage/A8E26A9EE26A710C/NVIDIA_SHIELD
2019/07/23 11:21:36.622743 [SYS] Created database snapshot: backup-20190723.112136
2019/07/23 11:21:36.624358 [SYS] Removing old backup backup-20190723.112136
2019/07/23 11:21:43.407707 [IDX] Pruned 0 expired airings from USA-PA37648-X in 1.415729ms.
2019/07/23 11:21:43.408833 [IDX] Pruned 0 expired airings from X-TVE in 1.037344ms.
2019/07/23 11:22:04.006783 [DVR] Fetching guide data for 124 stations in X-TVE @ 2019-07-23 11:00AM
2019/07/23 11:22:04.134701 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:22:04.140646 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2019-07-23 11:00AM
2019/07/23 11:22:04.269990 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:22:04.273050 [DVR] Fetching guide data for 124 stations in X-TVE @ 2019-07-23 5:00PM
2019/07/23 11:22:04.400268 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:22:04.405951 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2019-07-23 5:00PM
2019/07/23 11:22:04.534283 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:22:04.541336 [DVR] Fetching guide data for 124 stations in X-TVE @ 2019-07-23 11:00PM
2019/07/23 11:22:04.676235 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:22:04.682215 [DVR] Fetching guide data for 138 stations in USA-PA37648-X @ 2019-07-23 11:00PM
2019/07/23 11:22:04.807142 [DVR] Error fetching guide data: gracenote error 1023: start_date_too_large
2019/07/23 11:22:04.818733 [IDX] Pruned 0 expired airings from USA-PA37648-X in 1.524062ms.
2019/07/23 11:22:04.819869 [IDX] Pruned 0 expired airings from X-TVE in 1.057292ms.
2019/07/23 11:22:56.585293 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: x509: certificate has expired or is not yet valid
There is more log info earlier that I can cut out some repeated fat and post to here as well.
It appears that for some reason your SHIELD did not set the proper date. I believe that it should use NTP to update the date on the device. Because the date is wrong, many things won't work properly that require the date of the client to be accurate.
Do you still need me to do this?
Is there a way to force reset the date on the Shield, the DVR or anything else to kick this into shape?
I'm not sure. I've never used a SHIELD before. Sometimes the process that needs to run to reset the date will run after some period of time — it may just start working at some point.
You can check the logs from time to time to see if the date has updated or not.
Do you now have remote access to the SHIELD admin interface? (if it has one)
I can see the Shield in my network map and when I try to click on it to access it, it asks for a user name and password. I tried the ones I would think would work but they didn't.
Could this be an effect of when I had the Channels DVR Server on this Shield as internal storage initially and was advised by tmm1 to make it external storage so I changed the storage and reconfigured as external and moved the server?
Is there a way to do a DVR reset remotely?
Yes:
curl -XPUT http://localhost:8089/updater/force/restartSo just open a command prompt and type that in? Is this any different than clicking on and off the DVR checkbox in the settings menu?
Yes. You could also long-press on the "Check For Updates" button if there's been a DVR release since you last updated.