<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 10pt; color: #000000'>Alex, I recently had to do the same on one of my Nagios systems (v3.5.0 on a Centos 6.4 host). From the Nagios Admin web page (xx.xx.xx.xx/nagios), select Hosts, select the host that was removed. On the right side of the page is a list of Host Commands where you can 'Disable active checks of this host' and 'Disable notifications for this host'. The same can be performed for services and checks, but I am not sure if they are needed once you disable active checks. I didn't go that far when I removed the host. Regards <hr id="zwchr">From: "Alex" <mysqlstudent@gmail.com> To: "Nagios Users List" <nagios-users@lists.sourceforge.net> Sent: Sunday, June 30, 2013 10:54:27 PM Subject: [Nagios-users] Disabling a host from all checks Hi, I have a nagios-3.4.4 system on fc17 that's working properly. I physically removed a server without scheduling downtime or indicating to nagios to disable all checks. Now that the server has been removed, I'm receiving these constant alerts saying the host is down and "connection refused" on all services. How can I remove this host from nagios checks without having to edit the configuration file and removing all references to the hostname in all of them? I'm hoping there's an easier way. If it was possible, I'd put the host back into production, let nagios check all the services, then mark the system to not check this host, but I can't. Any ideas greatly appreciated. Thanks, Alex ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </div></body></html>