Somehow my Steam installation (the Windows app directory, not the games library) ended up with nonsense extended Linux ACLs that were preventing Steam from opening. (I have no explanation for this—Steam had plenty of updates but unless Samba’s bugged it shouldn’t be changing Linux ACL’s, right? Other than that, I was playing with the Krusader Docker image and was just poking around and I remember looking at my Windows apps drive, maybe somehow I inflicted ACL changes? I really haven’t the foggiest…)

 

Searching support, I found the `/usr/local/sbin/newperms` script which I looked over, and seemed like it would do the job even though it was designed for pre-Unraid 5 migration and I’ve never run anything earlier than Unraid 5.

 

Unfortunately, I didn’t look at the script closely enough to see that it expected absolute paths only, and since I was in the Steam directory looking at the perms, I ran `/usr/local/sbin/newperms .`. That ended up considering `.` from the perspective of the emhttp server—and voilà, the whole tree under /usr/local/emhttp was changed to owner nobody, with all files to execute off.

 

I did a quick `chown -R root:root` and `chmod -R u+x` on it just so the server itself wouldn’t experience any permissions issue, but then I ran Fix Common Problems, and that’s been just hanging for an hour. (Update: Maybe because I started Fix Common Problems after the recursive chown, but before running the recursive chmod, I think it only managed to display the “running” pop-up; I could find no evidence it was actually running, so I reloaded the page, and was able to re-scan at a normal pace with no issues found. So that’s that…)

 

I haven’t noticed any issues per se with the fileserver, hypervisor, guests, or the GUI, but I’m worried it’s just a matter of time until a cron job or something breaks and I have no confidence I will successfully be able to reboot the host or get back up from a host crash.

 

(For my husband, at least, it’s consolation that Steam’s working now that I ran `newperms` with the correct absolute path!)

 

Is there some tool I could use to fix the permissions on the emhttp directory properly?

Edited April 30, 20233 yr by TreyH
Fixing formatting

1 hour ago, TreyH said:

Is there some tool I could use to fix the permissions on the emhttp directory properly?

 

I would just reboot as the OS is installed fresh on each boot.

I reported this exact behavior for "newperms" before but was told it was working as expected. It has a bad effect on the UI and a lot of other things.

 

The quickest way to undo the damage it did is to reboot.

For completeness here are the previous posts documenting this regression and misbehavior compared to older versions of "newperms" which worked fine with "." as current directory:

 

 

 

 

Thanks @BRiT, I agree there is a problem here. We'll get this fixed

BTW, Unraid 6.12.0 includes the fix for 'newperms'