Subtitles not working in Plex 1.18 on FreeBSD/FreeNAS

Easily repeatable. Install a FreeBSD 11.2 VM on any choice of hypervisor, install the latest version of Plex. Add an mp4 or mkv movie to the library. Search for and add a subtitle. Start playing the movie in the web interface. If it doesn’t crash immediately, try fast forward.Plex Media Server Logs_2019-11-16_03-31-48.zip (147.8 KB)

I can confirm that.
I have the exact same problem with version 1.8 and up. I have tried with different guest OS-es on VM and Jail and when Plex is set in a jail I get this error [sonewconn: pcb 0xfffff80297badae0: Listen queue overflow: 193 already in queue awaiting acceptance (2 occurrences)] on console messages in FreeNas (not in the jail) as soon as I turn on subtitles. The same problem does not occur if I set Plex in a virtual machine ot the same FreeNas.
This only happens when i play from my LG TV. From PC or web there is no problem.
I noticed that with 1.17.0.1841 (last working version for me) everything is played on Direct Stream while the newer versions (1.18.*) video and subtitles are Тranscoded.
All this was tested with the same movie

My prod PMS server is FreeBSD (running in a jail) and I don’t experience this at all using the web player so lets see if we can figure if this might be a client issue.

First of can you both post exact server version running and web app, same for LG.

Also what type of subs?

Please give more info on the video or post the XML, this will help indicate what the problem might be.

Also there’s been a MAJOR upgrade to the transcoder in recent versions allowing for better Hardware Transcoding support with recent CPUs, some users using older chips (or more precisely Apollo Lake) did report a few issues, we also did solve a issue with subs that seems very similar to what’s described (this woulld be in one of the 1.18.0 builds though so I doubt you wouldn’t have it:

(Transcoder) Subtitles could vanish after a random period after seeking in certain clients (#10573)

There’s ofc always the chance of some regression, but in any case please post the request info and hopefully we can find the culprit.

On my testing machine in Azure I’m running 1.18.2.2029
Web client 3.108.2. I’ve tested using Edge, IE, Chrome and Firefox. It doesn’t matter.
Pretty sure it’s always SRT subtitles.
Let me know if you need access to the machine, that can be arranged.

I also tried using PMS 1.18.2…2041 and web client 4.8.4 on my FreeNas Box upgraded to 11.2U7 today. Same result. Playback error. Conversion failed. The transcoder exited due to an error.

Exactly the same problem yet again. Seems to be widespread.

Still not working. Just tested with the latest version on the vm I set up in Azure for testing.
FreeBSD 11.2-RELEASE-p2
PMS version 1.18.3.2156
Plex web version 4.16.4
Here are the relevant entries in the log:
ERROR - [Transcoder] [tcp @ 0x803bc5f80] Connection to tcp://127.0.0.1:32400 failed: Connection reset by peer
ERROR - [Transcoder] [segment @ 0x803a83600] Failed to open segment list ‘http://127.0.0.1:32400/video/:/transcode/session/d8z7vkx8q59bzzhlf0cx05m9/96d746c8-f798-428c-a149-18f254addae0/seglist
ERROR - [Transcoder] av_interleaved_write_frame(): Connection reset by peer
ERROR - [Transcoder] Error writing trailer of chunk-%05d: Invalid argument
Jobs: ‘/usr/local/share/plexmediaserver-plexpass/Plex Transcoder’ exit code for process 70067 is 1 (failure)
Streaming Resource: Terminated session 0x80d38a158:dtm36f0hykuw4eyu5wwnumv2 with reason Conversion failed. The transcoder exited due to an error.

This is a H264 encoded MP4 with AAC Audio and downloaded SRT subtitles.

And again with PMS 1.18.4.2164, Plex web 4.18.1. Same result.

so thanks to more feedback from @Pixaro looks like this still needs the system tunnable to be set to something higher…

So be sure to raise “kern.ipc.somaxconn” to something like 1024 or higher (PMS will use 1024 regardless but looks like it might not work if the system is set to less!?)

Tbh I’m a bit surprised about it but could you please try it and see if it works around the issue?

please keep in mind though this is all still just a mitigation there a more serious issues that happens to cause this and it should be fixed in a future releases (not the next but hopefully the one after that - meaning possibly 1.18.6)

1 Like

After pretty much having given up, @Pixaro managed to spark my interest again yesterday and after a troubleshooting session I finally managed to resolve my specific issue. I first tried it on my testing machine in Azure and then when it seemed to work, I applied the fix to my freenas box.
After adding the variable kern.ipc.somaxconn with the value 2048 and the type sysctl in tunables under System in FreeNAS and restarting PMS 1.18.4.2171 it actually started working. No more Transcoder errors in the web client. I’ve tested it extensively and everything seems to work just fine now. Quite the load off my shoulders. I actually considered switching to Emby or Jellyfin when I was at my most desperate. Really didn’t like it very much though. I’m glad I “persevered”.
Huge thanks to @Pixaro for keeping at it, when I ran out of patience.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.