check_yum
check_yum copied to clipboard
calestyo
check_yum is now maintained again by its original maintainer at https://github.com/HariSekhon/Nagios-Plugins/
YUM output signature is larger than current known format, please make sure you have upgraded to the latest version of this plugin. If the problem persists, please contact the author...
Hi @calestyo Instead of maintaining multiple divergent copies of this check_yum.py code, could you please just send any updates you want to [the original Advanced Nagios Plugins Collection repo](https://github.com/harisekhon/nagios-plugins) via...
In our case, there were lots of lines like `--> libuuid-2.23.2-22.el7_1.i686 from rhel-7-server-rpms excluded (updateinfo)` in the output of `yum --security check-update` which triggered the test for `len(output) > number_total_updates...
The same issue like https://github.com/calestyo/check_yum/issues/25: The check fails with exit 2 with > YUM output signature is larger than current known format, please make sure you have upgraded to the...
count lines with diagnostic output and deduct from total rewrote matching to use array of regexps with named parameters to simplify code.
This change fixes the error "YUM output signature is larger than current known format" when running CentOS/RHEL/OEL 7. Thanks for this awesome plugin!
On el7, yum will list all the packages available for update _after_ the summary line, as well as in the transaction. At first I tried just checking for `* 2`...
In RHEL/CentOS 7, the output from the command `yum --security check-update` seems to list all the packages that has been excluded from the check. This list is way too long...
``` I think it would be good to re-implement check_yum either in C or C++... or possibly in Perl. C/C++ have the typical advantages of real programming languages... (performance, etc.)....
I think critical is the wrong severity, even for security updates. We have a nightly cronjob on our servers that runs yumcron. Critical should only be used for problems that...
