Arch Linux User Repository

Ok yea.. I see the logs issue adding that.. Now working on the plugins part. Man I could have sworn this was working.. Must've been legacy library crap I had. Will have version 12 up tonight

Found it.. chown -R from the installer didn't work. I'll upload a new src. Guess the discussion about where to run the chown from (install or start_pms) made it get lost in translation :)

PPS - I am going to blow away my Library directory and install it "realclean". I'll see if the installer needs to create Logs. I'm not dismissing your finding :)

Thanks all. Yea the install script doesn't create any directories other than /usr/local/plexmediaserver, and then basically extracts the .deb file from plex into that directory. It then chown -R plex:plex all the files in /usr/local/plexmediaserver Now, here's how I've been testing it, and is probably how it got confusing. Between versions, to check things I just run "sudo pacman -R plexmediaserver". This removes all files, with the exception of /usr/local/plexmediaserver/Library. It will also rename /etc/conf.d/plexmediaserver to /etc/conf.d/plexmediaserver.pacsave. Then I just reinstall it with "sudo pacman -U plexmediaserver.xz" The installation process unpacks everything. Since the "Library" directory didn't get deleted (i.e. the default Application Support directory) nothing gets lost and when you start Plex up it auto creates the directories it needs. Now if you want to run this as another user (or as yourself), you need to make sure A> You've edited the /etc/conf.d/plexmediaserver file to have your username instead of "plex" in PLEX_MEDIA_SERVER_USER B> Either comment in PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR and point it to a directory that the user you defined above has FULL access rights to, recursively. If you don't define this, it will default to "/usr/local/plexmediaserver/Library/Application Support". You MUST make sure your userid from above can write to this directory recursively. The "start.sh" script you referred to is legacy and is not there in current releases.. Just use the "start_pms" script to run it (or more accurately, just run "sudo systemctl start plexmediaserver" TL:DR - Always make sure the user you run Plex as has full read/write to whatever is defined as PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR

Sorry if I was unclear tmoore, my issue was similar to everyone elses in regards to the plugins not automatically being created (and Logs dir as well) due to permission issues. Unfortunately after fixing permissions the plugins did not get created and plex just bombed. To resolve it (since I rely on Plex more than my cable subscription. ha) I simply edited the conf.d appropriately to point back to my original install/plugins since I had a large setup already that I wanted to preserve. However, for new installs from scratch it appears to be slightly borked permission wise or missing a step to create those plugins/Logs dir. :)

Eskimod got it, this assumes though that plex has been successfully run and the plugins were built in /usr/local/plexmediaserver/Resources/Plug-ins/ ...if you did what I did and killed the whole directory, try cd to /usr/local/plexmediaserver then ./start.sh this will startup the plexmediaserver as the currently signed in user, then kill the process with top/pkill then the plugins should be built...this is all very roundabout way I'm sure there is a much easier way out there.

Just fixed this problem. stop the plexmediaserver sudo systemctl stop plexmediaserver.service sudo chown -R plex:plex /usr/local/plexmediaserver cd /usr/local/plexmediaserver sudo rm -rf Library/Application\ Support/Plex\ Media\ Server/Plug-ins/{System.bundle,Framework.bundle} sudo cp -r Resources/Plug-ins/{System.bundle,Framework.bundle} Library/Application\ Support/Plex\ Media\ Server/Plug-ins/ start the service sudo systemctl start plexmediaserver.service

Could you share exactly what you did? Because I'm having the same problem.