Nagios 1.2 starting… (PID=6386)
Warning: Host ‘Barney’ is not a member of any host groups!
Warning: Host ‘Duckula’ is not a member of any host groups!
sh: /usr/local/nagios/libexec/check_load: No such file or directory
Warning: Return code of 127 for check of service ‘Current Load’ on host ‘Barney’ was out of bounds. Make sure the plugin you’re trying to run actually exists.
sh: /usr/local/nagios/libexec/check_load: No such file or directory

what check are you making?
you are missing the correct plugin in the libexec directory.
Possibily check_snmp (had that the other day… ) hasn0t compiled because NET-SNMP itself is not installed on the nagios machine.

why is it looking in /bin/check_ping ?
is that your correct plugin directory?
it’s usually in $nagios_install_dir$/libexec

Luca

PS: warning and critical values should be a timeout and a loss percentage separated by the comma…
Something like -w 500.0,20% -c 1000.0,40% would be better suited (depending on what you are pinging and how “far away” it is). Edited Fri Feb 18 2005, 03:40PM ]

OK, now I’m getting confused here. I was working with you in another thread and now I see 2 or 3 more from you. Which leads me to believe that you are good to go, in regards to your first post about trouble. But I actually don’t know for sure, since you have all these other problems.

I’d be glad to help, but communication is a 2 way thing and I never heard back in your first thread, whether or not things are ok.
If you are having trouble with check_ping using /bin/check_ping, it’s because you have a config file stating that is what the command is. For example:
minimal.cfg should have an entry of
define command{
command_name check_ping
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5
}
or maybe the above definition is in checkcommands.cfg
Also, like luca stated, resource.cfg may have USER1 set to /bin

This is what is in the “out of the box” minimal.cfg-sample file that comes with the nagios-2.0b2 and is most likely your problem.

Command to check to see if a host is “alive” (up) by pinging it

So if you used this sample, then you are going to have trouble, which is what I stated in your other thread. I have the new beta nagios working, and there are a few of these kind’s of buggy items.

It might be nice if we all adopt a policy of “one thread, one problem, one resolution”, and not start up a new thread and new problem, until you have closed your other one. In other words, it doesn’t take much to confuse me, so maybe this is just my problem, and I should just shut my trap. hehe, oh well, I’m done ranting.

[quote=“jakkedup”][size=67]OK, now I’m getting confused here. I was working with you in another thread and now I see 2 or 3 more from you. Which leads me to believe that you are good to go, in regards to your first post about trouble. But I actually don’t know for sure, since you have all these other problems.

I’d be glad to help, but communication is a 2 way thing and I never heard back in your first thread, whether or not things are ok.
If you are having trouble with check_ping using /bin/check_ping, it’s because you have a config file stating that is what the command is. For example:
minimal.cfg should have an entry of
define command{
command_name check_ping
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5
}
or maybe the above definition is in checkcommands.cfg
Also, like luca stated, resource.cfg may have USER1 set to /bin

This is what is in the “out of the box” minimal.cfg-sample file that comes with the nagios-2.0b2 and is most likely your problem.

Command to check to see if a host is “alive” (up) by pinging it

So if you used this sample, then you are going to have trouble, which is what I stated in your other thread. I have the new beta nagios working, and there are a few of these kind’s of buggy items.

It might be nice if we all adopt a policy of “one thread, one problem, one resolution”, and not start up a new thread and new problem, until you have closed your other one. In other words, it doesn’t take much to confuse me, so maybe this is just my problem, and I should just shut my trap. hehe, oh well, I’m done ranting.[/size] [/quote]

what is a slow process? Please, don’t rely on us knowing what you are talking about. Please state your trouble, and we will work through it with you.
If you are talking about “why is my ping timing out”, that is a signal that the check is not getting any response at all.
Try running the command by logging in as nagios, and running the check just like nagios would.
/usr/local/nagios/libexec/check_ping -H 127.0.0.1 -w 200,20% -c 300,30% -p 5

BTW, what did you find when you said “Yes, I found it”? Do you mean you fixed the problem with the /bin/ping? You see, that’s what I mean, we can’t just around on problems so much. One problem at a time, I’ll aready running on 13 brain cells only, due to the 70’s, so…hehe