(04-07-2019, 07:18 AM)TGates Wrote: Looks like there are many permission problems. ALL Sentora files/folders should be owned and grouped by www-data:www-data (or apache:apache depending on OS)
What OS are you using? (I'm guessing CentOS because the info matches my virtual machine of CentOS)
Is this a new install? You may need to reset and start over.
Did you install Sentora as actual root user? Using sudo will not work as explained in the install documentation.
Eh, I'm confused now... Even my VM shows the Sentora main as root:root??
@[fearworks], can you confirm this? Any ideas what the issue is? (I'm more affluent with Ubuntu than CentOS)
All of my permissions are the same as the OP's. Even my Sentora folder is root:root, so I'm guessing that CentOS have changed things since Sentora's 2015 release? I've not had permissions issues with anything so for me this has always been the setup and it has been working without issue.
As for the error message, I also have those lines in my bind logs, and they are to do with the service being stopped (including when restarted). If you look here:
https://bugzilla.redhat.com/show_bug.cgi?id=1487823
you will see a discussion about the issue, which is linked to permissions on the named home directory. AFAIK the inability to write these NTA files is irrelevant to the way bind is used by Sentora so TBH, I don't care about the entries. However if we want to fix this I have just tried:
Code:
chmod 775 /var/named/and now whenever I restart the named service those errors aren't being generated.
So, in summary, there's some sort of bug in the release of bind used by CentOS 7 (and maybe others?) that seems to alter the permissions of the directory in question upon installation, and we have to change these permissions back to allow writing.
That's my assessment of the situation, but as I'm not an expert I could be completely wrong, so if you think I am - tell me!
Keith.
