Package Details: plex-media-server 1.41.0.8994-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: 348
Popularity: 0.029861
First Submitted: 2014-10-14 22:11 (UTC)
Last Updated: 2024-09-26 17:02 (UTC)

Latest Comments

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 107 Next › Last »

justin8 commented on 2015-01-21 21:32 (UTC)

Hahaha.. So... I did exactly that and many other things over about 2 hours last night. and the first thing I do this morning is rm -rf ~plex/* and now the service works fine. Magic! Thanks

alucryd commented on 2015-01-21 15:15 (UTC)

justin8: Hmm, it's working fine on both an existing and a fresh install here. Can you clear /var/lib/plex/Plex Media Server/Logs, start the service and see if anything pops up in there?

justin8 commented on 2015-01-21 14:35 (UTC)

I just tried the changes you made to the launcher on a new machine, and the service fails to start. If I export all the stuff in the conf.d it runs from the terminal fine, but the service shows no real output. Just that it entered a failed state.

justin8 commented on 2015-01-13 10:39 (UTC)

Ahh, that's a bit of a pain. Thanks for the quick response though.

alucryd commented on 2015-01-13 10:03 (UTC)

justin8: The launcher script shouldn't be run directly, so I removed it altogether by moving LD_LIBRARY_PATH and TMPDIR in the conf.d file. The reason why I put them in a launcher script in the first place is because LD_LIBRARY_PATH must always be the PMS home, and TMPDIR the PMS tmpdir. It seems I can't use shell variables in the conf.d file so I must specify the full path, which could potentially be modified by whimsical users and no longer match the home/tmpdir. tl;dr Now the only way to launch PMS is with the systemd unit. stelleg: Unfortunately source_arm is unsupported, so I won't add it until it is (plus I have no way to test). BTW ALARM already has a PKGBUILD for PMS, using the Synology ARMv5 SPK.

stelleg commented on 2015-01-13 03:59 (UTC)

I've added support for arm architecture. Tested and working on goflex home. Wouldn't really recommend running on a goflex, 128MB not really cutting it. https://github.com/stelleg/plex-media-server-arm

justin8 commented on 2015-01-13 03:22 (UTC)

/etc/conf.d is for text-based config files. ususally environment files in systemd now. Definitely no binaries in there. A clean install uses the included 'plexmediaserver.conf.d' in /etc/conf.d/plexmediaserver. and it has: PLEX_MEDIA_SERVER_HOME=/opt/plexmediaserver which is called in the plexmediaserver.sh. @alucryd perhaps the plexmediaserver.sh file should source the conf.d file itself, or use some sort of default values so that running it directly will work. I get the feeling this is what might be getting people confused since it will not have a correct path. Maybe just replace export LD_LIBRARY_PATH="${PLEX_MEDIA_SERVER_HOME}" with export LD_LIBRARY_PATH="${PLEX_MEDIA_SERVER_HOME:-/opt/plexmediaserver}"

sirkingchase commented on 2015-01-13 02:16 (UTC)

@alucryd 'No, LD_LIBRARY_PATH is already set in the launcher script and I'm pretty sure PLEX_MEDIA_SERVER_LD_LIBRARY_PATH doesn't even exist' Thanks for the lead! The AUR script installs the binaries in /etc/conf.d/plexmediaserver the launcher script sets the LD_LIBRARY_PATH to the plex home directory, if you do a clean install, this script set the plex home directory to /var/lib/plex thus incorrect LD_LIBRARY_PATH Anyways, 'PLEX_MEDIA_SERVER_LD_LIBRARY_PATH' does still work but you could probably set the path in the launcher script

justin8 commented on 2015-01-07 23:12 (UTC)

@alucryd thanks, that is exactly what I was trying to say. By the way, thanks for maintaining this, it's been really solid the entire time I've used it.

alucryd commented on 2015-01-07 16:51 (UTC)

cjohnson: If there's anything true about code, especially simple code, it's that it does exactly what it's supposed to do. "systemctl enable" only creates a symlink in the dirs where the unit is wanted, period, it does nothing to the actual unit. Also if "systemctl start" didn't find the unit, there is no reason "systemctl enable" would, something definitely happened in between.

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 107 Next › Last »