Prove to me PMS is attempting to kill processes of other users.
Look at the logs provided above. The PID being killed for the processes is changing on each attempt to kill a process. Why would Plex be re-spawning processes constantly?
That said, I’ll put up some actual information:
for PID in $(grep -i kill Library/Logs/Plex\ Media\ Server/Plex\ Media\ Server* | grep pid | cut -d: -f6 | tr -d ‘)’ ); do ps aux | grep -v grep | grep " $PID "; done
redacted2 20501 0.1 0.0 1868480 51892 pts/65 SNl+ Jul29 110:47 Plex Plug-in [com.plexapp.system] /media/sdm1/home/redacted2/private/plex/usr/lib/plexmediaserver/Resources/Plug-ins-5089475/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 0.9.16.6.1993-5089475 /media/sdm1/home/redacted2/private/plex/usr/lib/plexmediaserver/Resources/Plug-ins-5089475/System.bundle
redacted1 24913 0.1 0.0 1798112 48184 ? SNl Jul29 130:46 Plex Plug-in [com.plexapp.system] /media/sds1/home/redacted1/private/plex/usr/lib/plexmediaserver/Resources/Plug-ins-6f64a8d/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 18.104.22.16800-6f64a8d /media/sds1/home/redacted1/private/plex/usr/lib/plexmediaserver/Resources/Plug-ins-6f64a8d/System.bundle
redacted3+ 3906 0.0 0.0 21400 2512 pts/49 S+ Sep08 5:18 Plex EAE Service
redacted3+ 13404 0.1 0.0 1660400 64144 pts/49 SNl+ Aug31 75:17 Plex Plug-in [com.plexapp.system] /media/sdj1/home/redacted3ast/private/plex/usr/lib/plexmediaserver/Resources/Plug-ins-c789b3fbb/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 22.214.171.12439-c789b3fbb /media/sdj1/home/redacted3ast/private/plex/usr/lib/plexmediaserver/Resources/Plug-ins-c789b3fbb/System.bundle
I can provide more logs if needed – but clearly, it is exactly s stated – MY Plex logs log MY Plex trying to kill pids NOT owned by me.
It is only aware of processes it forks.
Clearly untrue. You can also verify that this is not true by reviewing the full logs provided above – in those logs the FIRST thing that Plex does is start killing processes after being started – there is NO log of those processes being forked.
Only Feral Hosting’s kernel has the problem you are seeing so it can not be a global Debian problem.
You seem obsessed with defending your claim that it is the Kernel – it is FAR more likely that THIS issue you are seeing in the logs is actually a result of Feral running more than one Plex install on a single server – that fits all the evidence (the log messages, the pids of other user’s processes, the multiple kills to processes with the same name but different pids, the fact that those signals you claim do not exist actually work when tested by hand, and the fact that it’s absurd to think that Plex would be the ONLY software to have an issue with breaking POSIX compliance in such a fundamental way)
You show their
uname entry which is clearly their own kernel build. Equally as clearly as this is Fedora’s own kernel build
[chuck@lizum ~.2]$ uname -a
Linux lizum.hessen.lan 4.13.4-200.fc26.x86_64 #1 SMP Thu Sep 28 20:46:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Yes, but that literally means nothing without further evidence. You claim that their kernel lacks basic POSIX support – and your only evidence is that they have a custom kernel. I have pointed out a much better hypothesis that fits all the evidence.
Current GLIBC is:
[chuck@lizum ~.3]$ rpm -qa | grep glibc
I have asked Engineering for finite version minimum on `glibc`.
That’s the current on your RH based distro. Debian tends to do far more back porting than Fedora does.
That said, if the issue IS an outdated glibc, that is progress. If Plex is going to drop support for Debian Jessie, that sucks, but at least it’s an answer.