Failed to automatically restart after upgrade to 1.19.1.2589

I upgraded today from 1.18.9.2578 to 1.19.1.2589 and this is the first upgrade i’ve ever performed where PMS did not restart after the upgrade was completed. I had to manually start the server with systemctl. Interestingly, there’s a note in the release notes that says “(Ubuntu/Debian) Respect autostart after upgrade for all versions 1.18.5 and above” but my experience was the complete opposite. Here is the output from the ugprade if it helps (i didn’t see anything suspect)

(Reading database ... 376958 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.19.1.2589-2de7f3266_amd64.deb ...
PlexMediaServer install: Pre-installation Validation.
PlexMediaServer install: Pre-installation Validation complete.
Unpacking plexmediaserver (1.19.1.2589-2de7f3266) over (1.18.9.2578-513b381af) ...
Setting up plexmediaserver (1.19.1.2589-2de7f3266) ...
PlexMediaServer install: PlexMediaServer-1.19.1.2589-2de7f3266 - Installation starting.
PlexMediaServer install: 
PlexMediaServer install: Now installing based on:
PlexMediaServer install:   Installation Type:   Update
PlexMediaServer install:   Process Control:     systemd
PlexMediaServer install:   Plex User:           plex
PlexMediaServer install:   Plex Group:          plex
PlexMediaServer install:   Video Group:         video
PlexMediaServer install:   Metadata Dir:        /var/lib/plexmediaserver/Library/Application Support
PlexMediaServer install:   Temp Directory:      /dev/shm  (set in Preferences.xml)
PlexMediaServer install:   Lang Encoding:       en_US.UTF-8
PlexMediaServer install:   Transcoding HW:      Found
PlexMediaServer install: 
PlexMediaServer install: Completing final configuration.
PlexMediaServer install: PlexMediaServer-1.19.1.2589-2de7f3266 - Installation successful.  Errors: 0, Warnings: 0
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.23+linuxmint8) ...
Processing triggers for mime-support (3.60ubuntu1) ...

In the release notes, you should find where I respect the flags

  1. I do not forcibly enable PMS after upgrade. I leave management of Enable / Disable entirely up to you. I only force it on the first upgrade from a pre-1.18.5 version.

  2. If PMS was running at the time of the upgrade, I restart it.

I would very much like to see your /tmp/plexinstaller.log file if you don’t mind sharing.

@ChuckPa, here is the log plexinstaller.log (471 Bytes)

If I’m reading your point #2 correctly, if PMS was running before upgrade it should have restarted it afterward (regardless of the pre-update version). Is that correct?

That’s correct.

If plexmediaserver.preinst sees PMS is running (some debian versions do stop packages before preinstall runs) then I set the flag Running=1.

When I have completed installation, if [ $Running -eq 1 ]; then I start PMS again.
You will see it in the console output “Starting Plex Media Server.” right before dpkg exists.

Thanks for the installer log. If you examine it, near the bottom,

Verbose=1
Running=0
Errors=0
Warnings=0

This tells me PMS was not running when plexmediaserver.preinstall ran.

I have a secondary plexmediaserver.state file which I also use. The state file catches those versions where dpkg calls the uninstall routines (inappropriately) first while performing a partial ‘unpack’ of the DEB.

I look here too to keep any chance of detecting PMS’s as “running”.

With PMS now running as 1.19.1, If you’d care try to install on top of itself (it will let you). See if it now detects itself as running. I will be very surprised if it doesn’t and will want to know why.

Installed 1.19.1 over 1.19.1 successfully restarts PMS. Strange that it didn’t detect 1.18.9 as running even though it was. Oh well, all is right in the Plex world again :wink:

Excellent! “Another happy customer!” :rofl:

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