| Age | Commit message (Collapse) | Author |
|---|
|
|
|
add_pnp4nagios
Conflicts:
README.pnp4nagios
manifests/defaults/pnp4nagios.pp
manifests/pnp4nagios.pp
manifests/pnp4nagios/popup.pp
|
|
|
|
|
|
Conflicts:
manifests/apache.pp
manifests/base.pp
manifests/defaults/templates.pp
manifests/defaults/vars.pp
manifests/init.pp
manifests/irc_bot.pp
manifests/nsca/client.pp
manifests/nsca/server.pp
manifests/service.pp
manifests/service/mysql.pp
templates/irc_bot/nsa.cfg.erb
|
|
|
|
|
|
|
|
Add the port arg to check_http_url_regex. Default 80.
|
|
|
|
|
|
merge conflict due to immerda's branch not being up-to-date on the bot
|
|
|
|
|
|
|
|
This reverts commit fb75fcec220f9e2943d2e7af292ff884fd237f6d.
Reverted due to LeLutin's comments in #3310 and the fix implemented in #3298 in
preparation of merging those
|
|
|
|
|
|
On Debian, the nagios-plugins packages install
/etc/nagios-plugins/config/mail.cfg which contains the check_smtp/check_imap
commands, and these commands cannot be duplicated. The addition of these
commands in this module in c9c4f5bb895e98e31d84c751a7fcbdae9bf57008 and
1c4de48baf4ffcf5f39894a101a3c59479959b47 now cause Debian nagios servers to
fail to start with this message:
Warning: Duplicate definition found for command 'check_smtp' (config file '/etc/starting on line 9)
The versions of these check commands that were added in the above commits are
actually more full-featured than the ones that Debian ships, most notably
because they allow for the port to be passed as an option. In most cases their
names are the same, although the imap and pop ssl commands are different. This
leads to a somewhat unfortunate situation where the module defines duplicated
commands, which are better, but in some cases are differently named than the
ones shipped in the package. Ideally, those names would converge, and the
debian package commands would add the port options by default, and we'd case
out debian/ubuntu to not ship these in this module.
However, due to the added benefit of the options provided in the commands
shipped in this module, along with the benefits that come with the module
being able to automatically configure these, I've elected to simply remove
the debian package file (which is a config file, so it will be honored
by the packaging system).
|
|
Conflicts:
manifests/defaults/commands.pp
|
|
We have a serious problem with the concept that we had up to now if
you start adding more than one nagios server. This is an attempt to
fix it, with certain drawbacks, such as that you have to list all
the nagios plugins in the nagios modules. This will be subject of
further discussion.
|
|
|
|
|
|
|
|
|
|
|
|
the command specifier
|
|
|
|
|
|
|
|
|
|
|
|
|
|
check_dns had some problems with down nameservers. This one properly
checks the right nameserver.
|
|
|
|
|
|
. add an additional nagios::defaults::plugins class that is included in the nagios::defaults, this can be used to install other nagios plugins that aren't distributed in the nagios-plugins package
. use the nagios::defaults::plugins to setup the check_mysql_health plugin
. add a check_mysql_health command to defaults/commands.pp in the section for commands for services defined by other modules
. change the nagios::service::mysql to use the more advanced check_mysql_health plugin, instead of the basic check_mysql plugin
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
number of the check_commands that were being defined by this module,
this caused duplicate definition issues, so to solve this we don't define
the subset of commands on debian/ubuntu systems that are handled by the
package, but let other operatingsystems define them (as they were before)
|
|
only location where specific classification is done, and this anomaly
prohibits you from setting the variable in site.pp
|
