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.
[root@localhost nagios-plugins-timeout_state]# ./tools/setup
which: no gnumake in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/root/root/bin)
Found GNU Make at /usr/bin/gmake ... good.
./tools/setup: line 30: aclocal: command not found
./tools/setup: line 32: autoheader: command not found
./tools/setup: line 33: automake: command not found
./tools/setup: line 34: autoconf: command not found
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
I installed the automake and so I was able to run the ./tools/setup and then the ./configure
But I still got the same output when running check_http (timeout interval must be a positive integer).
Also, I got some error messages at the end of the compiling:
Rerun the configure, make, and make install steps afterwards.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
My bad. My last post said "make all" instead of "make install". And I edited it, so no, you are not going crazy. At least not *this* time
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
I didn't see a "make install" there, which would leave the plugins built but still in the install directory and the original check_http still in place. So you have two choices.
1) move back into the directory where you were building the plugins and run make install. Then test from your standard plugins path.
2) test the new binaries from the path where you currently have them (we'll use /tmp) with something like:
cd /tmp/nagios-plugins-timeout_state/plugins
check_http -V ( to check the current version, should be 2.0.3-dirty or something similar)
I would suggest option 1, since you will in all likely-hood want to switch to the newer plugins anyway.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Finally, now it works.
Just to make things clear: using the wrapped 2.0.3 version, I had a specific "CRITICAL - Socket timeout" string, so this was the only timeout message meant to return UNKNOWN state instead of CRITICAL.
Now, with the git's 2.0.1, all timeout-related messages will return UNKNOWN state instead of CRITICAL, right?
Even though the plugins report version 2.0.1, they are indeed a different branch (and have had commits post 2.0.1 merged into them). These changes will be pulled into the nagios-plugins master branch at some point.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.