[Release] Checkmk stable release 2.0.0p16

Announcements
, , ,
1

Dear friends of Checkmk,

the new stable release 2.0.0p16 of Checkmk is ready for download.

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

Changes in all Checkmk Editions:

BI:

  • 13282 FIX: BI datasource program: Fixed non-working aggregation filters with older configurations

Checks & agents:

  • 12240 mk_cups_queues: Accept printer names with hyphens ("-")
  • 13490 Eaton Power Xpert: Discover UPS services
  • 13468 mrpe: Do not crash upon invalid metrics
  • 13470 FIX: “Item not found” for cached local checks on clusters
  • 13450 FIX: apt: Fix APT Ubuntu security updates classification
  • 13354 FIX: check_sftp: Fix password store usage
  • 13487 FIX: datapower_fan: Fix KeyError (…)
  • 13517 FIX: gude_pdu: Fix errors during discovery and checking
  • 13489 FIX: mem_win: Fix missing levels in service graphs
  • 13494 FIX: mongodb_counters: Fix “ValueError: too many values to unpack (expected 3)”
  • 13516 FIX: mongodb_replica: Show both active and passive secondaries
  • 12335 FIX: Fix calculation of issued rds_licenses
  • 13188 FIX: cisco_qos: 0 bandwidth leads to permanently critical services
  • 13469 FIX: cisco_ucs_hdd: hot spares are OK to be inoperable
  • 13526 FIX: cisco_wlc{,_clients}: Support model Cisco WLC 3504
  • 13527 FIX: enviromux_sems_digital: Fix discovery
  • 13472 FIX: fjdarye500_disks_summary: “Transform failed” during cmk-update-config
  • 13253 FIX: if_brocade_lancom: move mapping information away from interface description
  • 13449 FIX: mk_mysql: Fix missing includes warning
  • 11902 FIX: Fix crash in Rittal CMC III temperature check
    NOTE: Please refer to the migration notes!

Core & setup:

  • 13079 FIX: REST API crash when setting SNMP credential
  • 13080 FIX: REST API: allow setting of downtime from read-only site

Notifications:

  • 13492 FIX: Notification plugins: Fix proxy setting “Connect without proxy”

Other components:

  • 13316 FIX: Checkmk now requires Appliance firmware 1.4.17 or newer

Setup:

  • 13314 SEC: Distributed monitoring: Do not log site secret on remote site
  • 13496 FIX: Fix “Request URI too long” error on upload of iCalendar files
  • 13384 FIX: Fix ‘Request-URI Too Long’ error on rule search
  • 13385 FIX: Fix error on uploading iCalendar with recurrence rules

Changes in the Checkmk Enterprise Edition:

Core & setup:

  • 12700 FIX: Fix false positives and high CPU for smart ping

Livestatus proxy:

  • 13518 FIX: Liveproxy Daemon: React to changes in CAs without manual restart
  • 13281 FIX: Liveproxyd: Fixed unresponsive communication with remote sites

NagVis:

  • 13493 FIX: MTR agent plugin: Run also under systemd

Reporting & availability:

  • 12998 Title alignment in report graphs
  • 13497 FIX: Fix BI name and group filter in report elements

Setup:

  • 13471 FIX: mk_logwatch: validate regular expressions upon rule creation

Changes in the Checkmk Managed Services Edition:

You can download Checkmk from our download page:

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

4 Likes
2

This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information. The HTTP 414 URI Too Long response status code indicates that the URI(Uniform Resource Identifier) requested by the client is longer than the server is willing to interpret.

To resolve this problem :

  • By POST request: Convert query string to json object and sent to API request with POST.

  • By GET request: Max length of request is depend on sever side as well as client side. Most webserver have limit 8k which is configurable. On the client side the different browser has different limit. The browser IE and Safari limit to 2k, Opera 4k and Firefox 8k. This means that the max length for the GET request is 8k and min request length is 2k.

If exceed the request max length then the request truncated outside the limit by web server or browser without any warning. Some server truncated request data but the some server reject it because of data lose and they will return with response code 414 Request-URI Too Long.

Under Apache, the limit is a configurable value, LimitRequestLine. If you want to increase URL limit to 5000 characters (bytes), add the following lines to your server configuration or virtual host file.

LimitRequestLine 5000

If you want to increase maximum header length supported by Apache to 3000 characters, then add the following line.

LimitRequestFieldSize 3000

3

You are referring to a rather old patch release of the oldstable version of Checkmk.
Your feedback is appreciated and relevant, but I think this is more of an architectural question.

I only found one more or less recent troubleshooting post here. If you think this is still relevant for the most recent Checkmk releases, do let me know and I will tag along the information.