Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
Directory
nkadel
bynkadel, April 8, 2015
It has no documenation and no explanations of how or what arguments need to be passed to it. Quite useless unless you can read Perl code as documentation, and if you can do that, you can write a better tool from scratch.
bynkadel, February 2, 2015
This is redundant: it's built into the nagios-plugins published 'check_mysql' package, which is tested and maintained. Use 'check_mysql -S' and review the options desired.
bynkadel, February 2, 2015
See above review.
This script is now redundant: it's built into the nagios-plugins published 'check_mysql' package, which is tested and maintained. Use 'check_mysql -S' and review the options desired.
This script is now redundant: it's built into the nagios-plugins published 'check_mysql' package, which is tested and maintained. Use 'check_mysql -S' and review the options desired.
bynkadel, February 2, 2015
This is redundant: it's built into the nagios-plugins published 'check_mysql' package, which is tested and maintained. Use 'check_mysql -S' and review the options desired.
bynkadel, February 2, 2015
This is redundant: it's built into the nagios-plugins published 'check_mysql' package, which is tested and maintained. Use 'check_mysql -S' and review the options desired.
bynkadel, February 2, 2015
The slave checks are now built into the supported 'check_mysql' plugin.
bynkadel, February 2, 2015
This is redundant: it's built into the nagios-plugins published 'check_mysql' package, which is tested and maintained. Use 'check_mysql -S' and review the options desired.
bynkadel, March 24, 2013
2 of 8 people found this review helpful
This is one of the basic packages I use in every large environment, for Nagios or Icinga monitoring and easy admin checking. Three are 3 small bugs:
* NRPE should have its own user, not share the "nagios" user. That causes confusion with ownership of configuration files and the "nagios" user itself.
* NRPE should have its config files in /etc/nrpe, not /etc/nagios. Again, this causes confusion with who manages the files in /etc/nagios and makes source control and package management much more awkward.
* The default location of "/usr/lib/nagios/plugins" should be set based on architecture. It's /usr/lib64/nagios/plugins on most x86_64 systems.
* NRPE should have its own user, not share the "nagios" user. That causes confusion with ownership of configuration files and the "nagios" user itself.
* NRPE should have its config files in /etc/nrpe, not /etc/nagios. Again, this causes confusion with who manages the files in /etc/nagios and makes source control and package management much more awkward.
* The default location of "/usr/lib/nagios/plugins" should be set based on architecture. It's /usr/lib64/nagios/plugins on most x86_64 systems.
bynkadel, December 30, 2012
The structure of available options is good. The security is *BAD*. MySQL commands for replication should never, never, never be run from unprivileged command line arguments, because access to the Nagios configurations or the output of "ps auxwww" will reveal the name and password of the user with replication privileges.
This commandn would benefit strongly from access to a default configuration file, even a $HOME/.my.cnf for the Nagios user, that would protect access to the replication user account.
This commandn would benefit strongly from access to a default configuration file, even a $HOME/.my.cnf for the Nagios user, that would protect access to the replication user account.