| Age | Commit message (Collapse) | Author |
|---|
|
|
|
anymore by the nagios module, and our config template has drifted.
Fixes: #7527
Change-Id: I56c3492056fcb95c499cf78b893249adcf0ae67f
|
|
- Resolves: #7514
|
|
Make the server-status information unavailable by putting the vhost on a
port that isn't configured as available to the tor hidden-service.
Change-Id: Idd3bfefb5b7fc26fb0a8cf48cdf6afc68a4192bb
|
|
installed
Change-Id: I272b30fd79e89ddf968c0a6e453d53a1f0540397
|
|
Change-Id: If9e17de438a4a6ac8e68877bfe0c5d13d45386ee
|
|
Change-Id: I5c7bcfe2e6dca2276c03bd4985b0fb1e4852a9df
|
|
Change-Id: I0f9397593bc4f00b64b626a159be09ab5ef694d6
|
|
In order to assure tapicero is still working, we need to monitor
/var/log/syslog for the last tapicero log msg, which should not be older
than the last check_mk_agent run (every 2 mins atm).
|
|
leap_platform was modified so the nagios.internal_domains contain the
domain name (with the tld replaced by an "i" for internal), see
https://leap.se/code/issues/6477#note-11.
in order to achieve this the easy way, each host got added a
domain_internal_suffix value, which can be iterated over to get all
nagios.internal_domains.
Because we use `create_resources ( site_nagios::add_host_services,
$nagios_hosts )` in site_nagios::server to deploy the services, the
site_nagios::add_host_services define needs to have a
domain_internal_suffix parameter added.
Change-Id: I6b83b3f291a1a611b5b92d5ba3ed82597a42bba7
|
|
contact email (Bug #6466)
Change-Id: Ib86ae771e0ac3b6f329a517a8a31c9ec54d33a05
|
|
Change-Id: Idf550ed004bcb42d6e19ac0a2c5286f52a390935
|
|
nagios::defaults will include nagios::defaults::hostgroups which
add "all" and "centos_servers" hostgroups which we don't want.
Change-Id: If42faa11c167fb7305ebbb21dc358a8813afaa25
|
|
Change-Id: I6508ce0d06b37a1c5601a0e981a59f7fda47f76a
|
|
a wrong hostname on single node setup (Bug #5998)"
before, the ssh module added this check, resulting in a wrong
hostname and the port was always '22'.
manage_nagios parameter is boolean, so we use false instead of 'no'
manually add check_ssh to nagios (#5998)
|
|
|
|
|
|
|
|
|
|
false-positive warnings
|
|
(Feature #2981), wip
also, use the configured ssh port for every node
|
|
because now, check_mk will add the hosts
|
|
|
|
|
|
|
|
Conflicts:
provider_base/services/monitor.json
puppet/modules/site_nagios/manifests/server.pp
|
|
nagios and webapp node (#5096)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
nagios and webapp node (#5096)
|
|
|
|
|
|
|
|
|
|
Change-Id: Icebf9d8849b4440f4f6dbc00a1a8ac0873b62f6a
|
|
Puppet 2.7.19 introduced a change that don't allow resource titles to be
something else that a string. from the puppet 2.7.19 changelog:
Don’t allow resource titles which aren’t strings
It was possible to create resources whose titles weren't strings, by
using a variable containing a hash, or the result of a function which
doesn't return a string. This can cause problems resolving relationships
when the stringified version of the title differs between master and
agent.
Now we will only accept primitives, and will stringify them. That is:
string, symbol, number, boolean. Arrays or nested arrays will still be
flattened and used to create multiple resources. Any other value (for
instance: a hash) will cause a parse error.
currently, it's much easier to iterate over a hash in puppet than over
an array, cause every resource you call iterating over an array would
need a unique name, and you don't have this in arrays.
|
|
shorewall is setup before the service is setup. This is necessary due to the strict initial firewall that stops various service setup operations from happening, but is relaxed once shorewall is setup properly (#3782)
Change-Id: Ia9640c4118aa0053cdb99e7bc11860fed5527501
|
|
more than once in different locations, depending on what services are configured on a node (#3612)
Change-Id: Iff064d3d67baa132fb5198fea741522ab4e71770
|
|
Change-Id: Ia4e36e9cb2b37172a148c209c5c07b9eca59d89e
|
|
|
|
|
|
|
|
|
|
|
