[Release] Checkmk stable release 2.3.0p18

Announcements
, , , ,
1

Dear friends of Checkmk,

the new stable release 2.3.0p18 of Checkmk is ready for download.

This stable release ships with 28 changes affecting all editions of Checkmk,
1 changes for the Enterprise editions, 0 Cloud Edition specific and
1 Managed Services Edition specific changes.

Changes in all Checkmk Editions:

Checks & agents

  • 16254 Add metric translations mrpe based windows checks…
  • 16851 mk-sql: VCRUNTIME dll isn’t required…
  • 17259 FIX: Fix mismatching network interface and switch port services…
    NOTE: Please refer to the migration notes!
  • 17088 FIX: mk_logwatch: Remove colored output support in debug mode…
    NOTE: Please refer to the migration notes!
  • 17257 FIX: postfix_mailq: Fix service reporting missing item after upgrade…
    NOTE: Please refer to the migration notes!
  • 14237 FIX: Fixed performance problems for various command line operations…
  • 16849 FIX: Legacy MS SQL reports correctly databases with trailing spaces
  • 16850 FIX: MK-SQL: better support for databases with non-Unicode collation…
  • 17331 FIX: azure: Fix app registration crashing while parsing agent output…
  • 17292 FIX: check_httpv2: Body checking: Fixes for inverted regular expressions…
  • 17039 FIX: db2_sort_overflow: Fix typo in service summary…
  • 17208 FIX: kube: Continue Upon Unresponsive Node…
  • 16896 FIX: mbg_lantime_ng_state: ValueError (could not convert string to float: ‘n/a’)…
  • 17305 FIX: mk_filestats: Fix recent regression in file filtering…
  • 17311 FIX: mk_logwatch: Apply context to informational (OK) messages…
  • 17124 FIX: mk_postgres: Fix ‘Argument list too long’…
  • 16871 FIX: smart: Monitor SATA disks connected via HBA…

Event console

  • 16567 FIX: Re-add missing “History action type” filter…

HW/SW inventory

  • 17135 FIX: HW/SW Inventory update: Do not archive remote tree if only retention intervals have changed…
  • 17134 FIX: HW/SW inventory: Do not archive or save trees with empty nodes…

Other components

  • 17276 FIX: NagVis: Updated to 1.9.44

Setup

  • 17095 SEC: Sanitize Host and Folder Credentials in Audit Log…
    NOTE: Please refer to the migration notes!
  • 17096 SEC: CSRF token leaked in URL parameters (CVE-2024-38863)…
  • 17258 FIX: Fix host renaming failing when host is node of cluster…

Site management

  • 17207 FIX: omd update: Reintroduce Log “Verifying site configuration”…
  • 16895 FIX: omd: curl wrapper not used for all supported versions of SLES and EL…

User interface

  • 17294 Improve logging for agent auto-registration and automatic host removal…
  • 17330 FIX: Fix comment selection affecting comments across multiple sites…

Changes in the Checkmk Enterprise Edition:

Notifications

  • 17145 SEC: Information leak in mknotifyd…

Changes in the Checkmk Cloud Edition:

NO CHANGES

Changes in the Checkmk Saas Edition:

NO CHANGES

Changes in the Checkmk Managed Services Edition:

Setup

  • 17310 licensing: Changes in license compatibility…
    NOTE: Please refer to the migration notes!

You can download Checkmk from our download page: Download Checkmk for free | Checkmk

List of all changes: Werks

We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

1 Like
2

Since the update, nagvis has been incredibly slow. Can anyone else confirm this?

3

I upgraded from 2.2 to this version today. I find the whole CheckMK incredibly slow tbh.

1 Like
4

I found that version 2.3.0p18 is much slower when synchronizing and activating changes in our distributed environment (two or three times slower than 2.3.0p17).

Also my users are complaining about 2.3.0p18 responding much slower (don’t have details at which actions so far)

1 Like
5

HI @MasopustC @erik
If you can provide some specific information then we can look into it. If possible create a ticket with some diagnostic information so that we can investigate on this topic.

Hi @CoLa

Do you see any obvious errors in the Site Apache error.log ? On which page of Nagvis do you experience slowness ? Can you be more specific here?

With a standard update from 2.3.0p17 to 2.3.0p18 , I don’t see any obvious problems related to slowness in general.

6

@chauhan_sudhir
We have now only experienced problems with Nagvis. And we can easily work around this, we are currently using the Nagvis from p17 (1.9.42) and not from p18 (1.9.44). A ticket is already open and the HAR file has also been uploaded.

image
image1140×34 2.6 KB

The ajax_handler.php process alone takes >10 seconds (ONLY in the current Nagvis in p18, in p17 everything is completely normal). Something about Nagvis 1.9.44 or 1.9.43 is definitely different than 1.9.42 (which is used in p17).

We have already been able to rule out warnings / errors in the error_log

1 Like
7

Thanks for the ticket. We can then look into this internally.

8

It needed a few days, it’s performing better now. I upgraded friday night.
Then saturday evening it was still performing slow. But now a few days later it’s working better.

I did notice an increase of CPU average use on the master site from around 15% towards 30-40% usage, but that might be expected with the 2.3 upgrade?

9

This will describe the behaviour: Update to version 2.3.0

10

We also experience the same thing. It has become very slow. It uses twice as much cpu as before the upgrade. “Activate on sites” can sometimes take forever. And lots of other slowness issues.

11

@eplpaho : we are not yet 100% positive, but our delays at the activation may have come from our antivirus solution (TrendMicro).