Server Version#: 1.13.5.5332-21ab172de
Player Version#:
The host runs Linux: OpenSUSE Leap 15 with an Intel Core i7 CPU (architecture x86-64), and 16 GB of RAM. It works flawlessly for everything else but not for Plex: the Fedora 64-bit rpm package installs with no complaints, but the server doesn’t run. A quick review (under YAST) of the service shows it is not running.
An attempt to activate plexmediaserver service fails. The error message states file plexmediaserver.service is missing.
Any help greatly appreciated 
Show me the system log files please (dmesg / journald) in a ZIP / tar.gz ?
Hi Chuck,
Dmesg shows nothing (I just installed). When installing, the rpm appears to run with exit code 0 (grep plex /var/log/messages)
` 2018-08-23T13:28:17.835883-04:00 mofi [RPM][8898]: install plexmediaserver-1.13.5.5332-21ab172de.x86_64: success
2018-08-23T13:28:17.838944-04:00 mofi [RPM][8898]: install plexmediaserver-1.13.5.5332-21ab172de.x86_64: success`
but then, running as user root the '` /etc/init.d/plexmediaserver start' command, I get`
` /etc/init.d/plexmediaserver start
redirecting to systemctl start plexmediaserver.service
Failed to start plexmediaserver.service: Unit plexmediaserver.service not found.
`
Please let me know if there's anything else you need to know.
Thanks for your help,
JulioPlease verify /lib/systemd/system/plexmediaserver.service exists.
I must also go look at the installer. Nothing has changed in it. I am rewriting the installers but at this point nothing is implemented.
The second message block you show implies Suse is not seeing the file but installation would have failed if it didn’t install so at a loss here with that.
It does, owned by ‘root’, group ‘root’ with 828 chars and permissions 664. I was a regular user until around Feb 2018, then something broke and I have not been able to reinstall and make it work since.
Let me know if you want me to try something else.
Thanks,
Julio
you cannot reinstall what ? PMS? Suse updates? Please be specific here… it’s very important.
PMS can always be manually installed/removed in a number of different ways. We can even create a second ‘test’ instance of it on the same host without touching your original installation.
Back around May 2018 I installed the new RPM for PMS corresponding to Fedora x86-64 and the media server I had ceased to work (before May I had it working for a long time). Since then, I installed each new RPM (June, July, now August 2018) and failed to make it run. Could it be associated with the change to systemd in OpenSUSE Leap 15? (I think I had OpenSUSE 42.3 with sysinit before).
I did not know about so many options to install PMS. Always used the RPM package for Fedora. I will read carefully how to do that (to avoid future mishaps) if you indicate a reference.
Thanks Chuck,
Julio
Thank you for clarifying. I will go setup a Leap 15 VM now, obtain all updates, and see what happens.
The last I checked, it did operate but it is possible Suse updates have broken that which means I will need adjust the packaging (IF possible).
I’m still trying to resolve what I’m seeing but Leap 15.0 is not putting files in standard locations (not surprised with anything Suse does).
If you wish to experiment,
- copy
plexmediaserver.servicefrom/lib/systemd/systemto/etc/systemd/system systemctl daemon-reloadsystemctl start plexmediaserver
If anything will bring it to life, this will.
**Hi Chuck,
Hi Julio. 
Any results to share?
*Hi Chuck,
Hi Chuck,
Copied and reloaded daemons… everything well until the 3rd command
systemctl start plexmediaserver
Job for plexmediaserver.service failed because the control process exited with error code.
See “systemctl status plexmediaserver.service” and “journalctl -xe” for details.
Running the first suggestion:
systemctl status plexmediaserver.service
● plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/etc/systemd/system/plexmediaserver.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-08-24 00:05:50 EDT; 3min 8s ago
Process: 16604 ExecStartPre=/bin/sh -c /usr/bin/test -d “${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}” || /bin/mkdir -p "${>
Aug 24 00:05:45 mofi systemd[1]: plexmediaserver.service: Unit entered failed state.
Aug 24 00:05:45 mofi systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Aug 24 00:05:50 mofi systemd[1]: Stopped Plex Media Server for Linux.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Aug 24 00:05:50 mofi systemd[1]: Failed to start Plex Media Server for Linux.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Unit entered failed state.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Running the second suggestion:
journalctl -xe
– The process /bin/sh could not be executed and failed.
– The error number returned by this process is 3.
Aug 24 00:05:45 mofi systemd[1]: plexmediaserver.service: Control process exited, code=exited status=216
Aug 24 00:05:45 mofi systemd[1]: Failed to start Plex Media Server for Linux.
– Subject: Unit plexmediaserver.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page
– Unit plexmediaserver.service has failed.
– The result is failed.
Aug 24 00:05:45 mofi systemd[1]: plexmediaserver.service: Unit entered failed state.
Aug 24 00:05:45 mofi systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Aug 24 00:05:50 mofi systemd[1]: Stopped Plex Media Server for Linux.
– Subject: Unit plexmediaserver.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page
– Unit plexmediaserver.service has finished shutting down.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Aug 24 00:05:50 mofi systemd[1]: Failed to start Plex Media Server for Linux.
– Subject: Unit plexmediaserver.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page
– Unit plexmediaserver.service has failed.
– The result is failed.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Unit entered failed state.
Aug 24 00:05:50 mofi systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Aug 24 00:07:02 mofi plasmashell[2446]: kf5.kpackage: No metadata file in the package, expected it at: “/home/julio/Photos/Stunning/”
Aug 24 00:07:02 mofi plasmashell[2446]: kf5.kpackage: No metadata file in the package, expected it at: “/home/julio/Photos/Stunning/”
Aug 24 00:07:02 mofi plasmashell[2446]: kf5.kpackage: No metadata file in the package, expected it at: “/home/julio/Photos/Stunning/”
Aug 24 00:08:23 mofi systemd[1]: is_symlink_with_known_name(plexmediaserver.service, plexmediaserver.service) → 1
Aug 24 00:12:02 mofi plasmashell[2446]: kf5.kpackage: No metadata file in the package, expected it at: “/home/julio/Photos/Stunning/”
Aug 24 00:12:02 mofi plasmashell[2446]: kf5.kpackage: No metadata file in the package, expected it at: “/home/julio/Photos/Stunning/”
Aug 24 00:12:02 mofi plasmashell[2446]: kf5.kpackage: No metadata file in the package, expected it at: “/home/julio/Photos/Stunning/”
Thanks again Chuck,
Julio
On 08/23/2018 10:35 PM, ChuckPA wrote:
I’m still trying to resolve what I’m seeing but Leap 15.0 is not putting files in standard locations (not surprised with anything Suse does).
If you wish to experiment,
- copy
plexmediaserver.servicefrom/lib/systemd/systemto/etc/systemd/systemsystemctl daemon-reloadsystemctl start plexmediaserverIf anything will bring it to life, this will.
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
I am uncertain if you are experiencing these errors because you put PMS in your home directory or not.
Putting PMS’ library inside your home directory is NOT advised nor can I support it because of cases exactly like this.
I just upgraded my VM to root and it’s a mess.
I can only advise you to continue to try and sort things out on your own and put PMS back where it belongs (/var/lib/plexmediaserver). You can change the ownership from there.
It is clear to me Suse switched to using systemd from sysvinit and there are artifacts from the migration.
How extensive they are remains to be seen.
I regretfully do not have time to delve into it and wont for the the next couple weeks due to my current workload. Suse is one of the “Use it if it works” distributions.
I agree: OpenSUSE has a history of doing things their own way, and its users are often left to clean up the mess. Nevertheless I must make a clarification: I did not put PMS in my home directory. I just used the RPM package as downloaded and ran 'rpm -Uvh ’ as root. As a UNIX/Linux aficionado, I can get used to almost any distribution - so my question to you is this: which one has proven to be (in your opinion, of course) the most stable one for PMS?
Thanks,
Julio
Julio,
Ubuntu is by far the most popular. Ubuntu 18.04 (current) has some issues because it’s new.
I use Fedora 27 (not 28 because it’s also too new / unstable)
Those are your two most popular and best supported (based on userbase) solutions.
Thanks again, Chuck. I’ll set up a Ubuntu 17.10, or Fedora 27 system. Yet, please let me know if the OpenSUSE issue is satisfactorily resolved
– Julio
julio,
I tried again in my VM after applying their updates.
Not promising.
This may be the end of the unofficial support it once had. I will not be able to look further until after current tasking is completed.
Completely understand the decision to limit efforts for an unofficially supported (and not very cooperating) platform. Thanks!
Julio
On leap15, add a symbolic link to /etc/SuSE-release that points to /etc/os-release
Then reinstall
