I have basically posted on here and reddit two times now in the past week regarding an issue with the DVR failing to start scheduled recordings. and have not gotten a response from. It just occured again and it would be nice to understand why this continues to happen.
Simply NO. I would suggest doing a plex forum search and your issue to list of other users.
Yea I have done that and just about all of them are issues with Set to HD only or guide issues and such which is really nothing related to the issues I am having. And any post that seem to be closely related to mine is same thing of no responses.
It’s still worth posting all your details in a new post. …you never know…
You either need to give the full set of logs or provide a lot more details. From the small snippet you uploaded in previous posts, the tuner failed to lock on in the allotted time. Since this is a HDHR-Prime model it is difficult to say whether it is the cable provider or Plex.
Oct 02, 2019 10:25:00.886 [14156] ERROR - [Transcoder] http://127.0.0.1:32400/livetv/sessions/80a8ae29-d41d-4f6f-8a95-e65196dd7c01/4184db1a-4c64-4141-a723-095eb3d11b0d/index.m3u8?offset=3658.840937&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx: End of file
Oct 02, 2019 10:25:00.892 [11676] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe' exit code for process 12336 is 1 (failure)
Oct 02, 2019 10:25:00.892 [8036] DEBUG - TranscodeSession: session failed while waiting for duration
Here is the full logs to it happening scroll to 7:11Plex Media Server.3.log (10.1 MB)
Can you let us know what program, and on what channel you were attempting to record, please?
Sorry for the delayed response. Just made a similar post because the issue occured again today and they pointed out your response. Here is the log from the issue occuring today. Show is Van Helsing Channel 680. Issue occurs at 7:30 Plex Media Server.1.log (10.1 MB)
Is your D: drive a local hard drive on the Plex server computer, or a mapped drive to a network share? If D: is a mapped to a network share, in Plex Web -> Settings -> Transcoder do you have the “Transcoder Temporary Directory” set to a location on the D: drive (looks like D:\Plex\Transcode?)
If so, change this transcoder temporary to a location on a local drive on the Plex server. Plex doesn’t recommend having the transcoder temp directory on a mapped drive because it can cause issues - see this article under “Transcoder temporary directory”.
Its a Local Hard Drive.
Come to think of it dont know if this matters but it is a local drive on the PC I have PMS on but I did map it as a network drive and share it on other pc’s in my household. Dont think thats what you were asking about just in case thought it couldnt hurt to tell you
I would think that would be ok to have mappings to that drive as long as nothing is making connections that is locking files that Plex needs via that inbound network mapping. I’ll defer an opinion to @DaveBinM on all of this of course.
There are several consecutive recordings of Van Helsing happening, which should be ok but makes it interesting:
- First, at 7:30, the “6:30 Van Helsing recording” process starts to move the file from the D:\ grab location to the final destination on E:\
- Then within the same second the “7:30 Van Helsing recording” prcoess fails to start with an error. Interestingly this one is using a .grab on E:\ where the 6:30 was using a .grab on D:\
- Then, still in the same second, the “6:30 Van Helsing recording” fails on the move of the file to it’s final E:\ location.
Does this library have multiple locations, one on D:\ and one on E:\? It’s really interesting that one recording was using a grab on the D:\ drive, then the second tried to start with a grab on the E:\ drive. Is E:\ local or mapped? I’m wondering if somehow the almost concurrent E:\ access is creating an issue, or it’s just having issues with E:\ in general.
I found this thread where people were getting some of the same errors, and one does talk about having a library with multiple locations.
Log Details
Nov 01, 2019 07:30:00.542 [5912] DEBUG - DVR:Grabber: Scheduling ‘Van Helsing - E9 - Wakey, Wakey’ for assimilation.
Nov 01, 2019 07:30:00.543 [7412] DEBUG - DVR:Subscription: Resolved subscription to library item ‘Van Helsing’ (5655)
Nov 01, 2019 07:30:00.545 [7412] DEBUG - There were 1 top-level paths for Van Helsing.
Nov 01, 2019 07:30:00.545 [7412] DEBUG - DVR:Grabber: Postprocessing, we’re going to putVan Helsing - E9 - Wakey, WakeyinE:\TV Shows\Van Helsing\Season 02\Van Helsing (2016) - S02E09 - Wakey Wakey.ts
Nov 01, 2019 07:30:00.546 [7412] DEBUG - DVR:Grabber: Moving “D:\TV Shows.grab\d53f8cfd042f6bd8fe570361bc09d000358605dc\Van Helsing (2016) - S02E09 - Wakey Wakey.ts” to “E:\TV Shows\Van Helsing\Season 02\Van Helsing (2016) - S02E09 - Wakey Wakey.ts”
Then some log entries for the 7:30 Van Helsing recording and it failed to start:
Nov 01, 2019 07:30:00.362 [9232] DEBUG - Job running: EAE_ROOT=‘\?\D:\Plex\Transcode\Sessions\EasyAudioEncoder’ FFMPEG_EXTERNAL_LIBS=‘C:\Users\Plex\AppData\Local\Plex\ Media\ Server\Plex\ Media\ Server\Codecs\395e79c-2735-windows-x86\’ X_PLEX_TOKEN=‘xxxxxxxxxxxxxxxxxxxx’ C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe -codec:0 mpeg2video -noaccurate_seek -live_start_index 0 -probesize 20000000 -i http://127.0.0.1:32400/livetv/sessions/013b3344-7155-4488-8982-20004ef1c54e/fbaeb523-d2de-40cc-b791-06ed759f828b/index.m3u8?offset=3597.800925&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx -map 0:0 -codec:0 copy -map 0:1 -metadata:s:1 language=eng -codec:1 copy -map 0:2 -metadata:s:2 language=spa -codec:2 copy -f mpegts -map_metadata -1 -map_chapters -1 “E:\TV Shows.grab\9a2abd3810e6521a863fbdb67bb6872ff6e64212\Van Helsing (2016) - S02E10 - Base Pair.ts” -y -nostats -loglevel quiet -loglevel_plex error -xioerror -progressurl http://127.0.0.1:32400/video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress
Nov 01, 2019 07:30:00.365 [9232] DEBUG - Jobs: Starting child process with pid 7036
Nov 01, 2019 07:30:00.447 [9328] DEBUG - Request: [127.0.0.1:60729 (Loopback)] PUT /video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress?status=startup (12 live) Signed-in Token (Shabashaly) (range: bytes=0-)
Nov 01, 2019 07:30:00.448 [10036] DEBUG - Completed: [127.0.0.1:60729] 204 PUT /video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress?status=startup (12 live) 0ms 203 bytes (pipelined: 1) (range: bytes=0-)
Nov 01, 2019 07:30:00.456 [0416] DEBUG - Request: [127.0.0.1:60729 (Loopback)] PUT /video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress?status=startup (12 live) Signed-in Token (Shabashaly) (range: bytes=0-)
Nov 01, 2019 07:30:00.457 [10036] DEBUG - Completed: [127.0.0.1:60729] 204 PUT /video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress?status=startup (12 live) 0ms 203 bytes (pipelined: 2) (range: bytes=0-)
Nov 01, 2019 07:30:00.457 [6068] DEBUG - Request: [127.0.0.1:60729 (Loopback)] PUT /video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress?status=opening (11 live) Signed-in Token (Shabashaly) (range: bytes=0-)
Nov 01, 2019 07:30:00.458 [10040] DEBUG - Completed: [127.0.0.1:60729] 204 PUT /video/:/transcode/session/fbaeb523-d2de-40cc-b791-06ed759f828b/2cfedbe0-7cb8-4611-9ac3-6e45a9c3cece/progress?status=opening (11 live) 0ms 203 bytes (pipelined: 3) (range: bytes=0-)
Nov 01, 2019 07:30:00.459 [11936] DEBUG - buildLiveM3U8: min 0 max 3597 ended 0
Nov 01, 2019 07:30:00.460 [9692] DEBUG - buildLiveM3U8: min 0 max 3597 ended 0
Nov 01, 2019 07:30:00.461 [9328] DEBUG - buildLiveM3U8: min 0 max 3597 ended 0
Nov 01, 2019 07:30:00.462 [12220] ERROR - [Transcoder] http://127.0.0.1:32400/livetv/sessions/013b3344-7155-4488-8982-20004ef1c54e/fbaeb523-d2de-40cc-b791-06ed759f828b/index.m3u8?offset=3597.800925&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx: End of file
Nov 01, 2019 07:30:00.467 [9328] DEBUG - buildLiveM3U8: ended due to segment 3597.781800 past end time 2019-11-01 11:30:00.000000000 +0000
Nov 01, 2019 07:30:00.469 [6324] DEBUG - Jobs: ‘C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe’ exit code for process 7036 is 1 (failure)
Nov 01, 2019 07:30:00.469 [9232] DEBUG - TranscodeSession: session failed while waiting for duration
Nov 01, 2019 07:30:00.470 [9232] ERROR - Failed to start session.
Nov 01, 2019 07:30:00.470 [2216] DEBUG - Streaming Resource: Terminated session 0xdbe3480:fbaeb523-d2de-40cc-b791-06ed759f828b with reason Recording failed. Please check your tuner or antenna.
Nov 01, 2019 07:30:00.470 [9232] ERROR - DVR:Recorder: Unable to create transcode session or session failed to start.
Then an error on the moving of the file for the 6:30 recording:
Nov 01, 2019 07:30:54.393 [7412] ERROR - DVR:Assimilator: Either section (2) or section location (2) didn’t exist.
Nov 01, 2019 07:30:54.393 [7412] DEBUG - DVR:Grabber: Operation for ‘Van Helsing - E9 - Wakey, Wakey’ on channel 680 completed with status error (The destination library or location did not exist)
So the really interesting part about the 6:30 recording is I recently added the E drive(so my TV show library has two drives it uses D and E drive) and through a couple accidental power downs I think some permissions got messed up on my C: which cause a whole bunch of wierd issues one of them being Plex would give me The destination library or location did not exist. What is wierd about it is if you do you look at the Log File you can see that is tries to move two grab separate files/folders and one of them does process correctly. What I found with that Error which isnt really an issue seems to resolve itself if I just switch whatever the default library was for the series recording. So I think at like around maybe 7 or 8 I probably switched the folder that the Series get saved to.
All that being said this has been an issue that has occurred long before the E: drive was added to the system. One thing that seems to be inconsistently consistent in the issue it usually occurs when there is back to back recordings on the same channel and the second recording is the one that fails. And what I mean by inconsistently consistent is that I dont always get this error on back to back recording but the only time I have ever gotten this error is on back to back recordings
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
