ID: 10167
Title: Fix excessive memory consumption on systems using apache 2.2 (e.g. RedHat 6)
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.7.0i1
The site apache was consuming a lot more memory than intended. The memory usage
seemed to grow with every request to the apache 2.2 process. This was caused by
a bad mod_wsgi configuration. This config made each apache process create multiple
python interpreters within a single process, one for each GUI page (views.py, ...).
Apache 2.4 based systems were not affected by this.
ID: 10078
Title: check_traceroute: Support for IPv6
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The active check for traceroute now supports IPv6. In the service parameters you can now specify the IP address familiy.
For link-local addresses (IP addresses starting with 'fe80') you may need to specify a zone/interface index or name by appending it with a % to the IP address (e.g. fe80::aebc:32ff:fe95:8ac1%eth0)
Otherwise this error might occur: 'connect: Invalid argument'
ID: 10077
Title: Validation of IPv6 address input fields extended by zone/interface index and name
Component: WATO
Level: 1
Class: New feature
Version: 1.7.0i1
The validation process for the input fields of IPv6 addresses will now allow the extension of the zone/interface index and name.
For IPv6 addresses you can add the zone index or interface name/index by appending a % to the IP address followed by the value.
A zone/interface index could be 1, 2, 3 etc. An interface name eth0, wlp5s0, etc.
Example: fe80::aebc:32ff:fe95:8ac1%3 or fe80::aebc:32ff:fe95:8ac1%eth1
For link-local addresses you may need to define the interface when calling tools like ping or tracroute.
Otherwise this error might occour: 'connect: Invalid argument'
ID: 10166
Title: Fix cmcdump issue during config activation
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
During config activation a KeyError with reference to a shadow host name
could be raises.
ID: 10165
Title: Factory settings: Docker container host check command is set now
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
Instead of always assuming the docker containers to be up, the docker containers
now base their host state on the service state of the "Docker container status"
service.
This is configured by the factory settings using the ruleset "Host Check Command".
The factory settings only apply to new created sites. In case you want this in
existing sites, you need to create a rule in this ruleset manually.
ID: 10091
Title: Agent AWS: Let EC2 services become stale if the instance was terminated
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The EC2 piggybacked hostname contains the value of the field 'PrivateIpAddress'.
If an EC2 instance terminates then this field is missing. In this case we skip
this instance and the services of the EC2 instance become stale. Moreover the
Check_MK service reports 'Got not information from host'.
ID: 10096
Title: mssql.vbs: Do not ignore empty blocked sessions which causes vanished services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the mssql.vbs ignored empty blocked session (==0).
This causes vanished services on the Checkmk server.
Now the blocked sessions are always delievered. You have to
deploy the mssql.vbs.