ID: 10168
Title: Disable CLUSTER sections in sample logwatch.cfg
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The uncommented CLUSTER sections in the logwatch.cfg could lead to unexpected
results when starting to configure logwatch using the sample configuration.
We have now simply commented out these sections.
ID: 10169
Title: mk_logwatch: Fix "random" missing logfile when monitoring through xinetd
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
When executing the agent through xinetd, the environment is initialized in
a different way than when executing the agent manually from the command line.
This can lead to different locale settings making mk_logwatch use a different
default encoding on linux systems.
Instead of the widely used UTF-8 encoding it assumed ANSI_X3.4-1968 encoding.
With this encoding it was not possible to process UTF-8 encoded log files. The
log file processing was terminated while reading the file, making the GUI show
it as UNKNOWN service.
In the moment we see a ANSI_X3.4-1968 default encoding in mk_logwatch, we
replace this with UTF-8 now.
ID: 10099
Title: mssql_blocked_sessions: Fixed vanished services if no blocked sessions are sent from agent plugin
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 or 'No blocked sessions' are delievered.
You have to deploy the mssql.vbs in order to make this work.
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.