kwhogster wrote:Yes the all spike at the exact same time
I sent a lot of info on this
Someone must know why
rkennedy wrote:I haven't seen in this post if the nagios user (or whoever you're running NRPE under) is able to actually run your script locally. Give that a try and get it working, then watch your /var/log/messages on the client machine when running the checks through NRPE AFTER you get it working locally.
kwhogster wrote:Does this also apply to Nagios Core 4.1
I all the suggestions on here not one was to change anything All I get is please send me this and send me that.
kwhogster wrote:I do not see any comment about only_from =
it was allowed_hosts=127.0.0.1,10,2,8,79
I did that and the -n did not work as I replied with the results
Where is only_from?????????????
this warning comes up a lot
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages. which the doc talks about arguments but other times it checks fine
So that is a false positive
Just like when the Linux servers spike again all false positives
tmcdonald wrote:Quite a few things going on here:
1.) Did you ever follow the advice of @tgriep in this post? User @ssax posted right after so you might not have seen @tgriep's post.
2.) Your output here seems to indicate that the server does not have the proper glibc version, which indicates to me that the plugins might have been copied over from an incompatible system. Can you please elaborate on how you got the plugins installed on each of these systems? The specific error I am referring to is:
/usr/local/nagios/libexec/check_load: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/local/nagios/libexec/check_load)
3.) As has been pointed out, this is not an issue of Nagios causing the high load. I know because the load averages are for 1, 5, and 15 minutes respectively in output such as this from your first post:
Current Load CRITICAL 03-02-2017 20:46:26 0d 0h 5m 42s 4/4 CRITICAL - load average: 0.99, 7.56, 4.89
That means that at the time the Nagios was check was run, the 1-minute load average was just under 1, which on most modern systems is not awful. Since a Nagios check typically doesn't take more than a second to run, it would have to be a bug of astronomical proportions to cause your 15-minute load to be higher than your 1-minute for an instantaneous check (astronomical here meaning "involving time travel and probably quantum physics")
Balance of probability puts this as a misconfiguration, as was pointed out early on in the thread. You had each of your remote checks configured to run a check not on that remote machine, but on the Nagios server itself. That is why all the loads were so identical - they were checking the same machine at roughly the same time.
I understand this is frustrating, but NRPE issues are some of the most common and solved problems we see on a daily basis. We have a 26-page PDF detailing everything we know about NRPE issues, and their solutions.
kwhogster wrote:Where is only_from?????????????
Users browsing this forum: No registered users and 7 guests