Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Hello, I have a command using check_tcp it returns exit code 2 but the status.dat file shows a current_state=1. Anyone know where it could come from, I expect it to be 2?
What is status_update_interval set to in /usr/local/nagios/etc/nagios.cfg? Are there any errrors or warnings when you run /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg or anything odd logged in /var/log/messages? Make sure it is running with ps aux| grep nagios.cfg and service nagios status.
Please provide the output of the commands as well as a copy of nagios.cfg if the above doesn't help resolve things.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
My status_update_interval is set to 10, just one warning (over more than 1000 hosts) about a host, that does not have services associated with it, but its normal in our case. Nothing fancy in /var/log/messages neither, and service is running properly (monitoring 1000s hosts, working properly) on host with check_tcp has this mismatch with current_state.
@naitsab, Would you be able to upload the source code for the check_tcp plugin? Also, does the plugin state update in the web interface? Is it red-critical, or is it yellow? Please send us a screenshot from the Web UI. Also, please force the service check from the web interface and then check the status.dat file one more time to see if the last_update_time has been changed.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Hey, I cannot give you the source code. It was installed from an rpm, with the version: 1.4.16-10.el6.x86_64.
The UI is red critical. I am not sure what you mean by 'Force' in UI, I guess its a re-schedule manually right? if so state does not change.
A host object has 3 potential states: UP (0) and DOWN (1) and UNREACHABLE (2). Per the plugin's output and the Nagios Core conventions, one would indeed think the host's status should be UNREACHABLE instead of DOWN in this case.
Being that Core 3.5.1 is very old (released in 2013), I think its unlikely that a similar patch will be deployed in a Core 3 release. For old RPM releases though, that's out of the hands of anyone on this forum (depending on your OS and package provider).