Package Details: plex-media-server 1.21.0.3616-1

Git Clone URL: https://aur.archlinux.org/plex-media-server.git (read-only, click to copy)
Package Base: plex-media-server
Description: The back-end media server component of Plex.
Upstream URL: https://plex.tv/
Keywords: DLNA
Licenses: custom
Conflicts: plex-media-server-plexpass
Submitter: alucryd
Maintainer: fryfrog (tixetsal)
Last Packager: fryfrog
Votes: 322
Popularity: 1.24
First Submitted: 2014-10-14 22:11
Last Updated: 2020-11-23 16:25

Pinned Comments

fryfrog commented on 2019-03-22 16:55

Flagging Out of Date:

This package is the non-plexpass package, it gets updated less frequently. Be sure to flag the right package. You can find the plexpass version at https://aur.archlinux.org/packages/plex-media-server-plexpass/

Current Issues:

The plex user's home directory needs to be changed, but likely can't if Plex Media Server was running when you upgrade. The package will tell you what to do, but of course that is easy to miss. The soluiton is to run sudo systemctl stop plexmediaserver ; sudo usermod -d /usr/lib/plexmediaserver plex ; sudo systemctl start plexmediaserver.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

techwiz commented on 2019-11-20 18:23

@j1simon, yes you can modify the PKGBUILD to meet your needs and maintain your patched repo yourself. As fryfrog mentioned, the change is trivial and the maintenance would be equally trivial for you. Asking the community, which agreed on “The Arch Way,” to bend over for your request is of course going to be met with resistance. Sorry for the inconvenience, but this is how we’ve all agreed things should be.

j1simon commented on 2019-11-20 17:32

I don't agree again. There are a way to solve this but someone decides doesn't use it because ¿the Arch way?

fryfrog commented on 2019-11-20 17:29

@j1simon: It doesn't matter if you agree or not, the Arch way is to not start or restart daemons and so that is how all the packages I manage operate. I personally would love if Arch came up w/ a way for packages to notify that they need restarting, so that at the end of a big upgrade, a user could be presented w/ all the services that might need restarting... but that doesn't exist.

You are of course welcome to take this AUR package and modify it how you'd like it to work. Keeping it up to date is as easy as changing a couple version fields and updating the checksums.

j1simon commented on 2019-11-20 17:24

I don't agree. Every time Plex is upgraded, I have to restart Plex service manually because the service is in a state of error after upgrade. That should never happen if the update was correct.
For that is the .install file and this package uses it. In the post_upgrade() section it would be necessary to check if the service is started and if that is the case to restart it.

techwiz commented on 2019-11-20 14:41

@j1simon refer to this reddit post from 2013 that does a good job of explaining why Arch packages don’t start or stop services: https://www.reddit.com/r/archlinux/comments/1s1p9t/comment/cdt8mo1

The gist is that it’s up to the user to configure and run their software, and as such many packages don’t ship with a default config that makes sense to run out of the box. Since we don’t know if the user wants to start the service right away or if the default config is good enough, pacman does not manage services, it just installs them.

j1simon commented on 2019-11-20 10:10

Why is not the service restarted when upgraded?

techwiz commented on 2019-10-31 02:37

@ectospasm: “ tl;dr, my ~/.cache/pikaur directory was a symlink to an NFS share, and for whatever reason this location was causing the bsdtar unpacking of the rpm to have permissions of 750, not 755.”

This makes sense as an NFS mount is not a local file system. Your NFS server is (correctly) defining your permissions as the file system is local to the server not your machine. Glad you figured out your issue.

ectospasm commented on 2019-10-31 02:29

@fryfrog: I solved my issue. See https://bbs.archlinux.org/viewtopic.php?pid=1871148 for my troubleshooting effort.

tl;dr, my ~/.cache/pikaur directory was a symlink to an NFS share, and for whatever reason this location was causing the bsdtar unpacking of the rpm to have permissions of 750, not 755.

ectospasm commented on 2019-10-14 23:56

@fryfrog

Here is a snippet of output from tar -tvf plex-media-server-1.18.0.1944-1-x86_64.pkg.tar.xz:

drwxr-xr-x root/root         0 2019-10-14 18:34 usr/lib/plexmediaserver/
-rwxr-x--- root/root   1483304 2019-10-14 18:34 usr/lib/plexmediaserver/CrashUploader
-rwxr-x--- root/root    415728 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Commercial Skipper
-rwxr-x--- root/root   4223416 2019-10-14 18:34 usr/lib/plexmediaserver/Plex DLNA Server
-rwxr-x--- root/root    239736 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Media Fingerprinter
-rwxr-x--- root/root   6576008 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Media Scanner
-rwxr-x--- root/root  21909120 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Media Server
-rwxr-x--- root/root    731336 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Relay
-rwxr-x--- root/root     12544 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Script Host
-rwxr-x--- root/root    267336 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Transcoder
-rwxr-x--- root/root   5540648 2019-10-14 18:34 usr/lib/plexmediaserver/Plex Tuner Service

So it's definitely getting stored in the pkg tarball that way. Where am I missing the permissions setting? I am using pikaur as my AUR helper, do you think that could be causing this?

ectospasm commented on 2019-10-14 23:45

@techwiz My umask for both my normal and root user are both 022, so I don't think there's anything out of the ordinary there.

I do notice some messages similar to the following (this is from my memory, I rebooted for a new kernel):

filesystem:  755  package:  750

Which suggests the package is overwriting the files with 750 permissions, even after I've set them with sudo chmod o+rx -R /usr/lib/plexmediaserver. Curiously, I did check the install command in the PKGBUILD, and it has permissions of 755. I don't know where the 750 permissions are coming from. It doesn't appear to be my umask (022 leads to permissions of 755, from what I remember about umask).