ID: 13663
Title: Fix JSONDecodeError on crash reports view
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If a crash report was created but the crash info key was missing inside the
file within ~/var/check_mk/crashes/CRASH_ID/crash.info, the crash report view
showed an error like "json.decoder.JSONDecodeError: Expecting value: line 1
column 1 (char 0)".
ID: 13659
Title: New SMS notification script for IP modems
Component: Notifications
Level: 2
Class: New feature
Version: 2.1.0i1
Until now, it was only possible to use SMS modems that support smstools.
With this werk a new notification option "SMS (using modem API)" was added as
notification method.
The script uses the API of IP modems, currenly supporting the model "Teltonika
TRB140" and outputs SMS in the same format as the notification method "SMS
(using smstools)".
ID: 13622
Title: Fixed empty hostname in network inventory table
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 2.1.0i1
A typo led into the problem, that the field "Hostname" in the network tree
has never been filled.
ID: 13531
Title: mk_postgres: Fix Bug with password authentication method on Linux
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
For using password authentication, the Path to the pgpass file needs to be in
the third argument of the INSTANCE Parameter in postgres.cfg:
INSTANCE=/opt/cmk/etc/pgsql-12.env:checkmk:/var/lib/pgsql/12/data/.checkmk_pgpass
In pg_hba.conf, password authentication needs to be set for the checkmk user:
local all checkmk password
With these setting, the current version of the Plugin asks for the password of
the checkmk postgres user when it is executes manually.
The PGPASSFILE is read correctly from the config, and it may work on Windows,
but on Linux we are using "su -" to change to the postgres OS user and we are
loosing all environment variables which are set to the Popen function via
self.my_env.
This change will add the PGPASSFILE correctly after switching the user. This is
tested successfully on Linux with a PostgresSQL 12 DB.
It will also cause no issue when not using the password authentication, since
the variable is empty and is not used.
ID: 13689
Title: Change xinetd/systemd unit names in Linux agent of Checkmk Raw Edition
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
This werk changes the systemd or xinetd unit names of the agent
package.
Users of the packages created by the Agent Bakery (Enterprise
and Managed Service Edition only) are not affected.
Until now the xinetd service name had been <tt>check_mk</tt>,
and the systemd units names were <tt>check_mk@.service</tt>
<tt>check_km.socket</tt> and <tt>check_mk-async.service</tt>.
In all of these, the "<i>check_mk</i>" bit has been replaced
with "<i>check-mk-agent</i>", to be consistent with the baked
packages of the CEE/CME.
Upon update, an existing configuration file
<tt>/etc/xinetd.d/check_mk</tt> will be migrated, and/or the
new systemd unit files are deployed.
If you have customized you systemd units (for instance by
placing files to <tt>/etc/systemd/system/</tt>), you must
rename them accordingly!
ID: 13662
Title: Fix saving of comment if BI pack is edited
Component: BI
Level: 1
Class: Bug fix
Version: 2.1.0i1
If you edited a BI pack and added a comment, this comment was not saved to the
configuration.
ID: 13290
Title: Fixed broken SLA painters in customize view
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
The sla painters <tt>Host/Services: SLA - Column specific</tt> and <tt>Host/Services: SLA - Service specific</tt> were
broken, showing up not at all or displaying incorrect painter titles in the dropdown menu.
ID: 13710
Title: <tt>oracle_instance</tt>: Handle unresponsive databases and login failures correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In case of unresponsive databases or login failures, the check plugin
<tt>oracle_instance</tt> went UNKNOWN and reported
"Item not found in monitoring data".
Instead, the plugin now goes CRIT and reports
"Database or necessary processes not running or login failed".
This also covers the case where a process which is needed to monitor
the databases is not running (e.g. <tt>ora_pmon</tt>).