Server settings unavailable

(FreeBSD) (@feld)

Following on to my earlier questions about LD_LIBRARY_PATH.

In a freshly installed normal jail, if I install the pkg/port version 1.22.1.4228, the provided rc script doesn’t have LD_LIBRARY_PATH, and it works fine.

In a freshly installed normal jail, if I install pkg/port version 1.23.2.4625, the rc script still doesn’t have LD_LIBRARY_PATH, but now it doesn’t work. Multiple errors.

(What’s confusing to me is that I removed LD_LIBRARY_PATH from my main system, and everything is still working fine. Some of my paths and environment are different - maybe that’s relevant.)

Adding it back to the rc script seems to be the immediate solution for 1.23.2.4656.

On line ~56 of /usr/local/etc/rc.d/plexmediaserver or /usr/local/etc/rc.d/plexmediaserver_plexpass, you’ll see this:

export SCRIPTPATH="/usr/local/share/plexmediaserver-plexpass"

Add a new line after it, so it looks like this:

export SCRIPTPATH="/usr/local/share/plexmediaserver-plexpass"
export LD_LIBRARY_PATH="${SCRIPTPATH}/lib"
1 Like

Nice find. That does indeed fix it.

awesome, thank you for putting in your time to figure out a workaround for this.

@Volts thank you putting in the time and effort figuring this out. But as I am on Windows Server, I’m not sure where to look for /usr/local/etc/rc.d/plexmediaserver or /usr/local/etc/rc.d/plexmediaserver_plexpass

Or am I being stupid?

Not stupid at all! But this wouldn’t be relevant for Windows. :slight_smile:

@Volts, Well damn! I’ll just wait for a fix in an update i guess.

1 Like

@Volts I would advise against doing this. The Plex team reached out to me and explicitly requested I remove LD_LIBRARY_PATH because it was no longer necessary and expected to break things in the future. If Plex has released a version that doesn’t work without setting LD_LIBRARY_PATH the issue is in their build system.

I know they contacted you - that’s why I pinged you. I figured you could rattle your contact. :slight_smile:

The FreeBSD 1.23.2.4656 port/pkg appears - to me - to currently be broken.

I’ll send an email and see what shakes out

edit: and thank you for pinging me on this thread :blush:

edit2: original contact email bounced, going up the chain to Elan. He usually responds to me.

edit3: getting access to a Plex internal chat group

edit4: if you don’t want to modify the plex rc script you can put this in /etc/rc.conf as a workaround to inject the env: plexmediaserver_env="LD_LIBRARY_PATH='/usr/local/share/plexmediaserver/lib'"

1 Like

Does anyone have a fix for the Windows version?

I’m a Plex Pass user and Plex user for year and never had an issue until now, but this issue is getting annoying and the lack of announcements from Plex is bothering me.

Maybe re-release the previous 1.22.3.4523 version as it seems to work fine when we wait for the team to fix this issue!

Thanks!

1 Like

That sounds like appropriate punishment. No rest for the wicked. :stuck_out_tongue:

That almost seems worse than modifying the rc script, in at least one regard. A future package update (or re-install) could correct the rc script in the next version, but changes to /etc/rc.conf are likely to be pretty durable on any given system.

But I defer to your expertise!


Oh hey! What’s "${plexmediaserver_support_path}/Plex" for, and why does the rc script create it?

with this i could solve my problem. Thx for your support! :slight_smile:

https://www.videohelp.com/software/Plex/old-versions

This is where it pays to use a proper server operating system like BSD/Linux instead of Winblows. For me all I needed to do was roll back to a previous working snapshot and disable my auto update cron job. Took all of 30 seconds. Now I just need to wait till a new version resolves the issue then just enable the auto update script and everything will be taken care of automatically during the next maintenance window.

I use plex on xigmanas. I updated the plugin and after that, the plex does not start, I tried to change the specified settings, but it does not help what to do ?

This also resolved it for me for the time being.
(freebsd iocage jail)
lets hope the devs come with a proper solution.

That almost seems worse than modifying the rc script, in at least one regard. A future package update (or re-install) could correct the rc script in the next version

FreeBSD pkg used to refuse to replace rc scripts that were modified during package upgrades. I don’t know what the current behavior is – I’ll have to test.

Oh hey! What’s "${plexmediaserver_support_path}/Plex" for, and why does the rc script create it?

Plex used to use this, so it was added to the rc script to ensure the directory had the correct ownership/permissions:

# ls -ltR /usr/local/plexdata/Plex/
total 1
drwxr-xr-x  2 plex  plex  3 Aug 18  2016 Codecs

/usr/local/plexdata/Plex/Codecs:
total 1
-rw-------  1 plex  plex  36 Jun 11  2016 .device-id

Looks like it’s not being used anymore and I can probably remove it.

1 Like

You’re right, of course.

Post-install script? Add something to the message?

I appreciate you doing this. :slight_smile:

Still have not heard back from the Plex team, but all my testing of the LD_LIBRARY_PATH fix has not shown any side effects so I’m shipping this

1 Like

In Windows you have to uninstall the current version (don’t remove user data!) and install the version you want.

I’m about to roll back myself. It’s not just server settings —I can’t add a new library as it dies on the language option, and I can’t edit libraries as the same thing happens.

Well, I rolled back. It didn’t fix the issue of adding/editing libraries. I can’t access anything in the main server settings. Should I roll back another few versions?