ID: 7880
Title: mrpe: Create mrpe config also for AIX systems when configured
Component: agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Despite the mrpe being included in the AIX agent, no mrpe.cfg would
be included by the agent bakery. This has been fixed.
ID: 7424
Title: mk_postgres: add missing database parameter
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The mk_postgres plugin was missing a database parameter in
the queries for the checks postgres_bloat and postgres_stats.
Therefore, the name of the database user was used as a
fallback. As a result no output for postgres_stats and
postgres_bloat was returned if a database with the username
did not exist. If a database with the username exists
the checks give the correct output.
To resolve the issue the fixed version of the mk_postgres
plugin has to be deployed on the affected hosts.
ID: 7423
Title: mk_postgres: fix syntax error
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Version 1.5.0p17 and 1.5.0p18 of the mk_postgres plugin gave a
syntax error when parsing databases. This results in empty
output between [databases_start] and [databases_end] in the
plugin output. As a consequence the checks postgres_stats,
postgres_bloat, postgres_connections, postgres_locks and
postgres_query_duration become stale.
To resolve the error the fixed version of mk_postgres has to be
deployed to the affected hosts.
ID: 7426
Title: mk_postgres: fix the version detection when using an MK_CONFFILE
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Since version 1.5.0p17 the version detection fails if an MK_CONFFILE
is used and the psql binary cannot be found in the PATH. To resolve
the issue the fixed version of the mk_postgres plugin has to be
deployed on the affected hosts.
ID: 7819
Title: Fix "HTTP header authentication"
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The HTTP header authentication can be enabled in the Global Settings using the
option "Authenticate users by incoming HTTP requests". In case you do not use
this authentication method, you are not affected by this issue.
It is mostly used in some reverse proxy setups where the Checkmk apache is
located behind an authentication service. The authentication service only tells
Checkmk the authenticated username and the user interfaces allows the user to
enter without further authentication.
The user name is handed over as HTTP header with each HTTP request to the site
apache and forwarded to the GUI.
With Checkmk 1.5 or older in connection with apache 2.4 and Checkmk 1.6 with
all apache versions this feature can not be used anymore using HTTP header
variables containing other characters than <tt>A-z, a-z, 0-9 and -</tt>. For
example <tt>X-Remote-User</tt> is still working, while <tt>REMOTE_USER</tt>
(which uses the not allowed <tt>_</tt>) is not working anymore.
This 1.6.0b3 release fixes an issue in this header variable processing and
changes the default setting in the GUI to <tt>X-Remote-User</tt>.
If you configured this before with 1.5, you will have to check your
configuration and change the HTTP header variable in the reverse proxy and
Checkmk configuration to make it work with the new variable syntax.
ID: 7821
Title: Fix adding graphs with many metrics to reports / dashboards
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.7.0i1
When trying to add graphs with a larger number of metrics to a report or dashboard using
the graph context menu, this resulted in an error "Request-URI Too Long" which is now
fixed.
ID: 7442
Title: Pagerduty notification host identifier to hostname when IP address is uknown
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
Pagerduty requires a host identifier to assign an event to the troubled
host. This was the IP address of the host, but in some cases like cloud
Services, there are no IP addresses assigned to a host. Thus the hostname
declared in Checkmk will be used when no IP address is found to declare
which host is under trouble.