Re: No output on stdout) stderr: connection refused
Posted: Wed Jun 21, 2017 4:21 pm
Commands typically go in to the commands.cfg file.
Support for Nagios products and services
https://support.nagios.com/forum/
Code: Select all
define host{
use linux-box ; Inherit default values from a template
host_name huey ; The name or IP or remote server
alias RHEL 7.3 ; A longer name for the server
address 192.168.1.42 ; IP address of the remote server
check_ping -H 192.168.1.149 -w 10,2% -c 20,5% -t 5 ; ping to remote hosts
}
Code: Select all
# SAMPLE HOST CHECK COMMANDS
#
################################################################################
# This command checks to see if a host is "alive" by pinging it
# The check must result in a 100% packet loss or 5 second (5000ms) round trip
# average time to produce a critical error.
# Note: Five ICMP echo packets are sent (determined by the '-p 5' argument)
# 'check-host-alive' command definition
define command{
command_name check-host-alive
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 5
}
This isn't the best strategy, IMO. If you are interested in XI, start the 60-day trial and show that it works from there. Editing config files in XI is not a thing. You are wasting a lot of time with Core if you plan to move to XI. If you need more than 60-days for a proof of concept, describe your requirements to Sales, and they may grant an extension.donnyforbes wrote:We do plan on getting XI, however we need to get it working and showing that it will work for our company and its needs that is why I am using the core version now.