Hello,
If check_nrpe times out after whatever the period is defined, I want to show a message different that the usual socket timeout message.
The socket timeout message usually could be ignored easily which I'm trying to avoid.
Has anyone done this before in a reliable way?
Thanks
check_nrpe socket timeout
-
- Posts: 5
- Joined: Sun May 15, 2022 6:43 am
Re: check_nrpe socket timeout
Isn't your 12.12.12.12 address routed to internet? It loosk to belong to AT&T or something?
Unless you actually own the 12.x.x.x subnet you should probably try one of the private networks for your hosts. Let me try to install the NRPE agent on another server in the same "enclave" as the nagios server. If it works, this will definitely reveal itself omegle shagle voojio be a router firewall issue.
Unless you actually own the 12.x.x.x subnet you should probably try one of the private networks for your hosts. Let me try to install the NRPE agent on another server in the same "enclave" as the nagios server. If it works, this will definitely reveal itself omegle shagle voojio be a router firewall issue.
Last edited by DevinPomsilina on Thu Sep 29, 2022 11:40 pm, edited 1 time in total.
-
- Posts: 11
- Joined: Wed Feb 16, 2022 2:47 am
Re: check_nrpe socket timeout
I see where you are going with this. Let me try to install the NRPE agent on another server in the same "enclave" as the nagios server. If it works, this will definitely reveal itself be a router firewall issue.
Is iptables running? if so, you might omegle.2yu.co need to open port 5666 (assuming your LAN is trusted):
iptables -A IN_public_allow -p udp -s="0.0.0.0/0" --dport 5666 omeglz echat -j ACCEPT
Is iptables running? if so, you might omegle.2yu.co need to open port 5666 (assuming your LAN is trusted):
iptables -A IN_public_allow -p udp -s="0.0.0.0/0" --dport 5666 omeglz echat -j ACCEPT
Last edited by PaulRajeshMEzra45 on Tue Sep 13, 2022 7:06 am, edited 1 time in total.
Re: check_nrpe socket timeout
I'm looking for a alternative to throw a message instead of "socket_timeout" message which doesn't make sense to a layman. It is presumed that there is a problem at the other end the test isn't working.
Thanks
Thanks
Re: check_nrpe socket timeout
You could write a wrapper script that runs check_nrpe and prints another message when it times out, or you can modify the source and recompile it.
You can also adjust the return value...
-u, --unknown-timeout Make connection problems return UNKNOWN instead of CRITICAL
-t, --timeout=INTERVAL:STATE
INTERVAL Number of seconds before connection times out (default=10)
STATE Check state to exit with in the event of a timeout (default=CRITICAL)
Timeout STATE must be a valid state name (case-insensitive) or integer:
(OK, WARNING, CRITICAL, UNKNOWN) or integer (0-3)
You can also adjust the return value...
-u, --unknown-timeout Make connection problems return UNKNOWN instead of CRITICAL
-t, --timeout=INTERVAL:STATE
INTERVAL Number of seconds before connection times out (default=10)
STATE Check state to exit with in the event of a timeout (default=CRITICAL)
Timeout STATE must be a valid state name (case-insensitive) or integer:
(OK, WARNING, CRITICAL, UNKNOWN) or integer (0-3)
Re: check_nrpe socket timeout
Thank you!
Yes, the wrapper idea was the one I ended up doing.
Yes, the wrapper idea was the one I ended up doing.