Package Details: plex-media-server 1.41.2.9200-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.012947
First Submitted: 2014-10-14 22:11 (UTC)
Last Updated: 2024-11-14 23:11 (UTC)

Latest Comments

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

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.

cjohnson commented on 2015-01-07 16:17 (UTC)

There were no other steps performed, nothing else changed. Maybe the set of circumstances for you is different than for me. I'm a software dev too and I'd say it's important to have every user's reports, not just the ones that work how I expect they should. Should somebody else come along with the same set of circumstances that cause the same set of issues as me, they might find a solution to their specific problem. I'm not saying we need to submit a bug report, if it seems to work okay for you, but I am saying that: * Start failed to run, again and again and again * I ran the enable command * Suddenly start works I agree it doesn't make any sense why that would matter. But it obviously did. So it's worth noting, that's all. Anyway, my issue is resolved, no sense arguing over it.

justin8 commented on 2015-01-07 06:10 (UTC)

It is of net negative worth if there is incorrect information about how a problem was 'fixed'. Out of curiosity I thought I would double check what it does. If you read through these two: https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c https://github.com/systemd/systemd/blob/master/src/shared/install.c You'll see that after checking if it's masked or a template and pushing dbus notifications, that all it does is create the symlink. I can't explain how your issue was fixed, but I can say with certainty that it was not by enabling the unit.

cjohnson commented on 2015-01-07 05:33 (UTC)

Still... I ran "start", it gave the error. Then I ran enable. Then I ran start again, error went away. Something else is definitely happening or the lack of that symlink is causing it not to work, in my situation. Maybe nothing much to go on now but worth noting in case the issue re-surfaces I guess.

justin8 commented on 2015-01-07 05:24 (UTC)

All enable does is create a symlink in /etc/systemd/system/multi-user.target.wants/foo.service to the service file in /usr/lib. It doesn't do anything else. Here is an example of it being installed and started on my work laptop; it has never had plex server installed on it before: http://hastebin.com/oqivirulel.avrasm

cjohnson commented on 2015-01-07 04:23 (UTC)

@justin8: I wasn't able to start the service until I had "enabled" it as per tmoore's suggestion. Before enable, it gave the error in my previous comment. So it seems as if it actually _is_ needed to start the service. Remember, I deleted *all* plex related files before installing the latest version just to be sure I wasn't running into a conflict. Are you totally sure? What else might have been the issue if so?

tmoore commented on 2015-01-07 03:56 (UTC)

Hmm.. I always thought you had to run it at least once to get the symlink created from /usr/bin to /usr/lib/systemd... Learned something new.. but hey, it fixed it somehow :)

justin8 commented on 2015-01-07 03:54 (UTC)

Your assumption was correct. enable only enables it for load on startup. You do not need that to start the service.

cjohnson commented on 2015-01-07 03:46 (UTC)

Haha, not stupid at all. I was under the impression the "enable" command was for automatically starting the service on start. I didn't realize you needed to enable it to be able to start it. Works perfectly now. I don't recall having to do this on the older version of the package... am I crazy? Did it used to do this for you?

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