Libraries and settings gone after upgrade to 1.19

Plex Media Server
41

thanks for advise, I do not see much of a difference in general just following general directions to install / fix stuff :slight_smile:

42

I have been trying to figure out how to setup FreeNAS in a VM so I can help others but haven’t had any luck with it.

43

I can give you access to my plex server if that helps.

44

Thank you for that but first I need understand how it works. :slight_smile:

45

Not a problem at all.

Can you point me in the right direction who to speak or where to look to get help in this matter?

46

I don’t know anyone other than Engineering who knows.
I am willing to go to another thread so we can discuss how I can setup a FreeNAS VM if you can help me so I can help you?

47

If there is anything I can do to help you help me, please let me know.

48

So when you are using docker, whats meant to happen since the build I’d been using for some time is now entirely broken?

49

In Docker,
I recognize it is Docker and exit. I perform no secondary work.
I know Docker is managing the environment therefore I do not need to.
I give it the files and let it do its thing.

If you are having problems from the installation, I do need see the /tmp/plexinstaller.log file. It will tell me what the installer saw. From there, it’s easy to trace its actions.

50

I tried plexmediaserver-init-v1.5.sh and it failed for my setup which installs into /opt/lib/plexmediaserver verses the standard /usr/lib/plexmediaserver. This non-standard setup has worked without issue through v1.18.9 but not with v1.19.1.

I noticed that the script variable PlexHome is set before but never tested after sourcing the config file plexmediaserver. The value is used to reset the exported PLEX_MEDIA_SERVER_HOME in the “# Build final runtime evironment variables…” section. My workaround has been to add both to the config file plexmediaserver:

export PLEX_MEDIA_SERVER_HOME=/opt/lib/plexmediaserver
PlexHome=${PLEX_MEDIA_SERVER_HOME}

While my setup is non-standard how about running tests on the PlexHome variable?

Hope that helps!

51

@Chuck56

To confirm:

You request:

  1. Use PMS defaults (/usr/lib/plexmediaserver)
  2. After importing /etc/default/plexmediaserver, validate and transfer to $PlexHome
  3. Export and then use the site-specific value for launch.

Correct?


    # Verify Plex Media Server is indeed where it says it is
    if [ -e "$PLEX_MEDIA_SERVER_HOME/Plex Media Server" ]; then
      PlexHome="$PLEX_MEDIA_SERVER_HOME"
    else
       echo "${0}: \"${PLEX_MEDIA_SERVER_HOME}/Plex Media Server\" does not exist.  Using default location."
    fi
52

To all reading here:

There is most likely going to be a hot-fix issued for this Monday/Tuesday if reviews go well.

Is there anything else I need get in ? I have until Europe wakes up Monday morning

Still testing as I write. Beware of bombs :slight_smile:

chuckpa-additions-to-plexmediaserver-init.tar.gz (2.2 KB)

53

Supplemental:

I just chatted with my coworker. He’ll spin us a formal build to test with when ready.
This will allow everyone to confirm all the issues are resolved before the formal hot-fix is released.

54

Yes, correct. Your proposed code would account for a non-standard install location. Thanks!

55

Have you had the opportunity to drop it in place and test drive it?

56

I have another question.

Should I create a compatibility script:

  1. /usr/sbin/start_pms
  2. Which , upon invoking, performs
    a. Informs the user start_pms is obsolete and this script is provided for compatibility only.
    b. sudo /etc/init.d/plexmediaserver start

It would provide something rather than leaving folks hanging.

57

Yes it works after removing a couple debug lines left behind:

env | grep ^Plex
exit

I also wonder if you really need to use the exec command in the start line? I removed the "exec " portion and it still seems to run as expected. Thanks again!

58

All good.

Thanks. That was left so you can see / catch anything bad.

The exec should remain please. I have the environment prepared and expect the exec. I don’t want another shell having the chance to compromise it.

What’s happening here is:

  1. launch the shell, with the PMS variables set in the environment as the PLEX_USER
  2. exec to PMS itself.

I could have done this in one step and exec PMS directly but that will interfere with some versions of init. This is the safer. Replace /bin/sh with PMS.

59

Folks,
If I understand everything correctly.

  1. 1.19.1 will be hot-fixed prior to being made “public” release
  2. 1.19.2 will have the updates from the start.

I caught things mid-cycle hence the unusual cadence of fix-release

60

Here is the final version (1.6) which will be in the distribution.

I figured everyone here deserved a first-shot at it for tolerating my fat fingers :slight_smile:

chuckpa-final-plexmediaserver-init-v-1-6.tar.gz (2.2 KB)

One Warning:

Don’t use ${HOME} in /etc/default/plexmediaserver. If you think about, the reason is obvious. :wink: