G'day Guys,
Aside from "Service and Host Freshness Checking" is there a way to ensure send_nrdp.sh commands successfully send results over WAN links with potentially high latency?
I hope I've been clear in my question.
Regards,
John Hobbins
Australia
Distributed Environment: NRDP & Network Latency
Re: Distributed Environment: NRDP & Network Latency
Yes, the send_nrdp.sh script will return with an error message and error code if it can't send something to the server.
Re: Distributed Environment: NRDP & Network Latency
Thanks mate.
Is it possible to set a retry or timeout value?
Is it possible to set a retry or timeout value?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Distributed Environment: NRDP & Network Latency
You can call it with the following flag
And it will store unsuccessful attempts in /path/to/temp/dir and retry sending them the next time the script is called
Otherwise you would need to modify the script adding
after wget on line 90
Code: Select all
-D /path/to/temp/dirOtherwise you would need to modify the script adding
Code: Select all
--timeout=seconds
Re: Distributed Environment: NRDP & Network Latency
Thanks mate.
Is wget preferable over curl?
If so, do I simply swap the order in the shell script?
Is wget preferable over curl?
If so, do I simply swap the order in the shell script?
Re: Distributed Environment: NRDP & Network Latency
Not really much of a difference either way. Some base installs of Linux don't ship with wget anymore, but most ship with curl.