Terry L. Inzauro wrote: > List, > > I have an odd occurrence that I cant seem to work out. > > I have a host with various services defined that belongs to a hostgroup and > such. The other day, the host had some IP issues > that cause nagios to report that the services were down. After the host came > back up, there was one service (check_dig) that > still reported as being down. All other services were fine (check_ssh, > check_users, check_load, check_ping, check_procs). > > The only workaround that allowed the check_dig to return to normal was to > change the 'host_name' and 'alias' in the host > definition. > > host_name host-mgmt > alias host.dom.tld > > It seemed that there was a cached or stale entry stored somewhere....Any > ideas as to why this would be? >
Does the host get its IP from DHCP? If yes, I'd assume the check_dig-based service check tried to verify that the host itself had a certain IP but it got a different one when you brought it back up, although why you'd want to resolve the name of a host with dynamic ip-assignment is beyond me. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Register now for Nordic Meet on Nagios, June 3-4 in Stockholm http://nordicmeetonnagios.op5.org/ Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ 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
