shows are being aborted

General Discussions Plex Features
41

@johnm_ColaSC said:
Did the DS9 episode even record? Plex shows 0 available tuners.
Apr 23, 2017 21:00:00.129 [0x7f7cc9bfb700] DEBUG - MediaGrabber: Going to record for 3600 seconds, final URL is http://192.168.0.151:5004/auto/v8.3?duration=3600
Apr 23, 2017 21:00:00.129 [0x7f7cc9bfb700] DEBUG - MediaGrabber: Waiting for a tuner (0 available).

So the HDHR at 192.168.0.151 had no tuners available. However the tuner at 192.168.0.156 had 2 tuners available for the other recording.
Apr 23, 2017 21:00:00.749 [0x7f7cd8bff700] DEBUG - Media Grabber: Saving recording to /mnt/plexdvr/TV Shows/.grab/19403b0c5706c8a7472766369b03f1a316de3d38Apr 23, 2017 21:00:00.749 [0x7f7cd8bff700] DEBUG - MediaGrabber: Going to record for 3600 seconds, final URL is http://192.168.0.156:5004/auto/v5.1?duration=3600&transcode=none
Apr 23, 2017 21:00:00.749 [0x7f7cd8bff700] DEBUG - MediaGrabber: Waiting for a tuner (2 available).

Not sure why Plex wouldn’t use the HDHR with 2 available tuners. If there a difference in channels selected for your different HDHR? Which HDHR is the 192.168.0.151 device?

It’s the connect. Also remember that I have an extend and 2 duals for a total of 8 tuners… There are no errors in the system log for the hdhomerun. I haven’t had any other issues with any other shows.

42

If you go into the DVR settings is the connect showing that it is recording shows currently? I had an issue where Plex was showing one of my connects as recording one show when there was no recordings running at the time. So Plex would only use one of the tuners. After reboot all was cleared up. Wondering if your connect is having a similar issue.

43

I find it sooo fascinating that there are several threads on this same topic.
Tons of user observations postsed…
Plethoras of logs posted…
Hundreds of posts with Info for Plex…

And in all that not a single response from Plex reps AT ALL!!!

So tell me DVR is NOT a trainwreck waiting to happen…

I hate when about 30% of my scheduled recordings fail. Unfortunately, it is what it is and that is how it seems Plex wants to leave it.

Plex has forced all of us to live with it…

44

@jjrjr1 - While it is annoying that Plex reps haven’t responded, this is a beta feature. So not something you should expect to be reliable. Don’t rely on it as your primary DVR if you want dependable recordings.

45

@kamererhouse
Absolutely, I do not depend on it. I have been a Plex Pass member MUCH longer than DVR has been around.

But for folks who purchased Plex Pass to gain DVR… might not feel that way.

But in any case if Plex plans to make this a viable product they should be communicating with us who have been so kind as to pay for the privilege of testing this train wreck…

At least acknowledge us!!!

And to make it even worse… Unless you pay for Plex Pass a person does not even have access to this sub-forum to help make an informed decision before purchase. How many folks do you think would PAY money to get a Beta Test Product with these sort of problems.

Plex is being a little deceptive IMO.

46

@jjrjr1
I agree. If they are listing beta features as a benefit to Plex Pass (which they are) they need to clearly label them as such with a disclaimer.

47

No posts in over a month. I paid for the Plex Pass so I could get DVR functionality. Half of my shows do not get recorded. If I happen to look at the schedule, I see an error that says recording was aborted, but that goes away after awhile and there is no indication that the particular show was even scheduled to be recorded. I don’t see anything in the logs that shows there was an error, or what caused it. Version 1.5.5.3634 if anyone cares.

Since no one from Plex has responded to this thread, I don’t know if anyone is working on this issue. This is the only premium feature I use. I guess I should cancel my Plex Pass and try again next year. I really don’t like paying for beta software.

48

@angus404 said:
No posts in over a month. I paid for the Plex Pass so I could get DVR functionality. Half of my shows do not get recorded. If I happen to look at the schedule, I see an error that says recording was aborted, but that goes away after awhile and there is no indication that the particular show was even scheduled to be recorded. I don’t see anything in the logs that shows there was an error, or what caused it. Version 1.5.5.3634 if anyone cares.

Since no one from Plex has responded to this thread, I don’t know if anyone is working on this issue. This is the only premium feature I use. I guess I should cancel my Plex Pass and try again next year. I really don’t like paying for beta software.

You are not on the latest Plex Pass release. Visit the download page and manually update to 1.7.3.

49

Yes plus what was said above. if you experience problems upload you logs so we can take a look at them and see if there is a problem that needs to be forwarded to the devs.

50

How are things forwarded to the devs?

51

OK…I’m also having the same issue. I have had 2 good recordings, since system updates, Plex Pass etc… My HDHomeRun was not in use by any other user. When I checked on my GUI, it stated “Recording aborted”. Is there anyone from Plex, watching this forum? It seems like a longstanding issue!

52

I’m getting the same thing - “Recording was aborted” . I’m on a Plex Pass free trial, but if I can’t figure out what’s wrong, and there are no meaning logs or support from Plex, I’m going to have to abandon this project.

53

I think it is related to the OTA signal. I have recordings that keep getting aborted, but they are the channels with the worse reception. I practically never see it on the strongest channels. In other words, I can have an aborted recording (weak channel), then immediately get a good recording (strong channel), then get an aborted recording again (weak channel) all within hours of each other.

Now why Plex is aborting the recording I don’t know. Windows Media Center just gives me a crappy recording that is almost too pixelated to watch, but at least it records the whole thing. Usually.

54

@kamererhouse said:
I think it is related to the OTA signal. I have recordings that keep getting aborted, but they are the channels with the worse reception. I practically never see it on the strongest channels. In other words, I can have an aborted recording (weak channel), then immediately get a good recording (strong channel), then get an aborted recording again (weak channel) all within hours of each other.

Now why Plex is aborting the recording I don’t know. Windows Media Center just gives me a crappy recording that is almost too pixelated to watch, but at least it records the whole thing. Usually.

This could be true in your setup, but I know it wasn’t the case in mine, simply because I have a cable card and when plex aborted, I didn’t have any issues connecting to the stream using the HD Home Run windows 10 app.

55

When you say you don’t have any issues, are you saying there are no pixelation moments where the sound or video gets slightly distorted for the entire hour?

Because I can connect to channels without problem, but my weaker channels have pixelation problems from time to time as the environment changes and those are the ones with the biggest abort problems.

56

@kamererhouse said:
When you say you don’t have any issues, are you saying there are no pixelation moments where the sound or video gets slightly distorted for the entire hour?

Because I can connect to channels without problem, but my weaker channels have pixelation problems from time to time as the environment changes and those are the ones with the biggest abort problems.

I don’t want to de-rail this thread. Are you asking me about quality when using my cable card? I haven’t noticed any signal issues.

57

I’m having the same issue as everyone else. I think I’m going to abandon the DVR functionality for awhile and just stick to live tv.

58

Pretty new to Plex and so far have not been able to get my schedule working. After some false starts with the Nvidia Shield not having write access to the USB drive, I thought I finally had it all working. Then the first show failed to record. Here is info from the log. Nothing pops out at me initially.

19:58:00.173 [15388] DEBUG - DVR:Grabber: Starting operation for ‘NCIS: Los Angeles - E13 - Cac Tu Nhan’.
Jan 14, 2018 19:58:00.178 [15388] DEBUG - Activity: registered new activity 128a2b2c-43a7-483b-bf0f-18c3e407c935 - Recording
Jan 14, 2018 19:58:00.206 [15388] DEBUG - DVR:Grabber: HDHomerun starting a media grab on device device://tv.plex.grabbers.hdhomerun/10403241 (Silicondust HDHomeRun CONNECT, supported) tuner 0.
Jan 14, 2018 19:58:00.216 [15388] DEBUG - DVR:Subscription: Failed to resolve subscription for ‘guid: com.gracenote.onconnect://show/3561420 thumb: http://tmsimg.plex.tv/assets/p14215795_b_v5_ab.jpg title: NCIS: Los Angeles type: 2 year: 2009’ to library item
Jan 14, 2018 19:58:00.219 [15388] DEBUG - DVR:Grabber: Saving recording to /storage/3CEA-324A/NVIDIA_SHIELD/.grab/a4a0101bc42b08f737ca8f752afe011797945555
Jan 14, 2018 19:58:01.113 [15866] DEBUG - EPG[onconnect]: Next thing to start/end is at 2018-01-15 02:00:00 (in 120 seconds)
Jan 14, 2018 19:58:05.717 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 20.505670 seconds: 192.168.2.63
Jan 14, 2018 19:58:06.712 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.63 (http://192.168.2.63:8088/description)
Jan 14, 2018 19:58:06.712 [15866] DEBUG - HTTP requesting GET http://192.168.2.63:8088/description
Jan 14, 2018 19:58:06.732 [15866] DEBUG - HTTP 200 response from GET http://192.168.2.63:8088/description
Jan 14, 2018 19:58:09.661 [15388] DEBUG - HTTP requesting GET http://192.168.2.227:80/lineup.json
Jan 14, 2018 19:58:09.678 [15388] DEBUG - HTTP 200 response from GET http://192.168.2.227:80/lineup.json
Jan 14, 2018 19:58:09.678 [15388] DEBUG - DVR:Grabber: Going to record for 4011 seconds, final URL is http://192.168.2.227:5004/auto/v42.1
Jan 14, 2018 19:58:09.681 [15388] DEBUG - DVR:Grabber: Setting timer to stop grab of ‘NCIS: Los Angeles - E13 - Cac Tu Nhan’ in 4011 seconds.
Jan 14, 2018 19:58:09.693 [15388] DEBUG - DVR:Grabber: Waiting for a tuner (2 available).
Jan 14, 2018 19:58:09.693 [15388] DEBUG - DVR:Grabber: Allocated a tuner (1 left)
Jan 14, 2018 19:58:09.693 [15388] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
Jan 14, 2018 19:58:09.695 [15388] DEBUG - DVR:Grabber: Freed a tuner (now 2 available)
Jan 14, 2018 19:58:09.695 [15388] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
Jan 14, 2018 19:58:09.695 [15388] DEBUG - DVR:Grabber: Operation for NCIS: Los Angeles - E13 - Cac Tu Nhan completed with status error (The recording was aborted)
Jan 14, 2018 19:58:09.695 [15388] DEBUG - Activity: Ended activity 128a2b2c-43a7-483b-bf0f-18c3e407c935.
Jan 14, 2018 19:58:09.696 [15388] ERROR - DVR:Grabber: Starting media grab failed.
Jan 14, 2018 19:59:05.716 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 23.064146 seconds: 192.168.2.63
Jan 14, 2018 19:59:05.716 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 20.235289 seconds: 192.168.2.228
Jan 14, 2018 19:59:05.716 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 23.067966 seconds: 192.168.2.238
Jan 14, 2018 19:59:06.764 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.63 (http://192.168.2.63:8088/description)
Jan 14, 2018 19:59:06.765 [15954] DEBUG - HTTP requesting GET http://192.168.2.63:8088/description
Jan 14, 2018 19:59:06.842 [15954] DEBUG - HTTP 200 response from GET http://192.168.2.63:8088/description
Jan 14, 2018 19:59:07.046 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.238 (http://192.168.2.238:8008/ssdp/device-desc.xml)
Jan 14, 2018 19:59:07.046 [15918] DEBUG - HTTP requesting GET http://192.168.2.238:8008/ssdp/device-desc.xml
Jan 14, 2018 19:59:07.069 [15918] DEBUG - HTTP 200 response from GET http://192.168.2.238:8008/ssdp/device-desc.xml
Jan 14, 2018 19:59:11.280 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.228 (http://192.168.2.228:8060/)
Jan 14, 2018 19:59:11.280 [15917] DEBUG - HTTP requesting GET http://192.168.2.228:8060/
Jan 14, 2018 19:59:11.293 [15917] DEBUG - HTTP 200 response from GET http://192.168.2.228:8060/
Jan 14, 2018 20:00:01.222 [15955] DEBUG - EPG[onconnect]: Next thing to start/end is at 2018-01-15 02:30:00 (in 1800 seconds)
Jan 14, 2018 20:00:04.886 [16024] DEBUG - Statistics: Flushing 1 expired bandwidth entries, 0 expired media entries.
Jan 14, 2018 20:00:35.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 22.255742 seconds: 192.168.2.228
Jan 14, 2018 20:00:40.533 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.228 (http://192.168.2.228:8060/)
Jan 14, 2018 20:00:40.534 [16396] DEBUG - HTTP requesting GET http://192.168.2.228:8060/
Jan 14, 2018 20:00:40.546 [16396] DEBUG - HTTP 200 response from GET http://192.168.2.228:8060/
Jan 14, 2018 20:01:37.502 [16490] DEBUG - Sync: uploadStatus
Jan 14, 2018 20:01:44.759 [7689] DEBUG - EventSource: Failure in ReadData (2 - End of file).
Jan 14, 2018 20:01:44.759 [7689] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Jan 14, 2018 20:01:44.759 [7689] ERROR - EventSource: Retrying in 15 seconds.
Jan 14, 2018 20:01:45.693 [7688] DEBUG - handleStreamRead code 335544539: short read
Jan 14, 2018 20:01:45.693 [7688] DEBUG - NotificationStream: Removing because of error
Jan 14, 2018 20:01:59.790 [7689] DEBUG - EventSource: Resolving 45.33.118.95 port 443s
Jan 14, 2018 20:01:59.791 [7689] DEBUG - EventSource: Resolved 45.33.118.95 to 45.33.118.95
Jan 14, 2018 20:01:59.811 [7688] DEBUG - EventSource: Failure in Connect (111 - Connection refused).
Jan 14, 2018 20:01:59.811 [7688] ERROR - EventSource: Retrying in 30 seconds.
Jan 14, 2018 20:02:02.020 [16395] DEBUG - EPG[onconnect]: Purging 20 airings which completed in the past.
Jan 14, 2018 20:02:02.036 [16395] DEBUG - Destroying metadata item 93 (V for Valentine-detta)
Jan 14, 2018 20:02:02.040 [16395] DEBUG - Destroying metadata item 92 (Season 8)
Jan 14, 2018 20:02:02.044 [16395] DEBUG - Destroying metadata item 91 (Bob’s Burgers)
Jan 14, 2018 20:02:02.107 [16395] DEBUG - Destroying metadata item 207 (Episode 10)
Jan 14, 2018 20:02:02.124 [16395] DEBUG - Destroying metadata item 224 (Episode 01-14)
Jan 14, 2018 20:02:02.141 [16395] DEBUG - Destroying metadata item 234 (Under the Influence 3)
Jan 14, 2018 20:02:02.145 [16395] DEBUG - Destroying metadata item 233 (Season 6)
Jan 14, 2018 20:02:02.163 [16395] DEBUG - Destroying metadata item 247 (Family Business)
Jan 14, 2018 20:02:02.167 [16395] DEBUG - Destroying metadata item 246 (Season 22)
Jan 14, 2018 20:02:02.184 [16395] DEBUG - Destroying metadata item 267 (Don’t Bank on Herman)
Jan 14, 2018 20:02:02.202 [16395] DEBUG - Destroying metadata item 278 (Bounty)
Jan 14, 2018 20:02:02.219 [16395] DEBUG - Destroying metadata item 290 (The Tipping Point)
Jan 14, 2018 20:02:02.222 [16395] DEBUG - Destroying metadata item 289 (Season 1)
Jan 14, 2018 20:02:02.226 [16395] DEBUG - Destroying metadata item 288 (Wisdom of the Crowd)
Jan 14, 2018 20:02:02.284 [16395] DEBUG - Destroying metadata item 185 (Episode 01-14)
Jan 14, 2018 20:02:02.357 [16395] DEBUG - Destroying metadata item 320 (Déjà Vu All Over Again)
Jan 14, 2018 20:02:02.376 [16395] DEBUG - Destroying metadata item 340 (You Shook Me)
Jan 14, 2018 20:02:05.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 29.499396 seconds: 192.168.2.63
Jan 14, 2018 20:02:05.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 25.776526 seconds: 192.168.2.182
Jan 14, 2018 20:02:05.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 28.247156 seconds: 192.168.2.228
Jan 14, 2018 20:02:05.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 27.664114 seconds: 192.168.2.238
Jan 14, 2018 20:02:06.723 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.63 (http://192.168.2.63:8088/description)
Jan 14, 2018 20:02:06.724 [16490] DEBUG - HTTP requesting GET http://192.168.2.63:8088/description
Jan 14, 2018 20:02:06.775 [16490] DEBUG - HTTP 200 response from GET http://192.168.2.63:8088/description
Jan 14, 2018 20:02:07.044 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.238 (http://192.168.2.238:8008/ssdp/device-desc.xml)
Jan 14, 2018 20:02:07.044 [16395] DEBUG - HTTP requesting GET http://192.168.2.238:8008/ssdp/device-desc.xml
Jan 14, 2018 20:02:07.063 [16395] DEBUG - HTTP 200 response from GET http://192.168.2.238:8008/ssdp/device-desc.xml
Jan 14, 2018 20:02:07.335 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.182 (http://192.168.2.182:8060/)
Jan 14, 2018 20:02:07.336 [17020] DEBUG - HTTP requesting GET http://192.168.2.182:8060/
Jan 14, 2018 20:02:07.366 [17020] DEBUG - HTTP 200 response from GET http://192.168.2.182:8060/
Jan 14, 2018 20:02:11.600 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.228 (http://192.168.2.228:8060/)
Jan 14, 2018 20:02:11.600 [16395] DEBUG - HTTP requesting GET http://192.168.2.228:8060/
Jan 14, 2018 20:02:11.612 [16395] DEBUG - HTTP 200 response from GET http://192.168.2.228:8060/
Jan 14, 2018 20:02:29.898 [7689] DEBUG - EventSource: Resolving 45.33.118.95 port 443s
Jan 14, 2018 20:02:29.898 [7689] DEBUG - EventSource: Resolved 45.33.118.95 to 45.33.118.95
Jan 14, 2018 20:02:49.998 [7688] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
Jan 14, 2018 20:02:54.997 [7688] DEBUG - HTTP requesting GET https://plex.tv/services/pubsub/servers
Jan 14, 2018 20:02:56.132 [7688] DEBUG - HTTP 200 response from GET https://plex.tv/services/pubsub/servers
Jan 14, 2018 20:03:01.136 [7688] DEBUG - PubSubManager: Time to connect to 45.79.197.109 was 128 ms.
Jan 14, 2018 20:03:01.136 [7688] DEBUG - PubSubManager: Time to connect to 173.255.237.43 was 132 ms.
Jan 14, 2018 20:03:01.137 [7688] DEBUG - PubSubManager: Time to connect to 184.105.148.108 was 151 ms.
Jan 14, 2018 20:03:01.137 [7688] DEBUG - PubSubManager: Time to connect to 109.237.24.233 was 253 ms.
Jan 14, 2018 20:03:01.137 [7688] DEBUG - PubSubManager: Time to connect to 139.162.142.209 was 318 ms.
Jan 14, 2018 20:03:01.137 [7688] DEBUG - PubSubManager: Time to connect to 82.94.168.55 was 383 ms.
Jan 14, 2018 20:03:01.137 [7688] DEBUG - PubSubManager: Time to connect to 139.162.115.125 was 767 ms.
Jan 14, 2018 20:03:01.137 [7688] WARN - PubSubManager: Connection to 45.33.118.95 failed: Connection timed out.
Jan 14, 2018 20:03:01.137 [7688] WARN - PubSubManager: Connection to 45.79.10.123 failed: Connection timed out.
Jan 14, 2018 20:03:01.137 [7688] WARN - PubSubManager: Connection to 139.162.7.93 failed: Connection timed out.
Jan 14, 2018 20:03:01.137 [7688] WARN - PubSubManager: Current server (45.33.118.95) failed, we’ll switch.
Jan 14, 2018 20:03:01.156 [7688] DEBUG - EventSource: Stopping.
Jan 14, 2018 20:03:01.157 [7688] DEBUG - EventSource: Resolving 45.79.197.109 port 443s
Jan 14, 2018 20:03:01.157 [7688] DEBUG - PubSubManager: Updating best host to 45.79.197.109.
Jan 14, 2018 20:03:01.157 [7689] DEBUG - EventSource: Resolved 45.79.197.109 to 45.79.197.109
Jan 14, 2018 20:03:01.157 [7688] DEBUG - PubSubManager: Updating best ping time for 45.79.197.109 to 128 ms.
Jan 14, 2018 20:03:01.758 [7689] DEBUG - EventSource: Connected in 558 ms.
Jan 14, 2018 20:03:01.759 [7689] DEBUG - EventSource: Wrote data, reading reply.
Jan 14, 2018 20:03:02.050 [17081] DEBUG - BPQ: onConsiderProcessing: Idle (true)
Jan 14, 2018 20:03:02.050 [17081] DEBUG - BPQ: [Idle] -> [Processing]
Jan 14, 2018 20:03:02.054 [17081] DEBUG - BPQ: generating queue items from 0 generator(s)
Jan 14, 2018 20:03:02.054 [17081] DEBUG - BPQ: generated 0 item(s) for queue
Jan 14, 2018 20:03:02.055 [17081] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
Jan 14, 2018 20:03:02.055 [17081] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
Jan 14, 2018 20:03:02.059 [17081] DEBUG - BPQ: [Processing] -> [Idle]
Jan 14, 2018 20:03:02.060 [17081] DEBUG - BPQ: garbageCollect - sync - forced - 1
Jan 14, 2018 20:03:02.060 [17081] DEBUG - Sync: starting Sync garbage collection: 1, forced
Jan 14, 2018 20:03:02.060 [17081] DEBUG - Sync: finished Sync garbage collection: 1
Jan 14, 2018 20:03:02.060 [17081] DEBUG - BPQ: garbageCollect - version - forced - -1
Jan 14, 2018 20:03:02.060 [17081] DEBUG - Versions: garbage collecting
Jan 14, 2018 20:03:02.065 [17081] DEBUG - Versions: garbage collected in 0.0 seconds
Jan 14, 2018 20:03:03.499 [7689] DEBUG - EventSource: Read HTTP reply header.
Jan 14, 2018 20:03:03.499 [7689] DEBUG - MyPlex: We appear to have regained Internet connectivity.
Jan 14, 2018 20:03:03.499 [7689] DEBUG - EventSource: Successfully connected to 45.79.197.109.
Jan 14, 2018 20:04:05.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.980514 seconds: 192.168.2.63
Jan 14, 2018 20:04:05.715 [7753] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 20.954378 seconds: 192.168.2.182
Jan 14, 2018 20:04:07.362 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.63 (http://192.168.2.63:8088/description)
Jan 14, 2018 20:04:07.362 [17624] DEBUG - HTTP requesting GET http://192.168.2.63:8088/description
Jan 14, 2018 20:04:07.389 [17624] DEBUG - HTTP 200 response from GET http://192.168.2.63:8088/description
Jan 14, 2018 20:04:11.750 [7753] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.2.182 (http://192.168.2.182:8060/)
Jan 14, 2018 20:04:11.751 [17597]

59

I have the same issue. Just random Recording aborted. I’m not using Plex for live TV, just DVR. I’m pretty sure is it not signal and is set up on cable QAM channels. Sometimes, the turner reports that it is recording something, but nothing is on the schedule. One time I caught it when it said that both tuners were recording, when in fact I only had one recording scheduled at the time. I decided to watch Live TV and it asked me if I wanted to stop recording a show I never heard of on Channel 2.1. I cancelled that and I was able to watch my Live TV while recording. Not sure what is going on.

60

Looks like an update to the Plex Media server Beta channel last night. After reading the change log descriptions, it appears that some of the items in this discussion may have been worked on. My fingers are crossed.