schedule immediate check, gives "An error occured"

[lyle]

On our XI 2009R1.3G installed on Centos 5.5, clicking on "Schedule an immediate check" for a service produces "An error occurred processing your request".

The nagios.log is silent when this happens.

Any ideas, or what to check next?

Thanks....Lyle

[rdedon]

Hello Lyle,
we recently just released the latest version of Nagios XI and should hopefully fix that issue. You'll find it on http://library.nagios.com/library/produ ... loads/main.
Please do not hesitate to contact us if you are still experiencing issues or have any questions.

Thanks!
I just pasted this response from our other thread in case other people look here and are have similar issues

[mguthrie]

If the issue persists I would also try restarting the nagios process

service nagios restart

[lyle]

Despite a fresh install of Centos 5.5 (64-bit) and a fresh download (looks like Feb 2 distributioncd) of XI, this problem still exists.

I've attached a screenshot.

Thanks...Lyle

[rdedon]

I am going to change the status of this thread from "completed" back to "problem" as this issue is occurring again. I will speak with Tony and Mike tomorrow to see if we can duplicate and remedy this issue.

[rdedon]

Could you go to Admin tab and reset Component Credentials with New Config Manager Admin Password:

CredReset.jpg

There may be something that is interfering with CCM is why we are having you try this and is a quick test without changing any configuration.

[lyle]

I reset the Component Credentials password, as suggested, but still see the same problem.

This isn't the most critical problem for me, as I'm not using XI in production yet, but I'll be needing it coming up.

Thanks for the help...Lyle

[mguthrie]

Try accessing the Service Details->(selected service)->Advanced(tab), and then select the link "See this service in Nagios Core" and see if you can access that url and submit the command correctly. I'm guessing it's some sort of permissions issue with the core cgi's.

[lyle]

Great trick. I hadn't noticed the latent Core interface.

I get:

Error: Could not stat() command file '/usr/local/nagios/var/rw/nagios.cmd'!
The external command file may be missing, Nagios may not be running, and/or Nagios may not be checking external commands.

And in fact there is no nagios.cmd file. I do see "check_external_commands=1" in the nagios.cfg file. Should I create an empty file owned by nagios?

Thanks for the help....Lyle

[jtata]

nagios.cmd is a named pipe that should be created by the Nagios process when you start the service. What are the permissions on your nagios command directory (default is /usr/local/nagios/var/rw)? Mine are:

Code: Select all

drwxrwsr-x 2 nagios nagcmd