Hello.
Sorry if this is not the right place for that kind of question.
I have installed Freebsd9 with nrpe 2.15.
In messages I have that kind of errors:
Feb 12 04:06:54 tovo nrpe[57585]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 04:18:16 tovo nrpe[57613]: Host 192.168.1.77 is not allowed to talk to us!
Feb 12 05:06:53 tovo nrpe[57747]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 05:18:18 tovo nrpe[57775]: Host 192.168.1.77 is not allowed to talk to us!
Feb 12 06:06:54 tovo nrpe[57907]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 06:18:19 tovo nrpe[57935]: Host 192.168.1.77 is not allowed to talk to us!
Feb 12 07:06:56 tovo nrpe[58065]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 07:18:19 tovo nrpe[58093]: Host 192.168.1.77 is not allowed to talk to us!
Feb 12 08:06:52 tovo nrpe[58223]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 08:18:20 tovo nrpe[58251]: Host 192.168.1.77 is not allowed to talk to us!
Feb 12 09:06:51 tovo nrpe[58391]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 09:18:20 tovo nrpe[58423]: Host 192.168.1.77 is not allowed to talk to us!
Feb 12 10:06:52 tovo nrpe[58579]: Host 192.168.1.79 is not allowed to talk to us!
Feb 12 10:18:20 tovo nrpe[58607]: Host 192.168.1.77 is not allowed to talk to us!
34 is Nagios Server. 77 and 79 are Kaspersky AV server working under Windows OS.
In nrpe.cfg I have:
allowed_hosts=192.168.1.34,127.0.0.1,192.168.77,192.168.1.79
When remove 77 and 79, messages are changed to:
allowed_hosts=192.168.1.34,127.0.0.1
Feb 12 12:06:52 tovo nrpe[58985]: Could not read request from client, bailing out...
Feb 12 12:18:21 tovo nrpe[59021]: Could not read request from client, bailing out...
Feb 12 13:06:53 tovo nrpe[59154]: Could not read request from client, bailing out...
Feb 12 13:18:21 tovo nrpe[59188]: Could not read request from client, bailing out...
Feb 12 14:06:54 tovo nrpe[59336]: Could not read request from client, bailing out...
Feb 12 14:18:21 tovo nrpe[59364]: Could not read request from client, bailing out...
Feb 12 15:06:53 tovo nrpe[59500]: Could not read request from client, bailing out...
Feb 12 15:18:23 tovo nrpe[59529]: Could not read request from client, bailing out...
What could be the problem ?
nrpe error
-
npolovenko
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: nrpe error
Hello, @netaccs.
Are you running NRPE as a standalone daemon or under xinetd? You may need to add the allowed ip's to /etc/xinetd.d/nrpe.cfg
In that config file separate IP addresses with spaces, not with commas.
Make sure to restart nrpe with:
You missed 1 in 192.168.1.77.allowed_hosts=192.168.1.34,127.0.0.1,192.168.77,192.168.1.79
Are you running NRPE as a standalone daemon or under xinetd? You may need to add the allowed ip's to /etc/xinetd.d/nrpe.cfg
In that config file separate IP addresses with spaces, not with commas.
Make sure to restart nrpe with:
Code: Select all
service nagios restart
or
service xinetd restartAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: nrpe error
I am Sorry for delay.
I am using nrpe daemon on computers.
It is somehow connected with kaspersky antivirus server. I have two server with KAV installed on it.
And I have many
nrpe[85804]: Host 192.168.1.79 is not allowed to talk to us!
nrpe[85985]: Host 192.168.1.77 is not allowed to talk to us!
What could be the conflict?
I am using nrpe daemon on computers.
It is somehow connected with kaspersky antivirus server. I have two server with KAV installed on it.
And I have many
nrpe[85804]: Host 192.168.1.79 is not allowed to talk to us!
nrpe[85985]: Host 192.168.1.77 is not allowed to talk to us!
What could be the conflict?
-
npolovenko
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: nrpe error
Welcome back, @netaccs. Here's what you need to do:
Then:You need to add the allowed ip's to /etc/xinetd.d/nrpe.cfg
In that config file separate IP addresses with spaces, no commas.
Code: Select all
service xinetd restartAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.