@aschmidtm said:
Process: 1277 ExecStart=/bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver /usr/lib/plexmediaserver/Plex\ Media\ Server (code=exited, status=127)
Maybe it’s just me, but I would like to see the output of
ls -al /usr/lib/plexmediaserver
@ChuckPa said:
If the difficulty was only because the service did not starting and you with the server to start automatically with each system boot:
sudo systemctl enable plexmediaserver
(Ubuntu 16 uses systemd instead of init. init is now obsolete.)
It’s easier to type service that systemctl. They produce the same output as service IS systemctl in Ubuntu 16. Sorry if this is wrong to you.
First, You are right to pick that nit. The word ‘obsolete’ was incorrect. I spend a great deal of time helping people try to install Plex who just installed Linux for the first time as well. On some systems, such as Fedora, the service script is minimalist at a mere 3K bytes. Trying to use it for Plex returns the following:
The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.
[chuck@lizum ~.102]$
That said, not only do I help with Plex, I am also teaching Linux for a number of users. With 13 different versions/flavors of Linux in my head and VMs because that’s what’s used by Plex users, I do sometimes choose ‘less than optimal’ words.
To share with you my diagnosis strategy, based on what I have seen in the vast majority of cases on both desktops and NAS units
a) Make sure PMS is getting a clean and proper installation (most common)
b) That failing, make certain the correct version of PMS for that platform is being installed
c) With the correct version for the platform having been installed, determine what other system-local conditions exist (systemd overrides, moved default user directory, etc).
As I’m sure you’re aware, /etc/systemd/system/plexmediaserver.service is the unit-level override. /etc/systemd/system/plexmediaserver.service.d/override.conf is the service environment override of the service definition in /usr/lib/systemd/system/plexmediaserver.service.
The two schools of thought in Linux are the Redhat school and the Canonical school. Who’s correct doesn’t matter. The fact both exist is a literal ‘pain in the backside’ to me.
I lead the effort to unify all PMS systems using systemd to a unified service definition file and use of the override file for sustainable customization for users. No more /etc/default/plexmediaserver on some, /etc/defaults/PlexMediaServer on others, and a dozen other places, all of which sprang from the lack of discipline in the init days. It had become too difficult for the Ninjas to support the different variants. The goal was simple:
- The PMS installer and dpkg/yum/dnf are in full control of
plexmediaserver.service. Any customization there is subject to actions taken by the package control tools
- Provide the users with an enduring mechanism to customize PMS’s runtime environment but maintain independence from the core PMS software startup and service operational definitions.
Therefore, we decided:
/usr/lib/systemd/system/plexmediaserver.service will be the the authority as so stated in systemd source./etc/systemd/system/plexmediaserver.service.d/override.conf will be where users can customize (override) those things which concern them (User, Group, and Library location)- All previous customization files (/etc/defaults, etc) would be untouched for users to refer to as needed.
What this leaves all of us is:
- Users have one place to make all their modifications to how PMS starts
- The Ninjas have a common starting point for determining what happening on Linux.
Clean, Simple, and most importantly, Predictable.
Back to diagnosis, after establishing the we have proper package and system, I will need to see the journal output (all the logging got moved to and is a pain) and what journalctl has to say (that’s ONE command i hate typing)
