PMS version 1.23.0.4482 + 1.23.0.4480 no longer auto start after upgrading on ubuntu 20.04

Plex Media Server Desktops & Laptops
1

Server Version: 1.23.0.4482 + 1.23.0.4480
OS: ubuntu 20.04.2 64bit

Problem:
Typically when doing a sudo apt install plexmediaserver_1.23.0.4482-62106842a_amd64.deb after the install completes the plexmediaserver service is auto started. Since the two updates today 1.23.0.4482 + 1.23.0.4480 this is no longer happening.

Workaround:
Starting the service manually sudo service plexmediaserver start works but would be nice to get the auto start back again.

2

Another user reported this in @ChuckPa 's Linux packaging thread; it looks like the problem has been identified and corrected:

3

Okay, thanks for letting me know.

4

Yes, All fixed.

I am REALLY sorry for the fat, over-tired, fingers

:cry:

2 Likes
5

Thanks, @ChuckPa – came here to attempt to file a bug report, OF COURSE you’ve already fixed it.

Updating to plexmediaserver_1.23.0.4482-62106842a_amd64.deb on Ubuntu 20.04.2 LTS x86_64 VM caused me to have to run a quick sudo service plexmediaserver restart at which point things appeared to come right back online.

Applying your ChuckPa-plexmediaserver_1.23.0.4482-62106842a_amd64.deb fix now. Get some rest, sir! You’re a rock star.

6

Again, sorry for the PEBKAC moment :see_no_evil: :gun:

7

No no no, please no apologies, sir. The turn-around time on your bugfix would make most project managers drool. We appreciate you.

PEBKAC are just fine, and to be expected. As long as we’re not dealing with any ID 10-t errors, things will be dandy. :sunglasses: Stay safe out there!

1 Like
8

Thanks @ChuckPa

9

Classifying as PEBKAC or ID-10T depends entire on the perspective, wouldn’t you agree? LOL

1 Like
10

I always liked the term Layer 8 problem.

11

UPDATE:

Engineering has the update in position now.
I would think it’ll show up in their next release but I’m not on the release team.

2 Likes
12

I’ve just installed 1.23.0.4482-62106842a on my newly installed unbuntu server 20.04 and service is starting when reboot without issues

13

@mirdragon

Thanks. The issue we’re discussing occurs when upgrading PMS. That’s what I broke.

Normal procedure is:

  1. Get current RUN state
  2. Stop PMS
  3. Perform upgrade
  4. Restart if previously RUNning

I broke that check. (working on weekends again while tired)

It’s all fixed now. We’re just waiting for it to be included in a formal release.

14

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