Upgrade to 1.19.1 removes /usr/sbin/start_pms

Plex Media Server installation configuration info: Sat 11 Apr 2020 03:03:23 PM PDT

Init=0
Systemd=1
Custom=0
LinuxContainer=0
NewInstall=0
HaveOverride=0
OverrideFile=""
PlexUser=“plex”
PlexGroup=“plex”
VideoGroup=“video”
AppSuppDir="/var/lib/plexmediaserver/Library/Application Support"
PlexTempDir="/tmp"
LangEncoding=“en_US.UTF-8”
ExistingVersion=11809
HaveHardware=1
HaveTranscoderPref=0
NeedUser=0
NeedGroup=0
NeedVideo=0
Verbose=1
Running=1
Errors=0
Warnings=0

Yep. You aren’t running an init based system anymore.

systemctl status plexmediaserver  - - gets status
systemctl start plexmediaserver -- starts it
systemctl enable plexmediaserver -- enables start at system boot
systemctl stop plexmediaserver - stops
systemctl disable plexmediaserver - - disables autostart at boot

root@XX:/tmp# which init
/sbin/init

root@XX:/tmp# readlink /sbin/init
/lib/systemd/systemd

your system matches mine… perfectly. Systemd . no init. therefore none of the init support files would have been installed.

Please disregard the init.d/plexmediaserver and default/plexmediaserver files.
They are useless to you.

This is how you customize PMS now. This change happened because init (Ubuntu 1-14) → upstart (Ubuntu 15) → systemd (Ubuntu 16).

Followed the steps and it seems to be working now. Appreciate the patience and assistance Chuck!

One question.

Still need start_pms? :rofl:

Haven’t rebooted yet, too many family members complaining about downtime, but manual start worked so… :wink:

if you’ve enabled the service then it will start at boot. :slight_smile:

I have setup the installer to leave Enable/Disable alone.
However you have it set is how it will be.

I only make certain to respect the “Running” state when performing upgrades.

Maybe? Should people using tini/runit/whatever in docker be concerned about some environment runtime breaking in the future? I kinda assumed start_pms was a shared entry point that would take care of sanity checking environments and providing a level of BC as things changed.

I am running Slackware current which was updated 4 days ago to adjust for the missing /usr/sbin/start_pms issue. However when invoking

#/etc/rc.d/rc.plexmediaserver start

manually or through my startup script it outputs that the server is starting but it does not start. Their script was oudated one version of plexmediaserver so I updated that string to compile the newest .deb and it builds installs but will not start? Let me know what else you need or why invoking the rc.plexmediaserver start would not start the server?
this is for plexmediaserver_1.19.1.2645-ccb6eb67e_amd64.deb

Regarding tini, binhex, and docker – Those are all recognized containers. I do not perform any processing once they are recognized as the containers manage themselves through their start/stop mechanisms. I also trust the environment is validated.

I recognize systemd LXCs and do not run udevadm due to a known trigger bug with udevadm when in a container.

Anything else is deemed Custom=1 (will show in the plexinstaller.log) to which I do nothing. I essentially provide a “tar ball” drop.

Slackware has never been supported. Another user tried it and had to make manual accommodations .

I did make a change to /etc/init.d/plexmediserver for SYSV-init (which is all I officially support – by design). It is a bit more forgiving.

I also corrected a timing error where PMS would start in ${HOME}/Library.... which ended up being /root/Library … OOOOPS :wink:

I will provide the updated /etc/init.d/plexmediaserver file here to download and use until 1.19.2 comes out if desired.

This is the /etc/init.d/plexmediaserver file which will be in the update.

I have renamed it to avoid collision.

chuckpa-plexmediaserver.init.tar.gz

chuckpa-plexmediaserver.init.tar.gz (2.2 KB)

5 posts were merged into an existing topic: Linux Server wont upgrade v 1.19

To All following along here.

I have a completed CI build containing all the lasted packaging updates for
Plex Media Server

This DEB contains the changes we’ve made here.

There is only one more change I plan to make to the Preinstall module.
A degenerate case was discovered today where the locale was not properly defined and the installer failed to catch it.

If everyone would please check this and let me know as soon as possible if this is fully as expected & previously worked out. I only changed the Init file. Once I have confirmation, I will be able to merge it into the master branch for the upcoming PMS release.

Thanks

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