[Release] Checkmk stable release 2.1.0p33

Announcements
, , , ,
1

Dear friends of Checkmk,

the new stable release 2.1.0p33 of Checkmk is ready for download.

This maintenance release ships with 23 changes affecting all editions of Checkmk,
2 Enterprise Edition specific changes and 0 Managed Services Edition specific changes.

Support periods can be found here: Checkmk versions

Changes in all Checkmk Editions:

Agent bakery:

  • 14614 FIX: Jolokia: manpages indicated agent support for Linux only
  • 15910 FIX: agent_aws: DNSName not available in load balancer info
  • 15289 FIX: mk_oracle: Revert werk 15559, use tnsping when availableā€¦

Checks & agents:

  • 16091 FIX: Local checks: Show metric values in service summary only if WARN/CRITā€¦
  • 15906 FIX: apc_symmetra: Improve wording in ruleset
  • 15913 FIX: check_disk_smb: Fix rule transform when updating from 2.1.0p30 and lowerā€¦
  • 15290 FIX: df: Support block device UUIDs with spaces
  • 15771 FIX: discovery: remove vanished labels on ā€˜Accept allā€™
  • 15911 FIX: jenkins_jobs: Consider ā€˜Override check state based on last build resultā€™ option
  • 15605 FIX: mk_filestats: Improve Handling of non-UTF-8 file pathsā€¦
  • 15970 FIX: mk_oracle: Fix ā€œDatabase or necessary processes not running or login failedā€ error due to race conditionsā€¦

Core & setup:

  • 16016 FIX: mk_postgres: addition of option to specify instance nameā€¦

Notifications:

  • 15941 FIX: Fix possible failed notifications on appliances

REST API:

  • 16052 FIX: time_period: the ā€˜excludedā€™ field can now be updated using the REST API
  • 15982 FIX: time_period: Creation, modification or deletion of time periods from the API now adds entries to activate changes
  • 15983 FIX: time_period: verify time_period usage before deletion and fix the reference for time_periods being saved to the configuration file in exclude fieldā€¦
  • 15889 FIX: password_store: pattern for password store identifiers should be the same as the guiā€¦
    NOTE: Please refer to the migration notes!

Setup:

  • 15939 FIX: Fix possible ā€œInternal Server Errorā€ on save of changesā€¦
  • 16054 FIX: custom notes for host and services: Fix multiple note display and fix note search path for services
  • 16095 FIX: hosts: Remove invalid ā€œRemove TLS registrationā€ on host search resultsā€¦

Setup, site management:

  • 16086 Support Diagnostics: Include basic SELinux infos

User interface:

  • 15936 FIX: Fix redirect for mobile views on login
  • 15934 FIX: Fix selection for downtime commandsā€¦

Changes in the Checkmk Enterprise Edition:

Agent bakery:

  • 16076 Agent Bakery: ā€œBake revisionā€ is now configurableā€¦
    NOTE: Please refer to the migration notes!
  • 16077 FIX: Agent Bakery: Leftover packages of non-agent hostsā€¦

Changes in the Checkmk Managed Services Edition:

NO CHANGES

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

List of all changes: Werks

Please mail bug reports and qualified feedback to feedback@checkmk.com.
We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

1 Like
2

Hello community,

I am upgrading from CRE 2.1.0.p26 to CRE 2.1.0p33 and after running:

omd update

I get the following error:

Traceback (most recent call last):
  File "/omd/sites/mysite/bin/omd", line 63, in <module>
    omdlib.main.main()
  File "/omd/versions/2.1.0p26.cre/lib/python3/omdlib/main.py", line 4685, in main
    command.handler(version_info, site, global_opts, args, command_options)
  File "/omd/versions/2.1.0p26.cre/lib/python3/omdlib/main.py", line 2694, in main_update
    exec_other_omd(site, to_version, "update")
  File "/omd/versions/2.1.0p26.cre/lib/python3/omdlib/main.py", line 4530, in exec_other_omd
    os.execv(omd_path, sys.argv)
FileNotFoundError: [Errno 2] No such file or directory
OMD[mysite]:~$

This is the first time an update has failed.

OMD[mysite]:~$ omd versions
1.6.0p14.cre
2.1.0p16.cre
2.1.0p17.cre
2.1.0p18.cre
2.1.0p19.cre
2.1.0p22.cre
2.1.0p26.cre (default)
2.1.0p33.cre

Python versions on my system

[root@omd]# python3 --version
Python 3.11.5

OMD[mysite]:~$ python3 --version
Python 3.9.16

Does anyone have a solution?

3

I would start by cleaning up the old unused versions of CheckMK.
Not sure if that will help, but couldnā€™t hurt :slight_smile:

4

Thanks for your answer. I delete them from time to time. Last time from 2.1.0p15 backwards. Iā€™ll delete them when I fix this. thank you.

5

Perhaps try updating to like another build first to see if that makes a difference? P27 or something like that.

It also still shows 1.6.0p14, not sure it that might cause something.

6

Have you tried updating from the root user instead of from the site?

omd update ā€œSITENAMEā€
Without the quotes

7

Thanks @erik, I will try what you say.

Regards

8

Hello to all,

itā€™s all sorted out. The mistake was a stupid mistake I made. The package didnā€™t download completely, although it did let me yum install. I noticed it when I compared the rpm sizes of version p27 and p33.

Regards and thanks for reading me.

1 Like
9

I recommend verifying the file hash of the downloaded file.
    sha256sum check-mk-package-file-name

Correct SHA 256 hash value is shown on the download page.

1 Like