Hi!
I don’t believe it was the 1.1.4 version the last one working, but right before 1.2.5. It looks like something related to bug fixes #5620 or #5703. We’re using this one because nobody can found a fresher one and the Plex staff, which already was warned, ignored us when we asked for a valid link to newer versions.
Thanks @ananke !
Do we have a bug number assigned to this yet? It seems that the number of reports, and repeatability of this issue should be sufficient to get something going.
@ananke said:
Do we have a bug number assigned to this yet? It seems that the number of reports, and repeatability of this issue should be sufficient to get something going.
The problem is still not identified - but i have escalated it.
In the meantime, suggest moving now to the latest version which is now 1.3.2.3112
@sa2000 said:
@ananke said:
Do we have a bug number assigned to this yet? It seems that the number of reports, and repeatability of this issue should be sufficient to get something going.The problem is still not identified - but i have escalated it.
Perhaps I’m not familiar with how Plex development cycle and support system works; however, this problem has all the typical characteristics that would qualify for a bug number: software regression, affecting multiple users and systems, repeatable, and can be pinpointed to a specific release.
Based on reports of others, it may be introduced in 1.2.5. If there was an easier access to historical releases, I would be more than happy to download all versions between 1.1.4 and 1.2.6 and report which exact version introduces this problem. I imagine others would be also willing to pitch in, as this issue is a bit more than an inconvenience.
Thank you for escalating this issue; I wish for a paid product there was an easier way to get attention to serious problems. Lack of a publicly facing bug tracker is a serious obstacle in this case.
In the meantime, suggest moving now to the latest version which is now 1.3.2.3112
Unfortunately, the problem persists. Considering it has been an issue for multiple releases now, and release notes don’t mention any fixes related to this, it was expected.
Cheers!
@ananke said:
@sa2000 said:
@ananke said:
Do we have a bug number assigned to this yet? It seems that the number of reports, and repeatability of this issue should be sufficient to get something going.The problem is still not identified - but i have escalated it.
Perhaps I’m not familiar with how Plex development cycle and support system works; however, this problem has all the typical characteristics that would qualify for a bug number: software regression, affecting multiple users and systems, repeatable, and can be pinpointed to a specific release.
Based on reports of others, it may be introduced in 1.2.5. If there was an easier access to historical releases, I would be more than happy to download all versions between 1.1.4 and 1.2.6 and report which exact version introduces this problem. I imagine others would be also willing to pitch in, as this issue is a bit more than an inconvenience.
Thank you for escalating this issue; I wish for a paid product there was an easier way to get attention to serious problems. Lack of a publicly facing bug tracker is a serious obstacle in this case.
In the meantime, suggest moving now to the latest version which is now 1.3.2.3112
Unfortunately, the problem persists. Considering it has been an issue for multiple releases now, and release notes don’t mention any fixes related to this, it was expected.
Cheers!
The logs have been looked at. Would like you to try doing a library re-analyze
See https://support.plex.tv/hc/en-us/articles/200289336-Analyze-Media
And after that completes, please have another test and get me fresh set of logs - testing same library that was tested before
And if it is still just one movie that gets displayed and if it is always the same one
Could you also please test with a smaller library. It is thought that may be the client (TV) is timing out
@sa2000 said:
Could you also please test with a smaller library. It is thought that may be the client (TV) is timing out
This issue affects all libraries, including a small one with home movies.
I’m not sure if this was mentioned before, I thought it may have been: the is no visible timeout. DLNA clients report ‘no items to display’ or just a tiny fraction of available media, very quickly. I may have mentioned it before: the symptoms are as PMS is not considering media to be viable candidates to serve to the clients, rather than an issue with corrupt media, etc.
I’m performing media analysis as requested, using latest 1.3.2 PMS. Will post logs shortly.
Cheers!
Not sure if the logs will be of much help since there was very little before. However, it’s becoming more and more clear what the root cause is:
PMS no longer offers media that would have to be transcoded.
I’ve gone through the total of four (out of >1000) movies, and then checked the TV libraries. The results are: MPEG-4 and WMV media is offered to the DLNA clients and plays, the rest doesn’t. It’s very much in line of what a lot of these 2011/2012 Sony TVs, BD players and presumably LG systems were capable of.
That’s why many of us have gone down the route of checking if the DLNA XML profiles bundled with PMS have changed, and they haven’t. So it’s some internal decision making in PMS is causing it.
Sample formats of what plays, per mediainfo:
Format : MPEG-4
Format : AVC
Format/Info : Advanced Video Codec
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Format : Windows Media
Format : WMV2
Codec ID : WMV2
Codec ID/Info : Windows Media Video 8
Cheers!
@Ananke I would like to assure you that the problem is now actively being investigated.
Please could you do the following test with a test library
Please ensure VERBOSE logging remains enabled on the server (as well as DEBUG)
Would like a new test library created with just one movie in it. One that does show up on 1.1.4 but does not show up on 1.3.0 or 1.3.1
After the library is created and scanned and the item is confirmed to be there through plex web app
Then on the sony, open the dlna server and select videos and drill down to that library folder and see if it shows up
If it does show up, try to play the media file
If it fails or does not show up, note down the time and collect the server and dlna logs and media info text and xml for the movie
I have been comparing the logs already provided and you could use one of these movies for the test if they are one exhibiting the problem
Fahrenheit 451 (1966)
The Fearless Vampire Killers (1967)
Flypaper (2011)
Frozen Fever (2015)
Franklin and the Green Knight (2000)
2012 (2009)
Choosing one of these would be better as I have the 1.1.4 info for them and you just need to test on 1.3.1
Thanks
Attaching logs of the following sequence:
Media doesn’t show up. last step was done roughly around: Fri Dec 9 14:24:xx EST 2016
To double check, I stopped PMS and downgraded to 1.1.4, then tried accessing the library & video in question. As expected, it worked.
@ananke said:
Attaching logs of the following sequence:
- stop current PMS, wipe all logs, upgrade to 1.3.2
- start PMS 1.3.2
- create new library called ‘test’, with a single media file: Fahrenheit 451 (1966).avi. Verify that PMS sees it and scrapes the metadata
- navigate via DLNA on TV to video->test-> all test
Media doesn’t show up. last step was done roughly around: Fri Dec 9 14:24:xx EST 2016
To double check, I stopped PMS and downgraded to 1.1.4, then tried accessing the library & video in question. As expected, it worked.
Thank you.
Problems have been identified and will be fixed and tested before going into the release process
Problems have been identified and will be fixed and tested before going into the release process
Awesome, thank you! Please let me know if any release candidates need to be tested, and I’ll be happy to do so.
Firstly, well done @ananke for your patience and testing prowess. The force is strong in this one! 
@sa2000 would appreciate if you could share the cause. I am one of the many affected and reverted back to 1.1.4. My gut feel was the streaming brain was the culprit.
Thanks @ananke !!!
It’s sad we had to mobilize so much people just to get some attention.
Thank you, @ananke !
Oh thank you so much I was looking all over the net everywhere for a solution to this problem. Finding help on DLNA issues is extremely difficult.
Good to see it was not a problem with any other component involved…
Does anyone know when we can expect the fix for this issue?
Again a big THANKS to you guys!!!
P.S. Just for completeness, I can totally confirm that both my Sony TVs ar running fine again using DLNA after downgrading to 1.1.4.
Investigations are continuing and fixes for identified issues so far are being tested - there appear to be a number of different underlying causes - problem is still unresolved
@ananke said:
Problems have been identified and will be fixed and tested before going into the release process
Awesome, thank you! Please let me know if any release candidates need to be tested, and I’ll be happy to do so.
Its great to finally have this issue get the attention it deserves - fingers crossed for next release! Thanks for persisting this @ananke !
Plex Media Server 1.3.3 has just been released. It has a fix for the DLNA Server issue where videos were not showing
See
@ananke The fix in this releases should address the issue where the movies were not showing.
Please can you confirm this is now ok. And if there are still problems with the movies, please could you get DLNA and Server logs together with media info and media info xml
Thanks
Good news and bad news.
Good news first: media is now showing up as a choice via DLNA. All previously missing media, that I can tell, is now showing up. Yay!
Bad news: vast majority of it is not playing. DLNA client attempts to play, everything looks like it’s going to play, and it eventually times out without showing a single frame.
I’ll collect debug logs from all components, but here’s a sample of non-verbose logs that take place as soon as I attempt to play any of the media in question:
Dec 15, 2016 20:56:06.770 [0x7f6f82bfe700] ERROR - handle_stream_read error 104 Connection reset by peer
Dec 15, 2016 20:56:06.784 [0x7f6f803ff700] ERROR - JobManager: child process killed by signal: 9 (Killed)
^[
==> Plex DLNA Server.log <==
Dec 15, 2016 20:56:36.805 [0x7f8849bfe700] ERROR - NPT_HttpClient::SendRequest to http://127.0.0.1:32400/video/:/transcode/universal/start?audioBoost=100&directPlay=0&directStream=1&directStreamAudio=1&path=%2Flibrary%2Fmetadata%2F564052&session=53b224042c4f422291ac72ed51da3824fb317b71&subtitleSize=100&videoQuality=99&videoResolution=1920x1080&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx failed: -20014
Dec 15, 2016 20:56:36.806 [0x7f8849bfe700] ERROR - ProcessFileRequest - ProcessObjectRequest returned -20014
Thank you for your assistance on this matter.
