Nagios Support Forum

Directories likely will need X, actual config files should only need nagios user and group(at least one that nagios is a part of, not necessarily the nagios group) read access. Also make sure that all of those files and directories listed in nagios.cfg do exist even if they are empty. It would make sense if your verifications were done as root, that you didn't see this before, as nagios will drop permissions before verification.

so just to test permission of nagios I chmod 777 -R the objects and private dir.
The script still failed on the same objects and private/resources.cfg
I dropped to the nagios user and ran nagios -v (nagios.cfg path), and the validation passes.
Is the script being run as the from the init.d NagiosUser=
I have it set to nagios currently.

-PS Thanks for all the help

What were you running it with before? Another random user, or root? I believe you should only be able to control the init script as root or nagios. If you can verify that it did not work as the root user then we might have another issue.

have been trying to execute the init script "service nagios start" as root.
The init.d/nagios is configure as user/group nagios.
The file permissions are 100% out of the way and it still errors on those two dir.

right now i am just running nagios -d (configpath)
then killing the process and removing the files that are specified under the init scripts stop section.

What do you get if you run the following

-rwxr-xr-x. 1 root root 892 Mar 18 13:36 /etc/nagios/private/resource.cfg

The dot at the end of the file permissions leads me to believe we migh have SELinux permissions set on the file...
Is SELINUX enabled on the machine?

BAM!!!

Works once I know the system was running SELINUX.
Why its always good idea to check the installed packages when you dont install the OS.

Thanks again for all the help when it came down to a system issue.

Good to hear! I'll be locking this thread now but feel free to open another if you need help in the future.