If you have not already, we suggest setting your Plex username to something else rather than email which is displayed on your posts in forum. You can change the username at https://app.plex.tv/desktop#!/account
Welcome to our forums! Please take a few moments to read through our Community Guidelines (also conveniently linked in the header at the top of each page). There, you'll find guidelines on conduct, tips on getting the help you may be searching for, and more!

Latest Roku Firmware Release Broke Plex

Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass
edited August 10 in Roku

I have eight (!) Roku 3's. Updated all with latest Roku release yesterday (Sunday, 7-30-2017.) New Roku version is 7.7.0, build 4116-04. I have the latest (as of 7-31-2017) Plex Pass version running on Windows 7. Some movies are unable to play at all. "We are unable to play this video..." Others, after 30-45 minutes of play, the screen breaks up and the Roku is frozen. This is definitely new with this Roku load. It did not happen before. I have noticed -no- failures on other Roku channels, including Tablo, Netflix, MLB.tv, etc.

Tagged:
«13

Comments

  • Elijah_BaleyElijah_Baley Posts: 4,365Members, Plex Pass Plex Pass

    I have multiple Rokus and I am updated to the latest firmware but I have seen none of the problems you are listing. My Rokus+Plex are all pretty much rock solid. I think something else is going on. I believe that what you have is a case of the "Post hoc ergo propter hoc" falicy.

    To diagnose your problem the experts are going to need more info like details of your network setup and how everything is connected. Also log files from your server and your Roku from right after a failure happens.

    With that info there are a lot of people that very well might be able to help find what has changed or been introduced that is causing the problems you are seeing.

    Plex has lost me! I am moving all my local media consumption to Emby. There are things about Plex that are better than Emby but Plex has begun misleading their customers and even telling their users bald faced lies and that is unacceptable so I no longer use Plex for any media consumption.
    I will NOT be lied to by a company I have any choice about using.
    It has been a good ride but I now feel that I am the one being ridden.
    Emby is NOT better software but they are a better company at this point.

  • ChuckPAChuckPA Posts: 16,850Members, Plex Pass, Plex Ninja, Plex Team Member Plex Team Member

    @Uncle 9 said:
    I have eight (!) Roku 3's. Updated all with latest Roku release yesterday (Sunday, 7-30-2017.) New Roku version is 7.7.0, build 4116-04. I have the latest (as of 7-31-2017) Plex Pass version running on Windows 7. Some movies are unable to play at all. "We are unable to play this video..." Others, after 30-45 minutes of play, the screen breaks up and the Roku is frozen. This is definitely new with this Roku load. It did not happen before. I have noticed -no- failures on other Roku channels, including Tablo, Netflix, MLB.tv, etc.

    Would you please recreate the problem on one Roku (with nothing else streaming) then go to Settings - Server - Help - Download Logs and upload that ZIP file here?

    I will look at it first and if need be can get the Roku team on it. I am playing on my Roku 3 as well and see no issues with firmware 7.7.0 build 4116-04

    Please DISABLE Verbose logging until requested

    Please search before posting

    Primary support forums: Linux, Synology, and QNAP

    Please remember to report back. This benefits others.

    Useful links

     Installation and Basic Setup |  Media Preparation (How to name your media files)  |  Linux Permissions 

     Handling TV Specials | Handling Movie extras  |  Nas Compatibility List

     Reporting Plex Server issues | Plex Media Server FAQ | Linux Tips

     

    Other useful guides: Local Subtitles | The Plex "dance" | Synology FAQ | PMS Release Announcements

    No technical support via PM unless offered

    Please remember to mark the appropriate answer(s) which solved your issue.

     
  • drinehartdrinehart Posts: 1,152Members, Plex Pass Plex Pass

    Just as another data point, I have 3 of the Roku 2 (2015) model (same hardware as Roku 3) and none of them exhibit the behavior described by the OP. Not that I am necessarily doubting OP, I just cannot corroborate that right now.

  • dragonmeldragonmel Posts: 622Members, Plex Pass Plex Pass

    why do people never state version numbers of the server and other details in thier posts.... since this is a front end, back end, design it just might be important.. no....

  • ChuckPAChuckPA Posts: 16,850Members, Plex Pass, Plex Ninja, Plex Team Member Plex Team Member

    Because if it's truly a Roku firmware issue, PMS firmware will not be relevant but for the record,

    Tested on PMS 1.7.5, 1.7.6 and 1.8.0

    @Uncle 9

    If you can attempt to play and then pull the Roku logs. https://support.plex.tv/hc/en-us/articles/201377603

    Whatever is going sideways for you will show there.

    Please DISABLE Verbose logging until requested

    Please search before posting

    Primary support forums: Linux, Synology, and QNAP

    Please remember to report back. This benefits others.

    Useful links

     Installation and Basic Setup |  Media Preparation (How to name your media files)  |  Linux Permissions 

     Handling TV Specials | Handling Movie extras  |  Nas Compatibility List

     Reporting Plex Server issues | Plex Media Server FAQ | Linux Tips

     

    Other useful guides: Local Subtitles | The Plex "dance" | Synology FAQ | PMS Release Announcements

    No technical support via PM unless offered

    Please remember to mark the appropriate answer(s) which solved your issue.

     
  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass
    edited August 1

    NO OTHER ROKU CHANNEL is messed up. Only Plex. My vids are freezing and causing the Roku to reboot after 30 or 45 or, at most, 60 minutes. For the log file zip I attached here, the breakup and freeze started 38 minutes after the movie (Patriot Games) started.

  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass

    @Elijah_Baley said:
    I have multiple Rokus and I am updated to the latest firmware but I have seen none of the problems you are listing. My Rokus+Plex are all pretty much rock solid. I think something else is going on. I believe that what you have is a case of the "Post hoc ergo propter hoc" falicy.

    You posted this "reply" and "ridicule" (Post hoc ergo propter hoc, which I'm guessing you learned watching "West WIng) exactly TWELVE minutes after I made the OP. I clearly stated that the problem happpens 30-45-60 minutes -after- the movie or vid starts. I have repeated this multiple times since yesterday. The log files I sent were from an occurrence 38 minutes into a movie. So, your "post" was not "propter," was it?

  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass

    Would you please recreate the problem on one Roku (with nothing else streaming) then go to Settings - Server - Help - Download Logs and upload that ZIP file here?

    I will look at it first and if need be can get the Roku team on it. I am playing on my Roku 3 as well and see no issues with firmware 7.7.0 build 4116-04

    Attached log files. Movie (Patriot Games) froze 38 minutes in to the move.

  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass

    @ChuckPA said:
    Because if it's truly a Roku firmware issue, PMS firmware will not be relevant but for the record,

    Tested on PMS 1.7.5, 1.7.6 and 1.8.0

    I believe it certainly IS a PMS issue if NO other Roku channel (I have 21 Roku channels) is exhibiting this problem. Do you not agree? Only PMS is failing out of 21 channels? I have looked at ALL of them--NTF with any except PMS. "PMS firmware will not be relevant????"

  • ChuckPAChuckPA Posts: 16,850Members, Plex Pass, Plex Ninja, Plex Team Member Plex Team Member

    @Uncle 9

    I'm looking at your logs right now. The log files you provided do not show any evidence of anything playing for 35-40 minutes as your OP states.

    This is from Plex Media Server.log. The size of this file is 35 KB. It is impossible to stream in this short a log file

    It is the first entry for PMS 1.8.0

    Jul 31, 2017 12:09:50.607 [3864] INFO - Plex Media Server v1.8.0.4109-42bd8c63f - Microsoft PC x64 - build: windows-i386 english - GMT -05:00
    Jul 31, 2017 12:09:50.622 [3864] INFO - Windows version: 6.1 (Build 7601), language en-US
    

    Plex Media Server.1.log is 27.8 KB in length and shows me evidence of a corrupted database and/or an overloaded machine but no evidence of having played video for

    Jul 31, 2017 11:23:56.702 [3424] INFO - Plex Media Server v1.8.0.4109-42bd8c63f - Microsoft PC x64 - build: windows-i386 english - GMT -05:00
    Jul 31, 2017 11:23:56.702 [3424] INFO - Windows version: 6.1 (Build 7601), language en-US
    Jul 31, 2017 11:23:56.702 [3424] INFO - 4 3093 MHz processor(s): Architecture=0, Level=6, Revision=10759 Processor Identifier=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
    Jul 31, 2017 11:23:58.137 [6488] ERROR - SetForegroundWindow failed: 0x0
    Jul 31, 2017 11:23:58.761 [5820] WARN - Held transaction for too long (..\Library\FullTextSearch.cpp:17): 0.156001 seconds
    Jul 31, 2017 11:24:08.885 [5820] WARN - Held transaction for too long (..\Library\FullTextSearch.cpp:27): 0.109201 seconds
    Jul 31, 2017 11:24:10.320 [5820] WARN - Held transaction for too long (..\Library\FullTextSearch.cpp:38): 0.452403 seconds
    Jul 31, 2017 11:24:11.022 [5820] WARN - Held transaction for too long (..\Library\FullTextSearch.cpp:48): 0.249602 seconds
    Jul 31, 2017 11:24:11.022 [5820] WARN - Held transaction for too long (..\Library\DatabaseMigrations.cpp:195): 0.967206 seconds
    Jul 31, 2017 11:24:24.438 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 31, 2017 11:24:24.453 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 31, 2017 11:24:24.453 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 31, 2017 11:24:24.453 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 31, 2017 11:24:24.453 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 31, 2017 11:24:24.469 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 31, 2017 11:24:24.469 [5820] INFO - SQLITE3:1D9FCE01, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    

    Ending with:

    Jul 31, 2017 11:26:36.850 [6924] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
    Jul 31, 2017 11:26:36.850 [6924] WARN - Failed to obtain a streaming resource for transcode of key /library/metadata/68297
    Jul 31, 2017 11:26:37.271 [7492] ERROR - MDE: video has neither a video stream nor an audio stream
    Jul 31, 2017 11:26:37.271 [7492] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
    Jul 31, 2017 11:26:37.271 [7492] WARN - Failed to obtain a streaming resource for transcode of key /library/metadata/68297
    Jul 31, 2017 11:26:37.771 [3044] ERROR - MDE: video has neither a video stream nor an audio stream
    Jul 31, 2017 11:26:37.771 [3044] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
    Jul 31, 2017 11:26:37.771 [3044] WARN - Failed to obtain a streaming resource for transcode of key /library/metadata/68297
    Jul 31, 2017 11:26:38.067 [5752] WARN - Got a request to stop a transcode session without a session GUID (or with an invalid one).
    

    Please DISABLE Verbose logging until requested

    Please search before posting

    Primary support forums: Linux, Synology, and QNAP

    Please remember to report back. This benefits others.

    Useful links

     Installation and Basic Setup |  Media Preparation (How to name your media files)  |  Linux Permissions 

     Handling TV Specials | Handling Movie extras  |  Nas Compatibility List

     Reporting Plex Server issues | Plex Media Server FAQ | Linux Tips

     

    Other useful guides: Local Subtitles | The Plex "dance" | Synology FAQ | PMS Release Announcements

    No technical support via PM unless offered

    Please remember to mark the appropriate answer(s) which solved your issue.

     
  • ChuckPAChuckPA Posts: 16,850Members, Plex Pass, Plex Ninja, Plex Team Member Plex Team Member
    edited July 31

    To prevent the post from being too long, here is Plex Media Server.2.log (the predecessor to .1.log)

    There is a corruption on your system. Am i correct today is the first PMS has been started since 17 July?

    Jul 17, 2017 18:20:48.836 [3852] INFO - Plex Media Server v1.7.6.4058-8fa494d15 - Microsoft PC x64 - build: windows-i386 english - GMT -05:00
    Jul 17, 2017 18:20:48.836 [3852] INFO - Windows version: 6.1 (Build 7601), language en-US
    Jul 17, 2017 18:20:48.836 [3852] INFO - 4 3093 MHz processor(s): Architecture=0, Level=6, Revision=10759 Processor Identifier=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
    Jul 17, 2017 18:20:49.148 [4888] ERROR - SetForegroundWindow failed: 0x0
    Jul 17, 2017 18:20:49.756 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.756 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.756 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.756 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.772 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.772 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.772 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.772 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.787 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.787 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.787 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.787 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:49.803 [5220] INFO - SQLITE3:0E8F8E7A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
    Jul 17, 2017 18:20:51.613 [5916] WARN - Couldn't determine bundle identifier for plug-in at: C:\Users\admin\AppData\Local\Plex Media Server\Plug-ins\Framework.bundle
    Jul 17, 2017 18:20:51.613 [5916] WARN - Couldn't determine bundle identifier for plug-in at: C:\Users\admin\AppData\Local\Plex Media Server\Plug-ins\LastFM.bundle
    

    Edit: Please turn on Debug logging in Settings - Server - General.

    Please DISABLE Verbose logging until requested

    Please search before posting

    Primary support forums: Linux, Synology, and QNAP

    Please remember to report back. This benefits others.

    Useful links

     Installation and Basic Setup |  Media Preparation (How to name your media files)  |  Linux Permissions 

     Handling TV Specials | Handling Movie extras  |  Nas Compatibility List

     Reporting Plex Server issues | Plex Media Server FAQ | Linux Tips

     

    Other useful guides: Local Subtitles | The Plex "dance" | Synology FAQ | PMS Release Announcements

    No technical support via PM unless offered

    Please remember to mark the appropriate answer(s) which solved your issue.

     
  • Elijah_BaleyElijah_Baley Posts: 4,365Members, Plex Pass Plex Pass

    @Uncle 9 said:

    @Elijah_Baley said:
    I have multiple Rokus and I am updated to the latest firmware but I have seen none of the problems you are listing. My Rokus+Plex are all pretty much rock solid. I think something else is going on. I believe that what you have is a case of the "Post hoc ergo propter hoc" falicy.

    You posted this "reply" and "ridicule" (Post hoc ergo propter hoc, which I'm guessing you learned watching "West WIng) exactly TWELVE minutes after I made the OP. I clearly stated that the problem happpens 30-45-60 minutes -after- the movie or vid starts. I have repeated this multiple times since yesterday. The log files I sent were from an occurrence 38 minutes into a movie. So, your "post" was not "propter," was it?

    My post was not only proper it was relevant. The time I posted after you posted was not meaningful any more than the exact time you posted was relevant.
    My Rokus give me no problems like you describe.
    Everyone I know that has Roku have no problems like you describe.
    The Roku forums do not seem to have any reports of problems like you describe.
    Therefore it seems that it is NOT the Roku firmware or the Plex software that are causing you problems it must be something somewhat unique to something in your setup.

    The logs you provided may allow someone here to see what the problem might be as there are some here with great knowledge of what the log entries mean and from that help you fix what is wrong.

    BTW: I have never watched "West Wing" and I get my knowledge form these things called "books" while TV and movies are strictly entertainment.

    Also in case you don't know "Post hoc ergo propter hoc" is a statement of a common logic mistake where it is assumed that just because event B happens after event A then event B was caused by event A when actually the two have no real relationship.
    What I was saying is that I believe the latest release of Plex's Roku client or Roku's latest firmware have nothing to do with the problems you are having even though you are experiencing the problem after the new software was installed.

    Plex has lost me! I am moving all my local media consumption to Emby. There are things about Plex that are better than Emby but Plex has begun misleading their customers and even telling their users bald faced lies and that is unacceptable so I no longer use Plex for any media consumption.
    I will NOT be lied to by a company I have any choice about using.
    It has been a good ride but I now feel that I am the one being ridden.
    Emby is NOT better software but they are a better company at this point.

  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass

    In this log file, the breakup happened 7:37 after movie (Sully) started.

  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass

    I have 4 PMS servers. For backup and to separate media types. They are ALL exhibiting the same behavior. The attached logfile is from another server, same movie (Sully) and the breakup/freeze occurred at 25:47.

  • ChuckPAChuckPA Posts: 16,850Members, Plex Pass, Plex Ninja, Plex Team Member Plex Team Member

    From this I see evidence of corrupted / invalid media. The scanner is very forgiving but the MDE (Media Decision Engine) cannot make a decision, the file is a problem. Kindly notice the proximity to, but prior to actual, attempt to playback on the Roku.

    From earlier in the day, Plex Media Server.log

    Jul 31, 2017 12:10:34.531 [3940] DEBUG - MDE: analyzing media item 263712
    Jul 31, 2017 12:10:34.562 [3940] ERROR - MDE: video has neither a video stream nor an audio stream
    Jul 31, 2017 12:10:34.562 [3940] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
    Jul 31, 2017 12:10:34.562 [2968] DEBUG - Completed: [192.168.1.9:49795] 400 GET /video/:/transcode/universal/decision (17 live) TLS GZIP 339ms 384 bytes (pipelined: 1)
    Jul 31, 2017 12:10:34.811 [2848] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
    Jul 31, 2017 12:10:34.811 [2848] DEBUG - Auth: authenticated user 1 as Uncle 9
    Jul 31, 2017 12:10:34.811 [2848] DEBUG - Auth: Came in with a super-token, authorization succeeded.
    Jul 31, 2017 12:10:34.811 [3952] DEBUG - Request: [192.168.1.9:49775 (Subnet)] GET /:/timeline?time=0&duration=8220000&key=%2Flibrary%2Fmetadata%2F76296&ratingKey=76296&state=buffering&guid=com.plexapp.agents.imdb%3A%2F%2Ftt3315342%3Flang%3Den&playQueueItemID=12072 (18 live) TLS GZIP Signed-in Token (Uncle 9)
    Jul 31, 2017 12:10:34.811 [3952] DEBUG - Client [bb4c7e0132a31fdb0d44924d6488b0f9] reporting timeline state buffering, progress of 0/8220000ms for guid=com.plexapp.agents.imdb://tt3315342?lang=en, ratingKey=76296 url=, key=/library/metadata/76296, containerKey=, metadataId=76296
    Jul 31, 2017 12:10:34.843 [3952] DEBUG - [Now] User is Uncle 9 (ID: 1)
    Jul 31, 2017 12:10:34.843 [3952] DEBUG - [Now] Device is Roku (Roku 3 - 1GN39X111420).
    Jul 31, 2017 12:10:34.843 [3952] DEBUG - [Now] Profile is Roku-7.x
    

    Very shortly thereafter, I find

    Jul 31, 2017 12:10:34.858 [2636] DEBUG - Media Analyzer: Performing on-the-fly analysis on 1 item.
    Jul 31, 2017 12:10:34.858 [2636] DEBUG - Job running: EAE_ROOT='\\?\C:\Users\BillyBob\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\EasyAudioEncoder' FFMPEG_EXTERNAL_LIBS='\\\\?\\C\:\\Users\\BillyBob\\AppData\\Local\\Plex\ Media\ Server\\Codecs\\0affb08-1243-windows-i386\\' X_PLEX_TOKEN='xxxxxxxxxxxxxxxxxxxx' C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe --analyze --log-file-suffix " Analysis" --item 76296 
    Jul 31, 2017 12:10:35.061 [2968] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
    Jul 31, 2017 12:10:35.061 [2968] DEBUG - Auth: Came in with the master token, authorization succeeded.
    Jul 31, 2017 12:10:35.061 [3940] DEBUG - Request: [127.0.0.1:49484 (Loopback)] GET /library/changestamp (18 live) GZIP Signed-in Token (Uncle 9)
    Jul 31, 2017 12:10:35.077 [2848] DEBUG - Completed: [127.0.0.1:49484] 200 GET /library/changestamp (18 live) GZIP 1ms 468 bytes
    Jul 31, 2017 12:10:35.092 [2968] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
    Jul 31, 2017 12:10:35.092 [2968] DEBUG - Auth: Came in with the master token, authorization succeeded.
    Jul 31, 2017 12:10:35.092 [3932] DEBUG - Request: [127.0.0.1:49485 (Loopback)] GET /:/metadata/notify/changeItemState?librarySectionID=3&metadataItemID=76296&metadataType=1&state=-1&mediaState=analyzing (19 live) GZIP Signed-in Token (Uncle 9)
    Jul 31, 2017 12:10:35.092 [2848] DEBUG - Completed: [127.0.0.1:49485] 200 GET /:/metadata/notify/changeItemState?librarySectionID=3&metadataItemID=76296&metadataType=1&state=-1&mediaState=analyzing (19 live) GZIP 0ms 166 bytes
    Jul 31, 2017 12:10:35.108 [2968] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
    Jul 31, 2017 12:10:35.108 [2968] DEBUG - Auth: Came in with the master token, authorization succeeded.
    Jul 31, 2017 12:10:35.108 [3932] DEBUG - Request: [127.0.0.1:49486 (Loopback)] GET /:/metadata/notify/changeItemState?librarySectionID=3&metadataItemID=76296&metadataType=1&state=-1&mediaState=thumbnailing (20 live) GZIP Signed-in Token (Uncle 9)
    Jul 31, 2017 12:10:35.108 [2848] DEBUG - Completed: [127.0.0.1:49486] 200 GET /:/metadata/notify/changeItemState?librarySectionID=3&metadataItemID=76296&metadataType=1&state=-1&mediaState=thumbnailing (20 live) GZIP 0ms 166 bytes
    Jul 31, 2017 12:10:35.123 [2968] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
    Jul 31, 2017 12:10:35.123 [2968] DEBUG - Auth: Came in with the master token, authorization succeeded.
    Jul 31, 2017 12:10:35.123 [3932] DEBUG - Request: [127.0.0.1:49487 (Loopback)] GET /:/metadata/notify/changeItemState?librarySectionID=3&metadataItemID=76296&metadataType=1&state=-1&mediaState=idle (21 live) GZIP Signed-in Token (Uncle 9)
    Jul 31, 2017 12:10:35.123 [2848] DEBUG - Completed: [127.0.0.1:49487] 200 GET /:/metadata/notify/changeItemState?librarySectionID=3&metadataItemID=76296&metadataType=1&state=-1&mediaState=idle (21 live) GZIP 0ms 166 bytes
    Jul 31, 2017 12:10:35.123 [2636] DEBUG - Killing job.
    Jul 31, 2017 12:10:35.123 [2636] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe' exit code for process 4708 is 0
    Jul 31, 2017 12:10:35.123 [2636] DEBUG - Media Analyzer: Background analysis completed in 0.3 seconds, removing 1 IDs
    Jul 31, 2017 12:10:35.139 [3952] DEBUG - Streaming Resource: Attempting to create AdHoc transcode session bb4c7e0132a31fdb0d44924d6488b0f9
    Jul 31, 2017 12:10:35.139 [3952] DEBUG - MDE: analyzing media item 263712
    Jul 31, 2017 12:10:35.139 [3952] ERROR - MDE: video has neither a video stream nor an audio stream
    Jul 31, 2017 12:10:35.139 [3952] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
    Jul 31, 2017 12:10:35.139 [3952] WARN - Failed to obtain a streaming resource for transcode of key /library/metadata/76296
    

    If these two times correspond to playing the same movie, I assert to you the file is damaged. as it has no discernible Video or Audio stream. (12:10:35.139)

    If all your files are behaving this way, Please look elsewhere while I get someone else to look at your logs. I suggest you get the previous version of PMS (PMS keeps the last 3 versions for you) and roll back. Then repeat with the same test file.

    Nothing here identifies problems with the Roku in any way at this time. All issues are occurring prior to playback when the MDE is determining what to do with the media.

    Please DISABLE Verbose logging until requested

    Please search before posting

    Primary support forums: Linux, Synology, and QNAP

    Please remember to report back. This benefits others.

    Useful links

     Installation and Basic Setup |  Media Preparation (How to name your media files)  |  Linux Permissions 

     Handling TV Specials | Handling Movie extras  |  Nas Compatibility List

     Reporting Plex Server issues | Plex Media Server FAQ | Linux Tips

     

    Other useful guides: Local Subtitles | The Plex "dance" | Synology FAQ | PMS Release Announcements

    No technical support via PM unless offered

    Please remember to mark the appropriate answer(s) which solved your issue.

     
  • OttoKernerOttoKerner Posts: 25,180Members, Plex Pass, Plex Ninja Plex Ninja

    I am no Roku expert, but I see that the encrypted connection was broken with some kind of TLS-related error, just prior to the playback stop occuring.
    Just for the sake of experimentation, can you try and disable 'Secure Connections'
    (Settings - Server - Network , restart Plex server after changing this setting)

    Help others too - by reporting back with your results!
    Have you checked the Documentation before posting a question in the forums?
    Use the SEARCH function before starting a new thread!
    No PMs unless requested, please! Do not use 'verbose' logging
  • Elijah_BaleyElijah_Baley Posts: 4,365Members, Plex Pass Plex Pass

    @OttoKerner said:
    I am no Roku expert, but I see that the encrypted connection was broken with some kind of TLS-related error, just prior to the playback stop occuring.
    Just for the sake of experimentation, can you try and disable 'Secure Connections'
    (Settings - Server - Network , restart Plex server after changing this setting)

    That actually might be a very good guess. I run with "Allow insecure connections set to "On the same network" (I used to use "Always" but that causes other problems) and on my server I have secure connections disabled. (I also disable remote access.)

    The fact that I do not use secure connections just might be why I see no problems at all.

    Plex has lost me! I am moving all my local media consumption to Emby. There are things about Plex that are better than Emby but Plex has begun misleading their customers and even telling their users bald faced lies and that is unacceptable so I no longer use Plex for any media consumption.
    I will NOT be lied to by a company I have any choice about using.
    It has been a good ride but I now feel that I am the one being ridden.
    Emby is NOT better software but they are a better company at this point.

  • ChuckPAChuckPA Posts: 16,850Members, Plex Pass, Plex Ninja, Plex Team Member Plex Team Member

    Thanks Otto and Elijah.. I just checked on this Roku 3 with Required (was Preferred) and have no playback issue.
    This having been said, the TLS errors are probably the reason.

    Please DISABLE Verbose logging until requested

    Please search before posting

    Primary support forums: Linux, Synology, and QNAP

    Please remember to report back. This benefits others.

    Useful links

     Installation and Basic Setup |  Media Preparation (How to name your media files)  |  Linux Permissions 

     Handling TV Specials | Handling Movie extras  |  Nas Compatibility List

     Reporting Plex Server issues | Plex Media Server FAQ | Linux Tips

     

    Other useful guides: Local Subtitles | The Plex "dance" | Synology FAQ | PMS Release Announcements

    No technical support via PM unless offered

    Please remember to mark the appropriate answer(s) which solved your issue.

     
  • Uncle 9Uncle 9 Posts: 175Members, Plex Pass Plex Pass

    I have just changed "Secure Connections" to "Disabled" on my 4 servers. (There are a ton of settings on the "Network" page and I forgot to click "Save Changes" the first time I went through. So it never took. Remind everyone to do that when they make a change.) I have re-booted the servers and am running a test film now. I will post again. (I don't need Transport Layer Security, or Secure Connections, as I only use Plex locally.) I am only ten minutes into the test, but I can tell you that files are loading faster (maybe 2x) than they did with "Secure Connections" either "Required" or "Preferred." My imagination?

    If Otto is truly a genius, and this fixes the problem, does anyone feel, as I do, that something in the latest Roku drop, regarding secure connections, changed, and broke the Plex TLS process?

  • jkallandjkalland Posts: 549Members, Plex Pass Plex Pass

    Roku Firmware 7.7 is a joke, and it's not just Plex. Netflix, Amazon, Plex....they all broke for older Roku devices. I rolled back to 7.6 using the "secret menu" and all is well. Seems how broken it is varies a lot by Roku SKU, but for me nothing would play beyond 15-20 minutes without freezing, turning into green pixelated mess...but the audio kept going. That, or it'd just hard reboot on the netflix menu whenever one of those preview videos started. Some folks had luck dropping to 720p from 1080p to fix it on the Roku forums, but not all.

    If I had to guess, they mangled the HDCP handshake and it's as much a device/screen issue as it is anything else.

    Netgear Nighthawk R7000 Router + HP ProCurve gig-E switch
    WD My Book Live 1 TB "NAS"
    Dell 3010 Chromebox running Ubuntu 14.04 LTS w/ PMS, TVHeadend (OTA Antenna), and Kodi (Jarvis) wired to the ProCurve (...and with a 1 TB USB3 pocket drive literally taped on top of it)
    Roku 3 (the original 3) wired to the ProCurve
    Roku 3 (2015ish refurb) wired to the Nighthawk (RIP Roku XD)

«13
Sign In or Register to comment.