Server Version#: 1.14.1.5488
Player Version#: iOS player 5.9.1 on iOS 12.1.1 & 12.1.2
So the last month or so the transcoder is killing it! Literally, killing all sessions it starts, whether I play music files on my iPhone or movies on my iPad. These same movies and music files played just fine a while back.
My (Ubuntu) server is hosted remotely, I have no control over the version of the OS but can and do keep PMS up to date.
Up until lately I’d have issues with the transcoder every now and again but it was mostly smooth sailing.
If I set it to play in it’s original quality I usually have no problems.
Which logs do you need from me to look at?
This is getting to the point where Plex becomes unusable for me as I usually don’t have enough bandwidth to support playing on original quality.
If the transcoder product is so broken (judging by my own experiences and a large number of threads on these forums) why not fix it?
Playing all my files from anywhere in any quality is the only reason I have Plex. (And just about the only differentiator from competitors.)
I am sorry. It has been the holiday and I’ve been trying to get through all the backlog.
Please define what you mean “Killing it”. Do they fail to start, start then stop, stutter? Please be more specific.
It would be of most help to me if I had a normal set of DEBUG logs (not VERBOSE), which you capture after recreating a couple of these failures. I only need about 30 seconds of playback or until 1st blip.
Given this is a remote VPS/host, I also need the CPU information (core count) and Memory allocated.
By killing it I mean it stops every movie or audio file I play at various points citing a transcoder issue. Regardless of whether I play it via the web, iPhone or iPad app. I’ve always had it set to prefer higher speed encoding and never had this problem before.
I just played a file from the server via my iPad app. At 23:48 it broke off the movie and cited a transcoder error. I’ve enclosed the log files.
Unfortunately I don’t have the exact info on the remote server, but it’s via Feral Hosting. Again, never had the problem before until the latest updates of the PMS.
“Feral Hosting”. Plex is not compatible with them. They put every Plex server side by side. There is no virtualization on their systems. They rely on Linux “namespaces” which PMS does not support. (too complex for the typical home environment).
Simply stated, you need a different provider.
The details of what’ s happening to you are:
You start PMS
As PMS starts, it makes certain there are no other instances running.
Upon seeing all those other PMS instances, it kills them (shutdown)
Given how many physical hosts they have at their disposal, it is 100% likely, you had the whole server to yourself.
We could do some investigating of your logs to verify if you wish. I fully expect to see “Shutting down (signal 15)” . This is a new PMS forcing yours offline.
Of those few I know, Hetnzer seems to provide good service. I know nothing of anyone’s pricing or packages however.
I’m sure a quick search here will give you several options.
