PlexMediaServer 1.32.6.7371 broken on FreeBSD?

Server Version#: 1.32.6.7371

I think something is wrong with the FreeBSD build.

Instant segmentation fault on launch.
And ldd immediately crashes if run on the Plex Media Server binary.

A previous version, and this is what I would expect for most binaries:

$ strings PlexMediaServer-1.32.5.7349-8f4248874/Plex\ Media\ Server | head -n 2
/libexec/ld-elf.so.1
FreeBSD

The new build version; this is weird:

$ strings PlexMediaServer-1.32.6.7371-b6a09ad81/Plex\ Media\ Server  | head -n 2
FreeBSD
FreeBSD

Where’s our buddy ld-elf.so?

3 Likes

The other binaries (Plex SQLite, others) have the same behavior.

I notice start.sh has changed slightly as well, so I’m guessing that changes have been made to the build.

I also notice that PlexMediaServer-1.32.5.7349-8f4248874/lib/libc++.so.2 exists, but there is no similar file in 1.32.6.7371-b6a09ad81.

This is a 13.1 jail on a 13.2 host, but I’m doubting that’s the issue.

Can confirm Plex Media Server 1.32.6.7371 does not start in my TrueNAS Core jail.

1 Like

Thanks for reporting this. Digging into it now.

4 Likes

Looks like it might be affecting multiple OS’s. Works find on my Qnap NAS, but crashes on my Centos stream 9 VM

Tried a downgrade and its still failing

It’s the same for me in a jail on TrueNAS-13.0-U5.3.

I’m able to get it back running again, by iocage update “jail name”, even tho there is no update it reinstalls the version for the plugin, which still works.

I’ve had to disable my pms-updater script until this is resolved.

Same issue, TrueNAS Core. I tried restoring a backup from last night, didn’t work. Then just installed the old version over the new one and it’s running again.

Yep, same issue here. I had to run Jail update to install the old Plex version and disable the Plex update script.

+1
1.32.6.7371 segfaults on startup. 1.32.5.7349 runs just fine after restoring the backup.

Is there a resolution for this yet?

Do you have a resolution yet?

Same problem here, hopefully gets resolved quickly.

I was able to download the 1.32.5 version and install using the PMSUpdater command. Plex fired right back last night and had people connected to it. Then I woke up this morning and it updated again and is not working. How do I prevent it from updating to this bugged release?

Plex itself doesn’t auto-update, so you have some script running automatically or on a schedule.

Check your crontab.

Gotcha. I just checked my Crontab and it shows “no crontab for root”. I set this Plex up two years ago and I don’t remember how I setup the updating part.

Would you be able to post the commands you used to do this please?

If you’re running Plex in a jail, remember to check the crontab of the jail itself.

1 Like

Apparently I did it the hard way… I backed up my data, deleted the jail,. created a new jail, installed PMS using the “pkg install plexmediaserver-plexpass”, copied my data back and started PMS, working fine.

But then I REALLY did a stupid move. I saw there was an update… so I ran my cron job to update… instantly killed it.

So…

I did it all again… but this time while my backup date is copying back… I jumped in here… and realzied I took the very scenic route… oh well it’s working for now. Cron job is disabled for now.

1 Like

This was my answer… thank you. I forgot I setup the Cron job in the web interface of TrueNAS and not command line. Disabled the Cron job until this mess gets sorted out.