Hey guys, I replaced my cache SSD recently and several of my dockers have stopped working. After some help from the LS.IO guys on discord, we have figured out my permissions for appdata are all messed up. I prolly did something wrong.

 

What's the procedure to redo those permissions so that appdata is accessible normally again?

I just had a look at my own appdata and, while the majority of files are owned by nobody:users with mode 644, 664 or 666 and the majority of directories are owned by nobody:users with mode 755, 775 or 777, it's by no means universal. Ownerships and permissions are dependent on the docker containers themselves and are subject to the whims of their authors. Often you can configure what user a container runs as and usually the default is nobody but it can be changed and it isn't universal. That's why there's a docker-safe version of New Permissions that leaves them unchanged. Depending on how you backed up your SSD you might find that some of your appdata files are now owned by root. Maybe if you make a list of your dockers and their authors people can help you fill in the blanks.

AFAIK, the two big ones that aren't working are Let's encrypt and Nextcloud. I have the original SSD but I used the procedure in the unraid manual and I set all those shares to not use the cache, shut off docker and VM engines, invoked mover, swapped the drives, reenabled the use of the cache drive and invoked mover again. So the original drive doesn't have appdata folders on it anymore. Man, what else can I do? Im pretty useless when it comes to a lot of this stuff so setting up nextcloud and let's encrypt in the first place was not by any means an easy thing for me to do and I would prefer to not have to do it all over again.

 

Was my procedure for replacing the SSD wrong? Was there a better way to handle this?

1 hour ago, cammelspit said:

After some help from the LS.IO guys on discord, we have figured out my permissions for appdata are all messed up.

 

1 hour ago, cammelspit said:

What's the procedure to redo those permissions so that appdata is accessible normally again?

Just having some fun here, but don't they know what the permissions are supposed to be?

 

Edited November 27, 20187 yr by Squid

17 minutes ago, cammelspit said:

I set all those shares to not use the cache

The procedure is correct but that^^ isn't. If you set appdata (and others) not to use cache then the mover will ignore its files. The correct way to do it is to change from Use cache:Prefer to Use cache:Yes. Then the mover will move the appdata files to the array (preserving the permissions).

 

I don't use either LetsEncrypt or Next Cloud but as they are both security-related it's possible that they run as a specific user rather than nobody. Maybe ask in their support threads?

FWIW, all the LS.IO containers that I use run as nobody.

@John_M

Ok, I meant I did indeed set them to 'yes', mover, swap drives, set to 'prefer', mover, now it's all broken.

 

@Squid

Frankly? I have no idea... I'm still kinda sad right now tho. No idea how hard it will be to get everything just right again if I decided to just toss out my current installs of these dockers and start over. THough, following the procedure in the unraid wiki shouldn't have caused this problem I would have thought.

https://wiki.unraid.net/Replace_A_Cache_Drive

I just did what this said to do.

2 minutes ago, John_M said:

FWIW, all the LS.IO containers that I use run as nobody.

If I were to just hail mary it and make every file owned by that user, what would I do? chown? Sorry for the noob question.

For example, I have this when I look at the files. From what I have read, I don't think I am supposed to have all dashes right? This means I don't have permissions to do anything with the files. I think...

 

 

So it all boils down to the fact that mover somehow dropped my permissions on the files. I just need to know how to allow user nobody to be able to read and write these files again. I think I have some idea what's going on I just don't know how to fix it.

Yes. The dashes mean neither read nor write access. However, most of those files have zero length so only the names were copied and not the content. That isn't what mover does. If it can't move a file it leaves it where it is. There must have been some problem with the move - either it was interrupted or the destination was full. Did you confirm that the old cache drive was actually empty of files before you removed it?

Er, you know... I don't think I did. Shit, maybe those missing files are still on the SSD... It's in the server still but fully disconnected since I also added two more 10TB drives to the system and they are preclearing now. The preclear will be done later today so once that happens I can maybe pull the drive out, use a USB adapter and plug it in. If the files are there I can then see about copying them over. Hmm, that might work assuming they are still there.

 

Yeah, I think that is what I am going to do. Hope to god it fixes it. Well, I'll be sure to keep you posted but it seems I can't do anything at all in that area till tonight or perhaps even tomorrow morning. Thanks for the tip.

Had you actually created keys and certificates with LetsEncrypt? The only instance where these files could legitimately be zero length is as placeholders, before the keys have been generated. Maybe they are meant to have no access permissions by default for security purposes. Storing private keys in appdata and readable and writable by the nobody user is not very secure, is it? That would be a question for the relevant support thread.

Oh yes, I had. It had been working for months without any issues at all. My plex.domian.com cloud.domain.com all of that stuff worked fine along with the SSL certs. Nextcloud was working fine as well, I love using the auto-upload features for pics and vids I take with my phone of the family. 

I believe you have more wrong other than file permissions, however, to fix your appdata permissions for Let's Encrypt and Nextcloud do the following:

chown -cR nobody:users /mnt/user/appdata/letsencrypt /mnt/user/appdata/nextcloud
chmod -cR ug+rw,ug+X,o-rwx /mnt/user/appdata/letsencrypt /mnt/user/appdata/nextcloud

fixAppdataPerms.sh

Edited May 14, 20197 yr by JoeUnraidUser

Whelp, there was data left on the old SSD but unfortunately, it didn't work copying it over. It was only a small snippet of the databases folder for MariaDB and nothing for LE or Nextcloud. All I can assume is running the dockers without their proper data somehow damaged it beyond repair. At this point, the only thing I can do really is just going on ahead and reinstall let's encrypt, MariaDB and Nextcloud again from scratch and try to be more careful next time. Still sucks that the 'proper' procedure outlined in the WIKI was not apparently enough to work properly but I guess if I was more experienced I would have caught the issue beforehand and I wouldn't have had to deal with this problem in the first place. 😢

 

On 11/28/2018 at 5:33 AM, JoeUnraidUser said:

I believe you have more wrong other than file permissions, however, to fix your appdata permissions for Let's Encrypt and Nextcloud do the following:

chown -cR nobody:users /mnt/user/appdata/letsencrypt /mnt/user/appdata/nextcloud
chmod -cR ug+rw,ug+X,o-rwx /mnt/user/appdata/letsencrypt /mnt/user/appdata/nextcloud

 

Running into this issue now too. the chmod for letsencrypt gives the error chmod: invalid mode: ‘ug+rw,ug+X,o-rwx’

try it again.  I repasted into the post for some reason there was a special character pasted in the code.

chown -cR nobody:users /mnt/user/appdata/letsencrypt /mnt/user/appdata/nextcloud
chmod -cR ug+rw,ug+X,o-rwx /mnt/user/appdata/letsencrypt /mnt/user/appdata/nextcloud

 

Edited May 2, 20197 yr by JoeUnraidUser

does it translate to 777?

 

edit: same error chmod: invalid mode: ‘ug+rw,ug+X,o-rwx’

Edited May 2, 20197 yr by dbinott

Try it one more time.  I repasted it.

1 minute ago, JoeUnraidUser said:

Try it one more time.  I repasted it.

same. what is the numerical value? be easier.

It doesn't equate to a number.  I have attached the script that I use.

fixAppdataPerms.sh

Edited May 2, 20197 yr by JoeUnraidUser

1 minute ago, JoeUnraidUser said:

It doesn't equate to a number.  I have attached the script that I use.

fixAppdataPerms.shUnavailable

ok, well that worked. Now if I could only actually see the containers on the docker page. any ideas about that?

 

Lately, for some reason, copy and paste doesn't seem to work correctly for posting code.

 

Sorry, I'm not sure how to fix the other problems.

Edited May 2, 20197 yr by JoeUnraidUser

np, thanks for the help.

Lately, for some reason, copy and paste doesn't seem to work correctly for posting code.
 
Sorry, I'm not sure how to fix the other problems.

Copying and pasting from the forum more often than not inserts hidden characters

Sent via telekinesis