Appears almost all the time "We have some files that are owned by a different user than librenms"

[hrv231]

• Steps to reproduce an issue.
  I don’t know how to explain to reproduce this issue.
  I have been having this problem for a while now, every time that run validate to the system, it always shows me to run the sudo chown -R … commands, I do that, and then the next day the same [FAIL] appears again.
  I have the system to automatically update, I keep running suudo chown -R librenms…etc , but still, after a while when I run validate again, it shows the same.

• The output of ./validate.php
  

  
  
  If it’s an issue with the WebUI then please consider including a screenshot and the browser version you are using.

[Magumbo]

I get the same, after every run of .daily.sh then ./validate.php then fixing them then ./validate.php again.

[Kevin_Krumm]

Mostly likely it’s because you are running those commands as root. You need to run them with librenms user.

[Magumbo]

That sounded reasonable, but after manually running daily.sh as the librenms user, then validate.php as root, i got the same errors.

[Chas]

See this thread probably same cause

Why does this keep happening? Issue with file permissions

Every so often I do a validate.php and see the [FIX] error about file permissions. I then fix it and it comes back. I haven’t check in weeks and just saw this today. Any idea of what is going on? (I did do the file permission changes again and now everything is fine but still wondering why it would revert back.) [OK] Composer Version: 1.7.2 [OK] Dependencies up-to-date. [OK] Database connection successful [OK] Database schema correct [ FAIL ] Some folders have incorrect file permissions, th…

[Magumbo]

Better to fix the problem at source, by refining the check, than to add a compensatory workaround

[hrv231]

So unfortunately, this is an issue.
I don’t understand how other people haven’t said anything about this, because my installation of librenms is by the book, I haven’t changed too much in the config, and even when I ran all the commands again with librenms username (I had to put it first on the sudoers), still the error appears.