| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
amended (lelutin): took out some trailing whitespaces and a commented
out (useless) line
|
|
|
|
|
|
|
|
|
|
amended (lelutin): removed trailing spaces and commented out code.
|
|
The default nsca.cfg is currently using the "non-normal" port for nsca.
Let's import a freshly installed nsca.cfg file with default values.
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
|
|
Without this link, puppet sometimes attempts to start the service before
the package is installed, wich triggers an error.
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
|
|
The current code tries to get the content of those two files in a bunch
of places and defines a fallback to a generic file in the module's
files/configs directory.
The problem is that there is no such generic config file present.
Link to Debian's config files as a generic version of those
configuration files.
This bug was found by taggart.
|
|
|
|
|
|
This reverts commit fb75fcec220f9e2943d2e7af292ff884fd237f6d.
Reverted due to LeLutin's comments in #3310 and the fix implemented in #3298 in
preparation of merging those
|
|
|
|
Conflicts:
manifests/irc_bot.pp
Had to merge in the use_notices change that we had in our branch
|
|
|
|
This gives us the possibility of using the nagios::irc_bot::disable
class without having any config variable set. When using
nagios::irc_bot, we still get yelled at when we didn't define the
appropriate variables.
While we're moving the code around, change the group applied on the
different files from 'root' to '0' for better portability.
|
|
All classes serving the same purpose as this one are called 'disable',
so let's follow this standard.
|
|
A misconception on my part made the dependencies "not-quite-right" (as
in: the script doesn't really depend on nagios, as we would expect). This
gives the IRC bot the save "level" as nagios itself. However, we'd like
for nagios to be started before we start the IRC bot.
|
|
It may sometimes happen that the bot dies or gets killed and the socket
file is not cleaned up. When using the init script with 'start', as
puppet does, the socket file blocks the bot from starting.
|
|
Since the service "disable" bug was fixed in the debian service provider
[1] in the puppet 2.6.2-5 package in squeeze, let's switch from the
manual calls to the "enable" feature.
[1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573551
Also add a requirement between service[nagios-nsa] and
file[/etc/init.d/nagios-nsa]. This was ensured in Debian with the exec
that we're now replacing but didn't find its way through the
centosification.
|
|
For when you need to ensure that the bot doesn't start on a server.
|
|
When we modify the config file, we'd like for the service to restart in
order for it to use the new configuration.
|
|
To give a little more info/meaning on what the number $SERVICEATTEMPT$ is,
change the current notification from "... n.$SERVICEATTEMPT$" to "...
$SERVICEATTEMPT$/$MAXSERVICEATTEMPTS$".
|
|
|
|
|
|
|
|
This plugin is already defined at nagios-plugins, so removing it
for the same reason as e7f85f647e6f641bd85fbdfdb26982350f782370.
This commit has more readable implementation than the previous.
|
|
This plugin is already defined at nagios-plugins, so removing it
for the same reason as e7f85f647e6f641bd85fbdfdb26982350f782370.
|
|
The file commands.cfg was introduced at 61aab91919b2e6d9cb5d7afe3befe40de67ac132.
This change make sure the file exists so nagios doesn't stop running.
|
|
|
|
|
|
|
|
which can be turned on by the puppet variable $nagios_nsa_usenotices
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
