I agree it sounds logical that check_ping uses one packet, then however many you have set after that. So thanks to everyone who pointed that out!
If I can get things straight so it doesn't do so many host checks, I'll probably revert back to the default number of ping packets. (Or maybe go for 4 instead, to actually get my 20-40-60-80% results) >> Also, along those lines... I recently moved from the 1.2 Nagios to the >> more recent 2.4-2.5 Nagios. Nagios 1.X seemed to only trigger a host >> check if a service check failed. Nagios 2.X seems to ALWAYS run host >> checks in addition to service checks. The fact that host checks are >> currently not run in parallel seems like this can really limit performance. >> >> Why did that behavior change? > > It didn't. Or rather, it wasn't supposed to. I haven't seen anything of > the kind in any of our ~160 customers installations, so I'm fairly > certain this doesn't happen for all setups. What does your nagios.log > report on the ~15 lines prepending the host-check entry? I should add that I'm using Monarch from the GrounworkOpensource.com guys. I'm using their latest open source version, which I believe is 4.5.11 or something like that. It came with, um, some version of Nagios that I can't immediately identify. Possibly as old as 2.0. (How can I confirm the current version of Nagios?) I've thought about upgrading the Nagios that comes with Monarch. I've seen posts in their forums on how to do that, although they say it is unsupported. Monarch imported our existing Nagios 1.X configuration, but it looks like this was one of a few mistakes it made. I see it is indeed now set to have a check_interval for each host, as well as for each service. (Not like it used to be!) I'll go update the Monarch config; sounds like that'll take care of that part. I assume I just remove the value from the host's check_interval completely? Here are the last few lines from nagios.log: [1166030882] SERVICE ALERT: Authentication1;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 25.15 ms [1166030891] SERVICE ALERT: whi-whwt;SNMP2;UNKNOWN;SOFT;2;SNMP problem - No data received from host [1166030901] SERVICE ALERT: 2river-210west;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 40.62 ms [1166030901] SERVICE ALERT: plum-rokap02;PING;CRITICAL;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 19.04 ms [1166030901] SERVICE ALERT: les-termap01;PING;CRITICAL;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 25.81 ms [1166030911] HOST ALERT: 2river-ap01;DOWN;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 24.82 ms [1166030913] HOST ALERT: 2river-ap01;DOWN;SOFT;2;PING CRITICAL - Packet loss = 50%, RTA = 25.33 ms [1166030913] HOST ALERT: 2river-ap01;UP;SOFT;3;PING OK - Packet loss = 0%, RTA = 12.41 ms [1166030937] HOST ALERT: crn-ap04;DOWN;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 15.69 ms [1166030937] HOST ALERT: crn-ap04;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 17.17 ms [1166030940] HOST ALERT: doug-pwr;DOWN;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 23.90 ms [1166030940] HOST ALERT: doug-pwr;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 17.42 ms [1166030982] HOST ALERT: plat-ap01;DOWN;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 12.12 ms [1166030982] HOST ALERT: plat-ap01;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 11.75 ms [1166031011] SERVICE ALERT: whi-whwt;SNMP2;UNKNOWN;HARD;3;SNMP problem - No data received from host [1166031021] SERVICE ALERT: wmn-ap01;PING;CRITICAL;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 7.19 ms [1166031021] SERVICE ALERT: plum-rokap02;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 53.29 ms [1166031021] SERVICE ALERT: les-termap01;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 62.16 ms [1166031027] HOST ALERT: wmn-ap01;DOWN;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 8.95 ms [1166031027] HOST ALERT: wmn-ap01;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 9.09 ms [1166031139] HOST ALERT: 2river-210west;DOWN;SOFT;1;PING CRITICAL - Packet loss = 50%, RTA = 28.75 ms [1166031139] HOST ALERT: 2river-210west;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 15.85 ms [1166031141] SERVICE ALERT: wmn-ap01;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 9.76 ms Thanks again for everybody's input!! ;) (Have I mentioned that I love Nagios? I've used it *forever* -- remember NetSaint? -- and it's pretty hard to beat!) -- Jason Byrns Production Manager System Administrator http://www.MicroLnk.com/ 402-328-8600 ext. 653 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
