Greetings: I am trying to use the latest Nagios 3.2.3 packages on a CentOS 5.5 64-bit virtual machine. I started with an up to date CentOS 5.5 install, added the rpmforge repo, and then installed the nagios, nagios-plugins, and nagios-plugins-setuid packages.
I am using the default nagios.cfg that came with the package for testing. My problem is that the nagios service won't start using the normal tools. When I try start the service using "service nagios start", I get an error back saying "Configuration validation failed". What's unusual about this is that if I validate the configuration by hand "nagios -v /etc/nagios/nagios.cfg", it returns as valid, with 0 warnings and 0 errors. I also tried a manual verification as the nagios user "su - nagios; nagios -v /etc/nagios/nagios.cfg", and that validates correctly as well. Additionally, if I start the service manually "su - nagios; nagios -d /etc/nagios/nagios.cfg", nagios starts up and runs properly. Once I have manually started the service, things like "service nagios status" and "service nagios stop" all work properly, but once the service is stopped, you can't use the service command to start it again. As part of my troubleshooting, I modified the /etc/init.d/nagios file's check_config() function so that instead of piping the output of the config check to /dev/null, it printed it out on the screen. When I run the modified service start, it reports that there is an error in the configuration file at line 465, and that the directory is not valid. Line 465 in the default configuration file is "check_result_path=/var/nagios/spool/checkresults". I have verified that the specified directory exists, is owned by nagios:nagios, and has appropriate permissions (755), and that there are no SELinux denies being generated. It seems that there is something different about the environment that /etc/init.d/nagios runs in than the normal environment. I don't know enough about the CentOS startup scripts to really go beyond that. If it's not too much trouble, could someone try installing nagios and see if they get the same behavior with the default config files? And any pointers as to how the environment that /etc/init.d/nagios gets run in differs from a normal environment would be appreciated. Thanks for your time. -Scott
_______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
