I am passing the evidence to our development team
Thankyou… of course I have to ask - any idea of how long it will take them to sort out this issue?
I am passing the evidence to our development team
Thankyou… of course I have to ask - any idea of how long it will take them to sort out this issue?
I do have the same thing on ALL THREE PMS… this is driving me nuts.
I am sorry I do not have such information - the pcap is good and it covers the time up to the failure. But you should be aware that the last time these errors arose was when Microsoft released a faulty windows 10 update on the 10th july 2018 which they addressed in a subsequent update on the 16th July 2018 - so there is a possibility that it is an OS issue and not Plex - but the evidence is now with the development team and we need to wait to see what is found and if it can overcome by changes to the transcoder
There are a number of different issues in this forum topic - all leading to the same top level error message. You posted just after a sequence of posts discussing this underlying error ERROR - [Transcoder] [stream_segment,ssegment @ 04ccb080] Failed to open segment list
This has only been seen on windows
Do get some logs and then we can see what is causing your failures
See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Please indicate what was being recorded / time of failure when attaching your logs zip file
Lets get some logs of the failures on 1.14.1.5488
Please indicate what time and what was being recorded
Thanks
See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
No failures on 5488. Please see earlier posts. …and Thank You for your help with this!
Sent the logs to you, a screenshot and some details…
I’ve got the antenna last week and jumped into this whole DVR thing, only to discover that recordings failed after half hour or so (faster if recording multiple streams).
I’m running Plex from official docker container on a computer with SSD primary drive (library is on separate NAS), in order to save SSD, I’ve had transcoder use ram (tmpfs) and usually haven’t had issues while streaming movies. I did notice that my transcoding folder did fill up during recording, even though the option to transcode the DVR was not used, whenever it got filled up, recording would fail.
Today I’ve switched transcoding folder to a much roomier USB 3.0 stick (256GB), so far so good, I was able to complete two simultaneous 1 hour recordings for the first time.
Question of the day: What is the size of your /transocde folder? It seems that, unlike for streaming, recording needs the full (high bandwidth) stream within /transcode folder to complete the recording.
DVR writes the MPEG2.ts segments off to disk before combining them into a container. An iterative process incase you want to remove commercials, optimize the video or on demand recording since it won’t know start or end. Ramdisk is not going to work well in this situation since it is trying to buffer in RAM and be the filesystem. High bit rate programs can use 6-9 GB per hour so I just point the transcoder directory to the tv storage 1 TB drive.
I’ve used everything from a laptop 5400 rpm drive to SSD, the laptop drive is more than adequate but a spinning disk is in you future. That or replace your USB stick when it fails.
I believe I’m in the same boat here. Last month I purchased the pass and setup some recordings. All of them failed within 15 minutes.
The machine that PMS is setup on is a Win 7 machine that is currently doing recordings via WMC. So I doubt is any kind of tuner or signal issue. But the tuner is a Hdhomerun prime.
I’ll need to check the logs to verify but I’m getting the same error with the recording.
I have encountered the same issue with 1.14 over the past few days. Reverting to 1.13 today seems to have fixed it. The typical chain of errors I encountered while trying to troubleshoot 1.14 this this afternoon can be found beginning at 15:31:19 in the attached media server log. Two “Unable to find title for item of type 5” errors, a “[Transcoder] http://127.0.0.1:32600/devices/dvb%23hdhr%231%23272345203/media/[...]: Server returned 404 Not Found” error, and then “ERROR - Failed to start session.” and “ERROR - DVR:Recorder: Unable to create transcode session or session failed to start.” Ubuntu 18.10 64 bit on an Intel i5 with an HDHomeRun Dual.Plex Media Server Logs_2018-12-24_16-30-47.zip (2.4 MB)
I wonder if this is related to a similar issue discussed in this thread:
However, the issue there doesn’t seem to be related to timeouts, because the “Playback was terminated by the server. Recording failed. Please check your tuner or antenna.” error comes up very quickly, and the channel tunes just fine when using Plex Web or PMP for Mac or PC.
Got the same “Recording failed. Please check your tuner or antenna” issue with Server version 1.14.1.5488.
I tried both on NVidia Shield and on Windows 10: most of my recordings fail with this error. This makes Plex DVR unusable for me.
I have an HDHomeRun Connect Duo Tuner (Firmware Version 20180817).
Antenna is directly attached to the tuner (no splitter), signal level is 100% and quality is also around 100% for most channels.
The same setup with the HDHomeRun app and its DVR service are able to tune within less than 2 seconds (compared to more than 10s with Plex) and there is no such issue with recordings.
Here are the logs:
Plex Media Server Logs_2018-12-24_10-18-38.zip (2.4 MB)
In the zip I joined the error details (see 12.xml).
This is all I captured from this event.
Got the same “Recording failed. Please check your tuner or antenna” issue
Would it be possible for you to provide the team with your logs as sa2000 described here?
The more information we can give the team, hopefully the sooner they can fix this issue. Every day I have multiple failed partial recordings. I’m over it.
Help!
Plex Media Server Logs_2018-12-27_15-44-40.zip (4.5 MB)
It seems to be working properly for me now. But I think I my recording issue may have been caused by a storage issue. Once I got the storage issue resolved the next recording was a full episode. I’m still on 1.14 using a hdhomerun prime.
same here with me…a chance (only a slight chance) recording will finish if i have one thing recording. 100% guaranteed both will fail if i have 2 simultaneously (HD home run silicon connect).
I went down to prior version to check what would happen…recordings all FINISH, but were more glitchy (i.e pixelation and missing of some video and audio)…prior to this, all my recordings were fine…and i mean positively fine. i convert them to MP4 and edit with iMovie. so i am quite aware of failure points.
the last 2 releases have seen complete degradation in recording, with the prior continuing on (i.e. not failing and blaming the tuner), but the most recent being great at identifying there is a problem…and stopping the recording!
There is no problem with my tuner, nor atenna.
i have just played with transcoder settings to have super fast, and to not use hardware transcoder.
If anything not using the hardware to transcode see’s it not fail as quickly.
But this is quite a bad time to have these updates degrade, as i had so many Xmas movies i wanted to record, and then there are so many holiday period movies on TV for the kids (here in Australia).
Looked at the logs. The logs don’t go back to the time of the scheduled recordings starting and failing and just cover the period after that or when you restarted the servers/
Are you sharing the DVR between 3 plex media servers ? I am not sure if this would be a supported configuration
I do see one server discovering the DVR but others failing
LECTER
Dec 20, 2018 23:15:53.036 [0xf13ffb90] DEBUG - DVR:Device: Discovering and refreshing all devices.
Dec 20, 2018 23:15:53.139 [0xf13ffb90] DEBUG - DVR:Device: Testing grabber Remote device device://tv.plex.grabbers.tunerservice/dvb%23sat2ip%23uuid%3a663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8 at http://192.168.94.254
Dec 20, 2018 23:15:53.140 [0xf13ffb90] DEBUG - DVR:Device: Device device://tv.plex.grabbers.tunerservice/dvb%23sat2ip%23uuid%3a663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8 was already known, refreshing database info
Dec 20, 2018 23:15:53.664 [0xf13ffb90] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.tunerservice/dvb%23sat2ip%23uuid%3a663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8, marking as dead.
SHIMANSKI
Dec 20, 2018 23:16:10.778 [0xf1ff7b90] DEBUG - DVR:Device: Discovering and refreshing all devices.
Dec 20, 2018 23:16:10.801 [0xf1ff7b90] DEBUG - DVR:Device: Testing grabber Remote device device://tv.plex.grabbers.tunerservice/dvb%23sat2ip%23uuid%3a663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8 at http://192.168.94.254
Dec 20, 2018 23:16:10.801 [0xf1ff7b90] DEBUG - DVR:Device: Device device://tv.plex.grabbers.tunerservice/dvb%23sat2ip%23uuid%3a663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8 was already known, refreshing database info
Dec 20, 2018 23:16:11.124 [0xf1ff7b90] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.tunerservice/dvb%23sat2ip%23uuid%3a663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8, marking as dead.
I need to establish if we can support sharing of DVR between servers.
With regards to logs not covering time of failures, see advanced server settings
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
and the preference/setting LogNumFiles
There is overlap of tuners between the servers - this complicates investigations of issues and a DVR is expected to be dedicated to a Plex Media Server
LECTER is referencing tuners sat2ip#0 and sat2ip#1
SHIMANSKI referencing sat2ip#2 and sat2ip#3
POIROT referencing sat2ip#1
Thanks for your suggestion.
I added the logs to my original post.
I hope this will help!