view host -> Not Authorized

[jbennett]

I did as you suggested, and it looks like I have some corruption in the DB:

NagiosXI ndo2db: mysql_error: 'Table './nagios/nagios_timedeventqueue' is marked as crashed and last (automatic?) repair failed'

Is there a built in method to clean this up?

A quick search on Google yields this: http://networking.ringofsaturn.com/SQL/ ... repair.php

Should I follow this?

Appreciate the help!

[scottwilkerson]

Use this procedure
http://library.nagios.com/library/produ ... i-database

[jbennett]

I ran the script and it did find a number of things that needed to be cleaned up.

However, I'm still having the same issue with users that should be able to see the host.

Not Authorized
You are not authorized to view the requested object, or the object does not exist.

[scottwilkerson]

Did you run the full repair of the database

Code: Select all

/usr/local/nagiosxi/scripts/repairmysql.sh nagios

Or just on the one crashed table you saw?

[jbennett]

I ran what was suggested int eh documentation:

/usr/local/nagiosxi/scripts/repairmysql.sh nagios

Ran it again and I'm still getting the same error.

[scottwilkerson]

Do you mean you still have the database corruption?

[jbennett]

It did find some issues, not nearly as much as before though.

Once the tool ran, I checked again as the user and I'm still getting the same error telling me that I'm not authorized to view.

[scottwilkerson]

By any change had you attempted to upgrade nagios core or ndoutils individually outside of an Nagios XI upgrade?

Also, can I have you run the following to make sure we don't have multiple copies of either running

Code: Select all

service nagios stop
service ndo2db stop
killall -9 nagios
killall -9 ndo2db
service nagios start
service ndo2db start

[jbennett]

I cannot say for sure prior to my getting control over the box. The guy that installed and configured the box previously didn't share much information about anything before he left.

Since I've had control, I have updated the CCM to the beta version that was suggested here on the forums for an issue I was running into.

I have rebooted the machine to be sure it wasn't some sort of fluke there, and I've killed the processes as you have outlined, yet I'm still experiencing this issue.

Since we are moving to a new box, I'm wondering if the issue will follow, or if it will be resolved at that time. I'm hooing to have the new install up and runnin gin the coming weeks, so I might just hold off on digging deeper on this issue until I know that we have the same issue on the new box.

Thanks for the help!

[mguthrie]

It is worth mentioning that users who are authorized at the service level will be able to see the colored status of the host, but if they are not authorized at the host level, they will get that message when they try and access the host details. Users authorized at the service level are only allowed to know if the host is up or down, but they are not allowed to see details. I'm wondering if that's the case here.