PlexMediaServer 1.32.6.7371 broken on FreeBSD?

You need to download the older version…
wget https://downloads.plex.tv/plex-media-server-new/1.32.5.7349-8f4248874/freebsd/PlexMediaServer-1.32.5.7349-8f4248874-FreeBSD-amd64.tar.bz2

Then run the installer…
sh ./PMS_Updater.sh -f -l PlexMediaServer-1.32.5.7349-8f4248874-FreeBSD-amd64.tar.bz2

1 Like

Why go through all the hazzle? PMS_updater creates a backup folder. Simply rename /usr/local/share/plexmediaserver-plexpass.bak and Bobs your uncle.

2 Likes

Why are people not using snapshots in this day and age? Took 5mins to realize it was broken and proceeded to roll back. You can do this in a one liner (include iocage jails)

Hell even use snapshots on my docker hosts as well for volume/mount data (not images).

Cause it rolls back your database as well (: Who knows what you might have changed in between the last snap. Reverting back the install keeps the db in tact.

It’s sooo useful to keep jails and plexdata and usermedia in different pools.

It’s nice to be able to snapshot them independently, backup/restore them independently, configure settings independently.

1 Like

Of course it will if your using only periodic snapshots. Just snapshot before running the update? Still quicker then copying the DB and simple to roll back.

This is being looked into, in the meantime please just remain on the public release.

Thanks for the reports!

1 Like

Can you pull the download? People (who probably shouldn’t be using the beta) keep installing it and not knowing how to roll back. :-/

2 Likes

I know this is slightly off topic and i apologise…
But if the FreeBSD version’s “Update now” button worked, i don’t think this would cause so many problems - perhaps that could be pushed up the priorities list a little?

Its only where people (like me admittedly) have got fed up with having to manually update and are instead using the PMS_Updater.sh to do the update - which apparently pulls the beta instead of the public (something else i did not know, could have sworn it was the latest public!).

Anyway - please don’t take offence at this post, was meant merely as a suggestion/comment.

Also - for those wanting roll back details, the following if run from shell within the Jail itself should rollback plex without affecting your db

/bin/sh /usr/local/PMS_Updater/PMS_Updater.sh -v -f -l /tmp/PlexMediaServer-1.32.5.7349-8f4248874-FreeBSD-amd64.tar.bz2

Why don’t you use the FreeBSD port/pkg?

That PMS_Updater.sh script has caused more pain than it has solved. It assumes Plex was previously installed via another mechanism, but then it breaks the port/pkg system.

The idea of an in-server Update Now is so weird on FreeBSD. That’s such weird behavior on a Unix-y system. How would that jive with system package management? And this build would still be broken, and how would you recover?

3 Likes

I have the same issue on FreeBSD - version 1.32.6.7371 causing instant segfault. Rolled back to the latest available version for non-plexpass (1.32.5.7349), and all has been restored.

… it’s almost like not jumping headfirst into every new update that comes out is a good idea if your system uptime and stability is important. :thinking:

2 Likes

I just updated a couple of servers only see seg faults. Why is this still available to download?? The downloads don’t even say beta. Now all my android /google tv boxes won’t play properly since downgrading. What a mess and waste of a night. The only thing that plays is my iPhone and web browser.

Your command line instructions were exactly what I needed. Thanks for getting me back online.

1 Like

For anyone else looking to quickly roll back, someone posted that you can run the updates function from the trunas plugin interface and it woll roll back to 1.32.5. I’d test but I already manually rolled back via PMS.

Just don’t forget to disable your PMS update cronjob if you have one set.

Any update on this? It’s been some time since this was reported and acknowledged. Guess I’m just looking for someone at Plex to give the all clear that it’s safe. :thinking:

That build is broken. If/when they fix it it will be a new build/file/download.

Yup, I figured. Just been over 2 weeks with no news and the latest available build still shows the broken one. :disappointed_relieved:

Any updates on this?

image