Server Version#: 1.18.5.2309
Player Version#: 4.12.3
According the Announcement for 1.18.6.2368 (Plex Media Server) there will be a FIX available:
(Ubuntu/Debian) The service may not have automatically started after upgrading an existing install.
Are there plans to also FIX this for Fedora/CentOS?
I have the same situation that after upgrading an existing install in CentOS using the official plex.repo (https://downloads.plex.tv/repo/rpm/$basearch/).
After an upgrade the service does not automatically restart and plex gets unstable.
Once you install the newer packaging , with this FIX already in, you’re ok.
I totally FAT FINGERED a variable name. It was reviewed and we all missed it.
The code has been locked away from me,
The keys taken away from me,
The combo to the safe changed.
hahahaha
Technical:
1.18.5 wrote IsRunning=1
1.18.6 looks for Running=1 and also writes Running=0 or Running=1.
All you need do is manually start it. it’ll be fine from here forward
As soon as this is stable (couple versions without bumps), It will be transferred to RPM packaging too. All changes up to this point have been DEB packaging only.
@ChuckPa as an fyi… I successfully upgraded today to sudo dnf upgrade plexmediaserver-1.18.7.2415-9930aef45.x86_64.rpm from plexmediaserver-1.18.6.2368-97add474d.x86_64.rpm and afterwards pms was still reported as stopped after the upgrade completed. I needed to manually start the pms service.
