Jump to content

TODDLT

Members
  • Content Count

    855
  • Joined

  • Last visited

Community Reputation

5 Neutral

About TODDLT

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Charleston, SC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have migrated from one plex docker to the other and now ready to delete the old docker. The new install is mapped to the location of the old appdata rather than it's own default location. Question is when I remove the old docker, is it going to try to remove it's default appdata, which is now used by the new docker? Is there any way to prevent it? Should I also be checking "also remove it's image"? I don't want un-necessary software hanging around, but dont want to delete the data still being used. It would be a train-wreck to re-create it. thanks.
  2. I recently went through some difficulty with my Plex docker and permission rights for files. It took a week of back and forth on two sections of the forums before I had the answer. In the end it was a simple fix but it seems like very few know its there or can be an issue. I would assume this could potentially affect or be useful in other dockers as well. --Issue-- I use the Plex DVR with the Linuxserver.IO Plex docker. The video files being created by the Plex DVR were being created with limited access rights for anyone but the user "nobody" the owner of the file. I could not move, rename, delete any files without first running the "new permissions" utility on unRaid. --Cause-- linux has a UMASK default of 022, but this is not compatible with the unraid system. This limits user access to the user/group that created the folder and/or file, in this case "nobody." UMASK of 0000 will mean that all files / folders will be r/w access for all users with the appropriate permissions in unRAID. --Fix-- The Plexserver.IO docker has a variable for UMASK that isn't in the default list when first installed. You can add in the docker settings UMASK_SET, and you then assign 0000 there. This resolved the access rights issues to the DVR created files. If this is helpful to others, certainly can be added to any FAQ
  3. so marked (and I was looking for a "solved" button). The answer came inside the LinuxServer.IO - PlexServer forum. I did reply that it solved the issue, and the fix was simple. In the end they do have a variable setting for UMASK available, its just not in the default list, so you have to add it manually. If there is somewhere I should post a summary write up I'd be happy to contribute.
  4. This is now solved. LinusServer.IO provided info on setting the variable for UMSASK
  5. Thanks for this. I set it tonight and now recording.. Hopefully its resolved.
  6. thanks for all the effort above. I will try to do the script in the next couple days and test it, hopefully tomorrow. I did post a note in the support forum here for LS.IO. I used the stats on the folder you saw above, but I also tried to use the "stat" command you mentioned. The real issue I had is I can't seem to call out the full directory name in the terminal because it shows a syntax error with the "(" character. All the folders and files created for media contain the year made in "(yyyy)" syntax. I get errors when tryring to type that. Is there a way around this?
  7. I've had some earlier posts, about the permissions granted for files that are generated by the Plex DVR using the LinuxServer.io docker. I started a new thread in the general forum looking for more help on the subject : https://forums.unraid.net/topic/82188-file-permissions-issue-with-plex-docker-linuxserverio/?tab=comments#comment-763917 I've had some help there and the most likely issue is the UMASK variable and I'm posting the basic info here so someone can look into a permanent fix. This would only be a problem for someone using the Plex DVR feature and then also wanted to be able to move or delete files that have been created by Plex. I know you can delete files from inside Plex, but 1. I dont want anyone logged in on a TV in my house to be able to make that mistake, and 2. There would still be a host of files and directories that can only be modified by plex, unless the "new permissions" utility is run. There is a lot more information if you go follow the thread in that link, but here are the highlights: Here are the permissions shown using the ls -al /mnt/user0 command: This folder was created using the Plex DVR drwxr-xr-x 1 nobody users 33 Jul 30 20:05 Bxxxxxg\ (2019)/ a similar folder that was created from the old plex (Limetech docker) DVR reads like this drwxrwxrwx 1 nobody users 52 Mayt 15 22:31 Bxxxxxxx\ (2017)/ His comment was: The umask 0000 needs to be called in the docker after the filesystems are created - in whatever entrypoint script is being used. I'd file this as a bug with the LS.IO guys on github or in their support thread. You can readily prove that the UMASK isn't being set properly; EDIT: attached is a screenshot of the file/folder stats created by the Plex DVR. I hope this is enough to get something going. If this is incorrect and the UMASK setting is correct already please let me know.
  8. Not everyone on Plex uses the DVR, and so for most users, they probably would never see files "created by Plex" that they accessed or wanted to modify outside of Plex itself. I'm not sure what they will say about the request because maybe it is more secure for the app data files that may be created by the docker, and not sure they can differentiate between those and the DVR created files. So all that being said, I would probably use this short term, or long if they don't make the change. Creating a userscript that simply says "unmask 0000" would be pretty straight forward and I use a couple user-scripts. However, I'm not sure what this script would look like to "add the line to their entrypoint script and restart the docker." Is there a way to write a script that would run in the proper sequence at the startup of unRaid to get this setup, and why would it revert or need to be run every day or so?
  9. Sorry, it's taken me a few days to get back into trouble shooting this issue, just been a little busy here. Thanks for taking the time to explain all this and I think I'm following this correctly. I've learned a little bit about what's going on in the background on this one. So where do I put this UMASK command? Is this a variable I should set in the docker or a command line that needs to be run every time the docker is started? Thanks again
  10. I just took a quick scan of this..... not exactly light reading so looks like project for tonight. Thanks for the info and the time to dig it up.
  11. Can someone explain the variables for PUID and PGID in the Docker settings (at the end)? The default values are 99 and 100 respectively. These are User ID and Group ID settings, correct? What do the values mean, or is this where it determines the user ID the docker operates and creates files under? I posted a thread in the General forum https://forums.unraid.net/topic/82188-file-permissions-issue-with-plex-docker-linuxserverio/ and after a little investigation this was the summed up message: The Limetech docker did not have this permissions issue and also did not set values for PUID or PGID, or if it did, there were no adjustable settings for it. Is it possible these settings are what is causing the issue? Can they be changed or what happens if I delete them? Thanks as always.
  12. Thanks, so this did trigger I thought. There are values in the docker settings for PGID and PUID. I think this stands for Plex UserID and Plex GroupID. (P=Plex is an assumption on my part but I think GID and UID is correct). They have numerical values: PUID = 99 and PGID = 100. I looked back and the older Plex Docker did not have any settings for these values. Should I just remove the values? or should they be changed? No idea what those values actually mean.