Thank you - i have passed the information on.
Over 20 seconds is a bit excessive for a tune to complete
Thanks, I appreciate you working on this.
We are looking into the timeouts - but find it difficult to comprehend why an HD Homerun needs over 20 seconds to tune a channel - normally such issues are due to signal
I like to establish what proportion of tunes on HD Homerun fail due to timeout after 20 seconds on starting to tune.
To identify this failure, logs would have a log entry for tuning, eg
POST /livetv/dvrs/4/channels/1463/tune
followed 20 seconds later with this timeout error
TranscodeSession: timed out waiting to find duration for live session
The diagnostics you provided was just one log file which only had one tune.
You mentioned that it was ok in 1.13.9 - could you confirm that this is still the case -
what i am after is seeing lots of examples of channel tuning with 1.14.1.5487 and also with 1.13.9 where the timeout period was more than 20 seconds. There should be no reason for an HD Homerun to take more than 20 seconds to tune. So would like to see confirmation with logs of tunes now on 1.13…9 and also on same day on 1.14.1 where we can assume signal remains the same between tests - of course tests on the 2 versions need to be for the same channels - like for like
Thank you
Just adding my logs here too. There were two examples here, both times in the log file it says:
“av_interleaved_write_frame(): Unknown error”. I know this is also a generic issue and the logs need to be reviewed to determine the issue.
This was happening with Windows version 1.13.9.5456 but is happening with newer versions too.Plex Media Server.2.log (4.5 MB)
Plex Media Server.log (813.0 KB)
The last time such errors were widespread was when Microsoft released a faulty windows 10 update on 10th July 2018 which they subsequently corrected in the July 16th Update - but the impact remained widespread for months after.
The problem manifests itself in loopback request failures and logging of errors like these
Nov 26, 2018 19:08:37.660 [10512] ERROR - [Transcoder] [stream_segment,ssegment @ 04ccb080] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/ba2d6b30-8b9a-48aa-952b-b166e3228b76/98fcd8a7-3bc0-4491-a091-a6003569532b/seglist'
Nov 26, 2018 19:08:37.660 [8656] ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
Nov 26, 2018 19:08:37.660 [10512] ERROR - [Transcoder] Error writing trailer of media-%05d.ts: Invalid argument
It is very possible that there has been a further update to windows that brought this problem on. So first advice is to check for windows updates - not just critical updates
If that does not resolve, then would need to see if we can capture packets between the transcoder and plex media server that come in through 127.0.0.1
Also you had debug logging disabled on the server - you would need to enable it and for transcoder issues would also need verbose logging - but that would mean you need to capture logs immediately after the failure as each log file may fill up in 5 minutes with verbose logging
To capture traffic through 127,0,0.1 there is a very easy to use program - RawCap.exe which can be used.
See my post here on the subject SOLUTION: Conversion failed. The transcoder exited due to an error - #307 by sa2000
1 Like
I do have a development build i can make available to you with increased timeout - but i would really want to understand the scale of the problem first and also that it is clear in 1.13.9 - so please could you get me the logs for more tuning examples on 1.14.1 and also of it not timing out on 1.13.9
(and please let me know which install package you need)
If that does not resolve, then would need to see if we can capture packets between the transcoder and plex media server that come in through 127.0.0.1
Also you had debug logging disabled on the server - you would need to enable it and for transcoder issues would also need verbose logging - but that would mean you need to capture logs immediately after the failure as each log file may fill up in 5 minutes with verbose logging
Cool - OK. First thing: no updates available, windows is up-to-date.
Here are some log files - I kept a few extra ones just in case, but the issue occurs in Plex Media Server.2.Log at Dec 15, 2018 13:10:17.536.
Logs.zip (2.1 MB)
The pcap file is really large (1.2G) really sorry… I’ve uploaded it to google drive though, it’s here: (removed)
[EDIT]: I’m no expert at PCAP files, but I think the issue might occur around 2426 secs. It’s almost bang on from the file creation date to the time of the logged error (which is 2432), and after 2426 there’s significantly less logging (ie from 2427 onwards).
I’m getting the same recording failings even after upgrading to 1.14.1.5487.
Windows 10 is up-to-date with 1809.
Using HDHomeRun version 20180817.
Let me know if I can help.
Using HDHomeRun version 20180817.
I’m also using 20180817.
This issue is getting worse and worse. I can’t record anything now without it stopping with this error. Nothing records fully.
The timeouts got increased now to 25-30 seconds in beta release 1.14.1.5488
See Plex Media Server - #242 by StSimm1
- (DVR) Revert timeout changes, should help with timeouts during tune startup (#9473)
The timeouts got increased now to 25-30 seconds in beta release 1.14.1.5488
Could I just confirm - this isn’t related to my issue, is it…?
Same thing here for me. And I messed with both of my antennas for my HDHomerun Quattro and Extend. Now The reception is even worse than before.
I do not understand why PLEX has more problems tuning that using the Silicon DVR software
I should have known better than to update my server software today…especially when it mentioned that they had messed with the “DVR scheduler”…which for me was working fine. I had two recordings scheduled tonight starting at 8…at 8:15 I noticed that both had failed with the notice to check my antenna. Well, my antenna is working fine as was Plex DVR until I updated (stupid…I’m so stupid! I know better than to update for at least a few days after it comes out). I was able to tune both channels fine…though I still went ahead and did a channel re-scan. After some fussing I was able to restart the recording that I cared about most. So that’s good I guess. But there are obviously some bugs with this “New DVR Scheduler”.
1 Like
Should not jump to conclusions. Only way to identify issues is through debug logs
It is not related to the specific errors you had. However, increased timeout period would be better
Hoping to look st your logs and pcap later today
1 Like
Hoping to look st your logs and pcap later today
Awesome, thankyou!
Last night installed 1.14.1.5488 and it looks like that solved the problem.
Yeah… that didn’t help me. I think my issue is different.
[EDIT] Although, it appears that whilst a show I recorded did error after 5 minutes (and therefore appeared in my library afterwards), I deleted it and THEN it continued recording! Is this some new functionality? Or is it because I deleted the 5 minute-long failed recording?
Thank you for the loopback capture and the logs. They do capture the sequence. I am passing the evidence to our development team - please leave the pcap on the linked google drive. I will remove the link from the forum post
