As of this post, I believe I am on the latest version of the server software (running on a windows 7 machine). I keep seeing this message for most of the shows I attempt to record “The recording was aborted” and I can’t duplicate it. Sometimes it records the show fine w/o any issues. I have re-booted the server and rebooted the HDHomeRun device (I am using a cable card). Not sure what else to check.
edit- Can this be moved to the correct forum? I was in the DVR section when I submitted, not sure why it defaulted it to the General Discussion forum.
@Skutterbob said:
Have you checked your TV signal, your network and that your server is not going to sleep?
Yes I have, the tuner I have has a cable card and 3 tuners. Plex was recording on 1 stream I was viewing on my laptop using a 2nd stream and the 3rd was not in use. My cable feed was fine, my other show recorded w/o issues, but I notice that shows randomly stop recording, I get the aborted message. One time I was not at home, so I couldn’t say for sure if the Plex computer shut down or the network switch lost power (or even the tuner device), but another time I was at home, nothing dropped, no flickers, etc… I have yet to notice a short recording fail (30 min) it seems to be something longer than 1-2 hours. So far, I have noticed it with hockey/sporting events that can run for a long time.
Plex computer is not going to sleep, first thing I do is set the power settings to keep everything running. Just to confirm, my current computer up time is 37 days and all sleep options are set to off.
edit- now that I think about it, I wonder if there is not enough space to fit the recording (maybe it can’t delete older content fast enough) so it just aborts the recording? Possibly due to the longer record time, it knows it will take up more space and it knows there won’t be enough space to record the entire program. If that is the case, the reason for aborting would be nice to see in the GUI.
edit2- ok, I have decided that it was a space issue, unless someone can point me in another direction? Maybe advanced logging gives exact reasons? I moved some files over to another drive and I will see if the game that is scheduled to record tomorrow completes 100%
Well this sounds like the issue I have reported forums.plex.tv/discussion/257599/use-of-tuners-tuner-conflict-handling . I will bet you anything Plex tried to record on the tuner you were watching. I have seen it do it many times now. Pretty much guarantees a recording failure if you are using a tuner for live TV as the HD Homerun hand out the lowest number turner not in use and then Plex tries to use it without checking if its in use.
@crusing said:
Well this sounds like the issue I have reported forums.plex.tv/discussion/257599/use-of-tuners-tuner-conflict-handling . I will bet you anything Plex tried to record on the tuner you were watching. I have seen it do it many times now. Pretty much guarantees a recording failure if you are using a tuner for live TV as the HD Homerun hand out the lowest number turner not in use and then Plex tries to use it without checking if its in use.
I don’t think that is the case, for me, but I am not sure. I know some recordings were aborted mid recording. I also know that one time I was not home and only one show was scheduled to record and the tuner was not in use, other than the scheduled recording, but it still aborted. Another time I was home, live streaming from my laptop and it recorded an entire game w/o interruption. I have not been able to duplicate the aborted recording error.
I haven’t been seeing mid recording aborts, so I am no help there. The live tv issue is easy to reproduce. say you are watching live tv and it is using tuner 1. Plex is already recording something on tuner 0. Another recording starts and then immediately fails as it tried to use tuner 1 instead of rolling to tuner 2 which was not in use.
@crusing said:
I haven’t been seeing mid recording aborts, so I am no help there. The live tv issue is easy to reproduce. say you are watching live tv and it is using tuner 1. Plex is already recording something on tuner 0. Another recording starts and then immediately fails as it tried to use tuner 1 instead of rolling to tuner 2 which was not in use.
I have tried to reproduce it, I haven’t been able to. I initially thought that is what was happening…it aborts when it is recording and I try to live stream the channel. I can try again, but first I am going to leave it as is and see if it fails w/o starting a live stream (to rule out the hard drive space…or lack of it).
Thank you for the feedback, I will keep this thread updated.
I’m having the same problems, everything was working fine before I updated to 1.4.1. Tried updating to 1.4.2 same problem. I have a DS415plus and a D214play, both have the same issue.
@Tcatt said:
I’m having the same problems, everything was working fine before I updated to 1.4.1. Tried updating to 1.4.2 same problem. I have a DS415plus and a D214play, both have the same issue.
I have had 3 versions of plex server, but I only recall issues on the current (latest) version and the one before the latest version. I can get exact versions, tomorrow, I still have the EXE files on the desktop. I am not sure how many DVR betas were released, so it might be very easy to figure out the versions…regardless, it is happening on the latest version.
The recording finished w/o issues, tonight. I had plenty of space available on the drive and I did not attempt to watch another feed from my tuner. Next time a recording is scheduled, I will try to watch a live feed using another tuner and seeing if that causes the recording to abort.
Most all of my recordings are aborted unless it’s a short partial recording when I test. I’m on 1.4.2.3400, but this was happening on the beta (I started with 1.2.0.3167). I turned on verbose debug logging and this is all I see around the time it fails.
Mar 02, 2017 06:40:13.137 [0x7f96537fd700] DEBUG - Activity: updated activity af64d024-6f00-4822-99eb-833cf81b94b6 - completed 67% - Recording
Mar 02, 2017 06:40:26.730 [0x7f96617fe700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Mar 02, 2017 06:40:26.730 [0x7f96617fe700] DEBUG - Auth: authenticated user 1 as jdp83
Mar 02, 2017 06:40:26.730 [0x7f96617fe700] DEBUG - Auth: Came in with a super-token, authorization succeeded.
Mar 02, 2017 06:40:26.730 [0x7f9638bff700] DEBUG - Request: [192.168.2.9:60250 (Allowed Network)] GET /status/sessions (4 live) Signed-in Token (jdp83)
Mar 02, 2017 06:40:26.731 [0x7f9638bff700] DEBUG - [Now] Adding 0 sessions.
Mar 02, 2017 06:40:26.731 [0x7f9638bff700] DEBUG - It took 0.0 sec to serialize a list with 0 elements.
Mar 02, 2017 06:40:26.731 [0x7f9661fff700] DEBUG - Completed: [192.168.2.9:60250] 200 GET /status/sessions (4 live) 1ms 292 bytes (pipelined: 1)
Mar 02, 2017 06:40:42.311 [0x7f965a3fe700] ERROR - Error issuing curl_easy_perform(handle): 28
Mar 02, 2017 06:40:42.311 [0x7f965a3fe700] DEBUG - HTTP simulating 408 after curl timeout
Mar 02, 2017 06:40:42.313 [0x7f965a3fe700] DEBUG - MediaRecorder: Recording completed with HTTP status 408
Mar 02, 2017 06:40:42.313 [0x7f965a3fe700] DEBUG - Activity: Ended activity af64d024-6f00-4822-99eb-833cf81b94b6.
Here was the tuner status of my HDHomeRun EXTEND (I had recently tried turning off the h.264 transcoding thinking I needed to reduce the cpu load on my plex server)
Tuner 0 Status
Virtual Channel none
Frequency 183.000 MHz
Program Number 1
Modulation Lock 8vsb
Signal Strength 100%
Signal Quality 78%
Symbol Quality 100%
Transcode Profile none
Streaming Rate 14.739 Mbps
Resource Lock 192.168.2.11
I tested this with the worst received OTA station, but it happens with 98%+ signal quality too.
Thanks
I hope someone from Plex can interpret the log info.
I certainly am not an expert at reading the Plex logs.
I do know it is unusually preferred that Verbose Logging be turned off.
Also I would not recommend running with Transcoding while recording as that right now is purely experimental and is not quite there yet. It has gotten better in V. 1.4.2 BTW.
PS. Every subsequent Beta release for me has gotten less and less reliable with each iteration as I think about 30% of my recording have been aborting for no apparent reason.
Try reducing some of the scheduled tasks like deep analysis and refresh program guide. That has, for me, increased reliability somewhat.
I had another long show record w/o any issues, now I am starting to think the issue was space and that I just didn’t notice the other times when the recording stopped. I have not been at home at the same time a longer event is scheduled to be recorded so I can use tuner 2 and 3 to watch a live show and attempt to watch the event, live, while recording (from my laptop using the tuner app). I know that I can start recording something, now, and test the live feed with another tuner, but I’d like to test with a scheduled recording that I had this issue with, originally.
I am having the same issues. I have 6 dedicated tuners for OTA and three for Cable. Last night 2 of 4 shows aborted (OTA) 1 OTA succeeded and 1 cable succeeded. Tonight 2 of 4 shows aborted. Both OTA again. One OTA and one cable succeeded. This has only been happening since the latest upgrade. I have 3 Gigs available on the disk and 8 processors. I don’t think this is a hardware issue. It think something went a little wonky in the DVR software.
Same issue, periodic aborts while other shows continue recording. Seemed to start immediately after setting up a 2nd HDHomeRun. Had a Connect, just installed an Extend. Plex server version 1.5.0.3501.
