Service and Host Groups disappear

[MSPk]

Hi,

We are using Nagios XI version 2012R1.0, We have recently restarted our Nagios server and when we were back ON we found that the host Groups and the Service Groups were missing. We had to restore our VM (luckily we have taken one jus before the restart) to get these groups back. Has this problem been reported by anyone else as I dont to find anyone reporting it in the forum...Is this an issue with Nagios or is it supposed to be working this way...!!!

[lmiltchev]

It is possible that you had a database corruption. This may happen after a power failure or if you shut down your VM improperly. Don't use "right click->power off". Run in terminal:

Code: Select all

shutdown -h now

If you run into a database corruption in the future, try repairing the database by running:

Code: Select all

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

Hope this helps.

[MSPk]

I see an issue with the downtime scheduled for a host or service group. If we have scheduled a downtime for a host or service group I see that the downtime is created for each host/service in the 'scheduled downtime' window which makes it difficult if we want to delete the downtime - we have delete each downtime id manually. Do we have an oiption to delete the downtime for the entire host, service group in a single shot.

[scottwilkerson]

We don't at this time but the feature has been requested, feel free to add any related comments you would like to the tracker
http://tracker.nagios.com/view.php?id=267

[scottwilkerson]

Mass deletion of downtimes has just been added to the Mass Acknowledge component (v1.6)

http://assets.nagios.com/downloads/nagi ... wledge.zip

[MSPk]

We have Implemented Nagios XI version 2012R1.8 for a client and we will be shuting down this VM tomorrow to add some capacity to it. I'm a little concerned as the clinet is not ready to take a snapshot of the VM. Should I be running through any procedure or a simple shutdown from the cli using the above command is fine? Please let me know the correct process as we cant afford to run into any issues iafter completing half the configuration.

[slansing]

Running:

Code: Select all

shutdown -h now

Is sufficient, that will allow your server to shut everything down in it's own order, and in a timely manner as not to kill off random services/processes/jobs etc..