Ok, I’m really trying to remain supportive, but this is getting really disappointing. Correct me if I’m wrong, but hasn’t Plex DVR been around almost 2 years now and it still isn’t reliable enough to record premiere shows in Fall of 2018.
Tonight, I had two aborted recordings on two different Servers on two different channels. To try and avoid missing any premiere shows, I setup a backup server on an ODROID-XU4 in case I had any issues recording on my primary server.
My primary server is a headless Ubuntu Server 18.04.1 LTS running the latest version of PMS 1.13.8.5395. I’m using a WinTV-quadHD as the tuner. At 9:00 pm, I tried recording “The Good Dr” and it aborted early.
My backup (test server) is Ubuntu Server minimal 18.04 LTS running on an ODROID-XU4 running the PMS 1.13.8.5388. That is using a HD Homerun Extend for the tuner. Also at 9:00 pm, I tried recording Manifest which also aborted early.
Logs for both servers are attached.
I know there have been tons of reports regarding these issues along with “Unable to Tune No Parts” , which by the way happened to me yesterday when I was trying to record/watch my local NFL team. Sorry I don’t have logs for that incident…
I love Plex and really hope you guys can get these issues figured out. I’ve been using the DVR feature since it’s release and literally have had 100’s of successful recordings. It seem when I really want to depend on it to record a show, I have issues. Let me know if you need anything else… Also FYI I highly doubt it has anything to do with signal strength as I don’t have issues regarding that.
Another example of trying to record football live and get “Unable to tune no parts”. Started a recording for Thursday night football at 7:00 pm. Tried watching live around around 7:50ish and got the above error. The a few minutes later, I tried playing again and nothing was recorded to that point. This happened to met last Sunday as well.
Happening to me as well. I’m sure its a bug somewhere in Plex. Recordings work, until they don’t. I get the dreaded “no parts” error on a single channel. Other channels continue to work fine, but no recording, or live tv session works on that channel. Plex seems to refuse to even try, it instantly gives an error message on selecting that channel. As soon I restart Plex, then the affected channel works fine again.
Apologies first for the long time in responding. I have been looking at your logs and I suspect the issue arose when the live tv playback that started at 18:27 was cancelled at 18:28. An issue like this which gave rise to errors at the subsequent attempts to tune has been referred to the development team.
The scheduled recording at 19:00 failed with an error
Sep 27, 2018 19:00:00.673 [0x7f770bffa700] DEBUG - DVR:Grabber: Allocated a tuner (1 left)
Sep 27, 2018 19:00:00.673 [0x7f770bffa700] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
and similarly your attempt to watch live tv later
Sep 27, 2018 19:53:50.834 [0x7f76f2bff700] DEBUG - DVR:Grabber: Allocated a tuner (1 left)
Sep 27, 2018 19:53:50.834 [0x7f76f2bff700] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
I am adding your logs to the issue that is under investigation with the development team
Thank you for your response. I appreciate it! I feel there is some type of correlation between using the live tv and having failed recordings. I initially rarely used the live tv feature and have had a lot of success with hundreds of recordings over the last two years.
Once I started using Live TV more it seemed the success rate went down with more failed recordings. Can’t really elaborate further but just my feeling…
So basically in the interim, If I use the live TV feature, I restart PMS service before I have any important recordings and I get 100% success.
I do the same thing after using live TV, every day at the end of my work day I login and restart the PMS services and have been getting a 100% success rate. The one day I did not log in and restart the services I had an aborted recording. After restarting them that recording started and finished as a partial recording.
Last week I noticed I was getting some memory error correction notifications on my server. I pulled the RAM and swapped it around and have not received any more messages about that, and have not had any aborted recordings until this evening. A show was supposed to start recording at 6:58 when I logged in at 6:59 it showed that the recording had aborted. I SSHed into the server restarted the service and the recording immediately started.
This has been seen before and was referred to the development team. It is suspected that it is to do with earlier use of Live TV for that channel. As you have found, a server restart resolves the issue
Oct 25, 2018 18:58:00.452 [0x7f86aafff700] DEBUG - DVR:Grabber: Starting operation for 'The Big Bang Theory - E6 - The Imitation Perturbation'.
Oct 25, 2018 18:58:00.455 [0x7f86aafff700] DEBUG - DVR:Grabber: HDHomerun starting a media grab on device device://tv.plex.grabbers.hdhomerun/104ACDF1 (Silicondust HDHomeRun CONNECT, supported) tuner 0.
Oct 25, 2018 18:58:00.464 [0x7f86aafff700] DEBUG - DVR:Grabber: Saving recording to "/mnt/b-data/DVR/.grab/3cdd2f860b4f7a5dc5d06062d1a592a5eb3de270"
Oct 25, 2018 18:58:00.483 [0x7f86aafff700] DEBUG - DVR:Grabber: Waiting for a tuner (2 available).
Oct 25, 2018 18:58:00.483 [0x7f86aafff700] DEBUG - DVR:Grabber: Allocated a tuner (1 left)
Oct 25, 2018 18:58:00.483 [0x7f86aafff700] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
I will add your logs to the evidence that was referred to the development team
@pbenzschawel@baendres I would like to offer you a development build to try to see if the issue is fixed. If you are willing to try it, please let me know what platform you are running on
@sa2000
Sure I can try it out. I am also on Ubuntu 64 bit. I won’t be able to install it until after Survivor records this week (the wife would kill me if she missed it)
Thank you - i am sending you a link to development version 1.14.0.5464
This has a fix for issue where livetv use may impact recordings and tuning afterwards
A number of Live TV and DVR improvements - one to mention is the change to the deletion policy. It will now be based on date recorded rather than original airing
@sa2000 I installed 1.14 last night and so far haven’t had any issues relating to aborted recordings or live tv. So far so good! I will continue to test without restarting PMS and see if I have any issues.
However, may be unrelated, but I cannot update my EPG guide now. I only have 1 day. During a refresh it cancels early at different intervals. I read other forums which you talked about it being a cloudfare issue or gracenote issue. Didn’t know if those were still relevant as the post was from a while back. Anyways, I’ve attached my logs. You will see the guide refresh JSON error right at the end of the first PMS logfile. FYI I only have 22 channels and do not have “Enhanced Guide” checked.
Thank you again though for all your help getting the tuning issue fixed once and for all.
Could you get me zip of these files /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Diagnostics/EPG-onconnect-e062a56a-4274-4da9-a00f-24cdfebc9f81.json /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Diagnostics/EPG-onconnect-eb37dc6d-2e41-4aa5-b4b4-5c2209d44304.json
Nov 08, 2018 09:34:37.627 [0x7f2c1bbfd700] ERROR - EPG: JSON parse error. Wrote JSON data to "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Diagnostics/EPG-onconnect-e062a56a-4274-4da9-a00f-24cdfebc9f81.json"
. . .
Nov 08, 2018 09:42:28.991 [0x7f2c16ffd700] ERROR - EPG: JSON parse error. Wrote JSON data to "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Diagnostics/EPG-onconnect-eb37dc6d-2e41-4aa5-b4b4-5c2209d44304.json"
Are there lots of files in that Diagnostics directory ? how far back do they go in dates? Could actually zip whole folder and also get list directory showing names, dates and sizes
In the past these were gracenote issues
The log is also showing a DNS glitch - for one second plex.tv failed to get DNS Resolved at 09:42:03 - not sure why that was. Local issue ? ISP DNS issue ?
Nov 08, 2018 09:41:54.706 [0x7f2c13fff700] DEBUG - NetworkInterface: received Netlink message len=88, type=RTM_DELADDR, flags=0x0
Nov 08, 2018 09:41:54.706 [0x7f2c13fff700] DEBUG - NetworkInterface: Netlink address message family=2, index=2, flags=0x0
Nov 08, 2018 09:41:54.706 [0x7f2c13fff700] DEBUG - Network change.
Nov 08, 2018 09:41:54.706 [0x7f2c13fff700] DEBUG - NetworkInterface: Notified of network changed (force=0)
Nov 08, 2018 09:42:02.335 [0x7f2c083ff700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=b50cfa67-d3fd-46a6-81cf-a8dceb61a9df
Nov 08, 2018 09:42:03.186 [0x7f2c083ff700] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=b50cfa67-d3fd-46a6-81cf-a8dceb61a9df
Nov 08, 2018 09:42:03.189 [0x7f2c0effd700] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/0d136eec0e55d89880dcb4f66364b0347e270d7a/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=cabaee21-0bcd-4fc3-9ff9-2ed61a603add
Nov 08, 2018 09:42:03.239 [0x7f2c0effd700] ERROR - Error issuing curl_easy_perform(handle): 6
Nov 08, 2018 09:42:03.239 [0x7f2c0effd700] WARN - HTTP error requesting PUT https://plex.tv/api/servers/0d136eec0e55d89880dcb4f66364b0347e270d7a/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=cabaee21-0bcd-4fc3-9ff9-2ed61a603add (0, No error) (Couldn't resolve host 'plex.tv')
Nov 08, 2018 09:42:03.242 [0x7f2c0d7fa700] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/0d136eec0e55d89880dcb4f66364b0347e270d7a/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=f6c09cf7-1292-4809-be63-39236605ca3e
Nov 08, 2018 09:42:03.299 [0x7f2c0d7fa700] ERROR - Error issuing curl_easy_perform(handle): 6
Nov 08, 2018 09:42:03.299 [0x7f2c0d7fa700] WARN - HTTP error requesting PUT https://plex.tv/api/servers/0d136eec0e55d89880dcb4f66364b0347e270d7a/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=f6c09cf7-1292-4809-be63-39236605ca3e (0, No error) (Couldn't resolve host 'plex.tv')
Nov 08, 2018 09:42:04.849 [0x7f2c083ff700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=a2d7152b-0b62-494b-a525-e114ef34a67b
Nov 08, 2018 09:42:05.679 [0x7f2c083ff700] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=a2d7152b-0b62-494b-a525-e114ef34a67b
Here are the two requested, yes there is about a dozen in there… They only go back to yesterday, however I had wiped my entire database/directory a few days prior and started from scratch.
