On May 22, 2007, at 9:08 PM, Wil Schultz wrote: > Here is 3 minutes of the log, after i plonked a host: > > [1179892722] HOST ALERT: myhost;DOWN;SOFT;1;CRITICAL - 1.1.1.1: rta > nan, lost 100% > [1179892722] SERVICE ALERT: myhost;ciscoMemory;UNKNOWN;SOFT; > 1;ERROR: Description table : Send failure: Invalid argument. > [1179892792] HOST NOTIFICATION: myemail;myhost;DOWN;notify-host-by- > email;CRITICAL - 1.1.1.1: rta nan, lost 100% > [1179892792] SERVICE ALERT: myhost;ciscoEnvironment;UNKNOWN;HARD; > 1;ERROR: Description table : Send failure: Invalid argument. > [1179892832] SERVICE ALERT: myhost;ciscoInterfaces- > myhost;UNKNOWN;HARD;1;ERROR: Description table : Send failure: > Invalid argument. > [1179892842] HOST ALERT: myhost;DOWN;SOFT;2;CRITICAL - 1.1.1.1: rta > nan, lost 100% > [1179892842] HOST NOTIFICATION: myemail;myhost;DOWN;notify-host-by- > email;CRITICAL - 1.1.1.1: rta nan, lost 100% > [1179892842] SERVICE ALERT: myhost;ciscoMemory;UNKNOWN;HARD; > 1;ERROR: Description table : Send failure: Invalid argument. > [1179892862] SERVICE ALERT: myhost;ciscoLoad;UNKNOWN;HARD;1;ERROR: > Description table : Send failure: Invalid argument. > [1179892882] SERVICE ALERT: myhost;ping;CRITICAL;HARD;1;CRITICAL - > 1.1.1.1: rta nan, lost 100% > [1179892912] HOST ALERT: myhost;DOWN;HARD;3;CRITICAL - 1.1.1.1: rta > nan, lost 100% > [1179892912] HOST NOTIFICATION: myemail;myhost;DOWN;notify-host-by- > email;CRITICAL - 1.1.1.1: rta nan, lost 100% > > So, hot checks every minute and promptly notifies... > So host caching and parallelization(is this a word?), I'm assuming > this is in the main config file. What directives should I be > looking at? > > For what it's worth the service checks are working just fine... > > -wil > > > On May 22, 2007, at 8:32 PM, Thomas Guyot-Sionnest wrote: > >> On 22/05/07 01:02 PM, Wil Schultz wrote: >>> Looks like I may have misstated my problem, apparently I was simply >>> not receiving the HOST UP email thanks to my fat fingers mucking up >>> the hosts.cfg >>> >>> What is happening is that I am seeing a DOWN notification every >>> minute, this is why I thought I was getting the wrong alert. I've >>> got >>> a v2.7 box up and running quite nicely and I've compared the configs >>> and do not see any differences. Obviously I am missing something >>> here, any suggestions why DOWN notifications are being sent every >>> minute? >> >> Are you sure the host check is functioning properly? (try running the >> command defined in commands.cfg manually; you will have to manually >> expand the macros.) >> >> Could you send a relevant part of the history for that host? >> >> Also, looks like you're running regularly scheduled checks. Is >> that what >> really you want? Nagios 3 support running host checks in parallel and >> host state caching, but in Nagios 2 you will likely not benefit from >> running regularly scheduled host check and their serialized nature >> can >> easily cause service latency issues. >> >> Thomas >> >
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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
