Page 2 of 2
Re: Restoring Nagios XI to factory default did not work well
Posted: Tue Feb 27, 2018 3:34 pm
by scottwilkerson
on the services page in the CCM can you click the disk icon next to one of the services and save the output and post it here.
It's line 65 of that output we need to look at because the one you checked on the file system was already reverted to a snapshot
Thanks
Re: Restoring Nagios XI to factory default did not work well
Posted: Wed Feb 28, 2018 3:54 am
by habuhejleh
Here is the output, PLease advise ASAP:
########################################################
#
# Service configuration file
#
# Created by: Nagios Core Config Manager 2.6.0
# Date: 2018-02-28 10:53:20
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################
define service {
service_description Current Load
use local-service
check_command check_local_load!5.0,4.0,3.0!10.0,6.0,4.0
register 1
}
define service {
service_description Current Users
use local-service
check_command check_local_users!20!50
register 1
}
define service {
service_description HTTP
use local-service
check_command check_http
register 1
}
define service {
service_description PING
use local-service
check_command check_ping!100.0,20%!500.0,60%
register 1
}
define service {
service_description Root Partition
use local-service
check_command check_local_disk!20%!10%!/
register 1
}
define service {
service_description Service Status - httpd
use local-service
check_command check_xi_service_status!httpd!!!!!!!
register 1
}
define service {
service_description SSH
use local-service
check_command check_ssh
register 1
}
define service {
service_description Swap Usage
use local-service
check_command check_local_swap!20!10
register 1
}
define service {
service_description Total Processes
use local-service
check_command check_local_procs!250!400!RSZDT
register 1
}
###############################################################################
#
# Service configuration file
#
# END OF FILE
#
###############################################################################
Re: Restoring Nagios XI to factory default did not work well
Posted: Wed Feb 28, 2018 10:41 am
by scottwilkerson
Ok, none of the services have a host assigned.
So in the CCM, add localhost to each of these services and click save, once they are all added, Apply Configuration
Re: Restoring Nagios XI to factory default did not work well
Posted: Thu Mar 01, 2018 6:37 am
by habuhejleh
Each one is already assigned a localhost as you can see in the attached.
Please advise why resetting to the factory default is not working with me
Re: Restoring Nagios XI to factory default did not work well
Posted: Thu Mar 01, 2018 7:48 am
by scottwilkerson
you may have to go through each as I mentioned and click save so the correct id get linked and the service re-writes the config
Re: Restoring Nagios XI to factory default did not work well
Posted: Thu Mar 01, 2018 8:37 am
by habuhejleh
Done with no luck.
I am getting this error when apply configuration "Error: Service has no hosts and/or service_description (config file '/usr/local/nagios/etc/services/localhost.cfg', starting on line 65)"
Please advise why the system is not going to factory default?! is it because on virtual machine?
Re: Restoring Nagios XI to factory default did not work well
Posted: Thu Mar 01, 2018 9:48 am
by scottwilkerson
habuhejleh wrote:Please advise why the system is not going to factory default?
I actually do not know why it is failing however it will never reset the VM, it is supposed to just remove the configurations.
The last think I can suggest is to place the attached file in
/usr/local/nagios/etc/import/
localhost.cfg
Then run Apply configuration.
This should overwrite your current setting.
If it still fails, I would suggest re-downloading the VM from our website.