I have a service in downtime - the only one for that host.
Whenever I try to delete it via the GUI as nagiosadmin I get the message "Sorry, but you are not authorized to commit the specified command."
I've tried creating other downtimes for the same service on the same host and can create & remove them OK via the GUI
It's just this one entry that refuses to be removed. Even tried writing direct to the nagios.cmd file and it won't go
Are you trying to delete the downtime logged in as nagiosadmin or another user? Can you post the service definition? Run the following commands and show the output:
Sigh.... today I was able to delete the scheduled downtime - having done nothing but just letting hours elapse since I tried it last night!
I will list what I did in case it helps any future occurrences.
I scheduled 2 Service downtimes on different hosts as myself (Admin rights)
Sometime later I deleted both downtimes as myself - one was successful, the other popped up a window saying I wasn't authorised.
I then logged in as nagiosadmin and tried deleting the downtime - again message displayed not authorised.
I then logged in as myself again and created another scheduled service downtime for the same service/host - there were now two scheduled downtimes displayed.
I then deleted both - the last one was successful, the original still displayed not authorised.
I then tried inserting the DEL_SVC_DOWNTIME command in the nagios.cmd file - still couldn't delete it.
I ran a repair of the mysql d/base in case there was a corruption - then tried unsuccessfully to delete the downtime again.
Restarted Nagios - then tried unsuccessfully to delete the downtime again.
Left it overnight.......
Tried to delete the service downtime as myself - this time it was successful.
It doesn't look like this is going to be an easy issue to troubleshoot... Did you have a chance to run the commands I asked you to run? Any weird permissions?
You can upgrade to the latest version of XI (5R1.0). The upgrade may resolve this problem. Do you have a test server, on which you can upgrade and try to recreate the issue?
Be sure to check out our Knowledgebase for helpful articles and solutions!