Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This reverts commit 4403c402cba0315c2cb9ebe40639a5fe312d643e.
|
|
|
|
Signed-off-by: Sven Nierlein <sven@nierlein.de>
|
|
The "-6" optarg now prepends the server_address with "udp6:" for the
snmpget external command as per the net-snmp syntax at:
http://www.net-snmp.org/wiki/index.php/FAQ:Applications_28
Thanks to DrydenK (Roberto Greiner) for the heads up.
|
|
|
|
This addition is based on a patch contributed by Christopher Schultz.
Closes #1099.
Closes #1171.
|
|
|
|
Update the THANKS.in file with the new Git commit authors.
|
|
Conflicts:
NEWS
THANKS.in
|
|
|
|
|
|
|
|
|
|
---
Closes #1218
Closes #1281
|
|
|
|
|
|
This patch allows checking if MySQL server is running without providing valid
username and password. Similar to check_ssh plugin it returns MySQL server
version string and protocol number.
Example:
check_mysql -n -H aaa.bbb.ccc.ddd
MySQL OK - Version: 5.0.51a-24+lenny5 (protocol 10)
This is useful for monitoring servers where one does not have administrator
privileges or does not want to grant any privileges for the monitoring station.
To enable this functionality new option --ignore-auth (-n) is added to
check_mysql plugin.
Thanks to Julius Kriukas
Closes #1020
Closes #1178
|
|
sshutils prints the expiry time of certificates in US format
this patch uses the strftime %c, I don't know how portable that is
Thanks to Neil Prockter.
Closes #1188
Closes #1161
Closes #977
Closes #976
Closes #975
Closes #840
Closes #382
|
|
The perfdata output violates the current Nagios Plugin Development Guidelines
(http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN202 :
"space separated list of label/value pairs").
Thus the Addon PNP did not read the perdata correctly.
The patch replaces the commas with spaces in the perfdata output.
Many thanks to Patric Wust.
---
Closes #1169 and #721.
|
|
check_oracle in the 1.4.15 release doesn't correctly parse the output gotten
from at least Oracle 11 (with german locales). I guess it's probably more.
Also it completely needlessly uses sed where basic bash string parsing actually
does more than suffice (and does not run into possible problems with locales
like sed ;)).
--
Just turning attached patch of github issue #1015 into a push request.
(Closes #1015 and #1191)
|
|
|
|
Update the THANKS.in file with the new Git commit authors.
|
|
Add the new Git commit authors to the THANKS.in file.
|
|
|
|
|
|
When a timeout value is specified with the -t option, dig will sometimes
timeout before the timer is actually reached.
The problem occurs because the check_dig plugin does not pass the specified
timeout value to dig, leaving dig to timeout with it's default value which
seems to be around 10-15seconds.
To reproduce:
time ./check_dig -H 127.0.0.2 -l www.google.com -t 30
It will not run for 30secs, which is the expected behaviour.
The following will work, because the timeout is less than the default dig
timeout, so the plugin cancels the dig command:
time ./check_dig -H 127.0.0.2 -l www.google.com -t 2
This fix passes the timeout value to dig, and sets the number of retries which tends to vary from system to system by default.
Closes #1168
|
|
Adding nullmailer support to check_mailq submitted by Luca Corti
Closes: #740
Closes: #1189
|
|
|
|
by Geoff Oakham <goakham at oanda.com>
Patch of check_ping that allows it to gracefully handle when ping outputs
to stderr "Warning: time of day goes back (-XXXXus), taking countermeasures."
Closes: #809 and #1195
|
|
Add all new Git commit authors to the THANKS.in file.
|
|
Thanks to Emmanuel Dreyfus for providing the patch.
|
|
- cleanup whitespace
- added test cases
- print time_ssl only if ssl is in use
- updated news and thanks file
|
|
|
|
Thanks to Roman Fiedler for reporting the issue and providing a fix
|
|
Thanks to Vaclav Ovsik for reporting the issue and providing a fix
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add --perf-oids option for check_snmp to retain optional 1.4.14 compatibility
|
|
The (current and past) team members are listed in the AUTHORS file.
|
|
|
|
|
|
Don't return a WARNING state if the number of lost packets is greater
than zero but below the specified warning threshold. This happened
because the check_ping plugin used the exit status of the ping(1)
utility. (#3535140 - Tobias Brox)
|
|
(Debian #654259 - Charles-Henri Larose)
|
|
RFC 2131 (2.) says: "DHCP clarifies the interpretation of the 'siaddr'
field as the address of the server to use in the next step of the
client's bootstrap process." So, we shouldn't interpret this field as
the DHCP server's own address. (#3503921 - Jason Ellison)
|
|
The ping6(1) implementation provided by Debian's iputils-ping package
may produce output such as the following:
| 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2009ms
There's a corresponding pattern in check_ping.c:458:
| "%*d packets transmitted, %*d received, +%*d errors, %d%% packet loss"
Without this fix, the pattern in check_ping.c:456 matched first (as
sscanf(3) interprets "+3" as a match for "%d"):
| "%*d packets transmitted, %*d received, %d%% loss, time"
(#1894850 - Debian bug report #514588 - Matej Vela)
|