On 2015-05-03 6:55 pm, Tim Dunphy wrote:
It's listening on both IPv6 and IPv4. Specifically, why is that a
problem?
The central problem seems to be that the monitoring host can't hit nrpe
on
port 5666 UDP.
[root@monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H
puppet.mydomain.com
On Sun, May 03, 2015 at 08:25:45PM -0400, Tim Dunphy wrote:
Rather than a yum install. If I install the nrpe package from yum I don't
find a check_nrpe script on the system for some reason!
That's because the 'check_nrpe' command isn't in the nrpe package.
It's in the nagios-plugins-nrpe
On Sun, May 03, 2015 at 08:25:45PM -0400, Tim Dunphy wrote:
Rather than a yum install. If I install the nrpe package from yum I don't
find a check_nrpe script on the system for some reason!
That's because the 'check_nrpe' command isn't in the nrpe package.
It's in the nagios-plugins-nrpe
On 05/03/2015 03:55 PM, Tim Dunphy wrote:
You mention that it's listening on both tcp v4 and v6. But I only see v6 in
that output. How are you determining that
On Linux, IPv4 is mapped inside the IPv6 space. An application that
listens on an address-less v6 port is listening on both IPv4 and
hey all,
I tried disabling tcp v6 on a C7 box this way:
[root@puppet:~] #cat /etc/sysctl.conf
# System default settings live in /usr/lib/sysctl.d/00-system.conf.
# To override those settings, enter new settings here, or in an
/etc/sysctl.d/name.conf file
#
# For more information, see
On 05/03/2015 02:18 PM, Tim Dunphy wrote:
Yet, xinetd/nrpe still seems to be listeing on TCP v6!!
It's listening on both IPv6 and IPv4. Specifically, why is that a problem?
What am I doing wrong? I need to be able to disable tcpv6 completely!
You could add ipv6.disable=1 to your kernel
is it working on localhost or not???!!! it could be selinux problem also,
if context is not correct.
--
Eero
2015-05-04 1:55 GMT+03:00 Tim Dunphy bluethu...@gmail.com:
It's listening on both IPv6 and IPv4. Specifically, why is that a
problem?
The central problem seems to be that the
On Sun, May 3, 2015 at 4:18 PM Tim Dunphy bluethu...@gmail.com wrote:
What am I doing wrong? I need to be able to disable tcpv6 completely!
Ultimately you can disable ipv6 completely by disabling the ipv6 module. On
this FAQ below also includes a reason why you may not want to do that.
It's listening on both IPv6 and IPv4. Specifically, why is that a problem?
The central problem seems to be that the monitoring host can't hit nrpe on
port 5666 UDP.
[root@monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H
puppet.mydomain.com
CHECK_NRPE: Socket timeout after 10 seconds.
It
On Sun, May 03, 2015 at 07:23:19PM -0400, Tim Dunphy wrote:
[root@puppet:~] #telnet localhost 5666
This is using TCP
[root@monitor1:~] #nmap -p 5666 puppet.mydomain.com
...
5666/tcp filtered nrpe
This is using TCP
Back on the puppet host I verify that the port is open for UDP:
So why are
is it working on localhost or not???!!! it could be selinux problem also,
if context is not correct.
It's working on localhost:
[root@puppet:~] #telnet localhost 5666
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
I notice if I stop the firewall on the puppet host
Tim,
where did you installed this nrpe package? is selinux running enforcing
mode (getenforce command), try disabling with setenforce 0. why you are
running it under xinetd as usual way is to run it as nrped daemon.
test against with check_nrpe, not using telnet.
--
Eero
2015-05-04 2:27
Eero,
where did you installed this nrpe package? is selinux running enforcing
mode (getenforce command), try disabling with setenforce 0. why you are
running it under xinetd as usual way is to run it as nrped daemon.
For NRPE I usually do a source install with these flags:
./configure
make
13 matches
Mail list logo
