Unable to schedule downtime for a hostgroup

[chelch]

Hello,

I am receiving the following error when attempting to schedule downtime for a host group. I am attempting to complete this task using our Nagios Administrator login which has admin access.

"Sorry, but you are not authorized to commit the specified command."

[npolovenko]

Hello, @chelch.
Are you using Scheduled Downtime form the Incident Managment menu in XI? Also, can you schedule downtime for an individual host just fine or will it give you the same error?
Could you upload your Nagios XI System Profile so I can review it?
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it in this forum or send it in a pm. If you send it in a pm please let us know here when you do that.

[chelch]

Hello,

The way I am attempting to schedule downtime is by clicking on hostgroup summary on the left and then next to the host I am clicking the black box that says "view hostgroup commands". From there I am attempting to schedule downtime for a host group. I actually did this with no problem a few months ago so not sure what changed.

When I try and schedule downtime for an individual host under incident management it schedules fine. I have PM'd you my profile

[npolovenko]

@chelch, I received it, thanks. Please make a backup of your system first:
In XI web interface go to Admin/ System backups in the left column, Local Backup Archives and create a backup.
After that in linux console go to this folder:

Code: Select all

/usr/local/nagios/scripts/

and run

Code: Select all

sudo ./reset_config_perms.sh

and then

Code: Select all

./repair_databases.sh

After restart nagios and httpd:

Code: Select all

service nagios restart
service httpd restart

Let us know if that resolved your problem.

[chelch]

Ran through all steps and same issue. Was able to fix by just removing the host group and recreating. Any idea what would cause this behavior?

[dwhitfield]

The repair script doesn't always fix everything in the db. We may have been able to fix it by running more advanced fixes, but since it's fixed, do you want to go ahead and lock the thread?