Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15969 discussions

Checkmk Werk 14452: ESX vSphere: Add build number to HW/SW inventory

by Moritz Kiemer

ID: 14452 Title: ESX vSphere: Add build number to HW/SW inventory Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1

2 years, 2 months

Checkmk Werk 13911: Improve RRD logging when path to DB is missing

by Mathias Laurin

ID: 13911 Title: Improve RRD logging when path to DB is missing Component: Livestatus Level: 1 Class: Bug fix Version: 2.2.0i1 Attempts to flush the DB when the path to the RRD database is missing would produce the rather unhelpful error "Error flushing RRD: Usage: rrdtool flushcached [--daemon|-d <addr>] <file> [<file> ...]" This fix removes the flushing attempt and silences the corresponding error in the log.

2 years, 2 months

Checkmk Werk 14453: cisco_temperature: Use sensors name instead of description

by External contributor

ID: 14453 Title: cisco_temperature: Use sensors name instead of description Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The check plugin <i>Cisco Devices: Temperature Sensors</i> /<tt>cisco_temperature</tt>) previously used the entPhysicalDescr MIB instead of the entPhysicalName MIB (.2 and .7 of 1.3.6.1.2.1.47.1.1.1.1 respectively). On Cisco IOS-XE the entPhysicalDescr MIB and entPhysicalName MIB are identical. However on Cisco IOS-XR all fibre module power levels show "Power Sensor" in entPhysicalDescr, and the unique interface name in entPhysicalName. Before this change IOS-XR would only have a single power sensor called "DOM Power Sensor".

2 years, 2 months

Checkmk Werk 14551: IPMI sensors include temperature measurements

by External contributor

ID: 14551 Title: IPMI sensors include temperature measurements Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 If the option '--output-sensor-thresholds' was disabled on an IPMI device, the temperature would not be recorded as a metric.

2 years, 2 months

Checkmk Werk 14281: Fix local privilege escalation from site users

by Lars Michelsen

ID: 14281 Title: Fix local privilege escalation from site users Component: Site Management Level: 1 Class: Security fix Version: 2.2.0i1 Each Checkmk site provides it's HTTP services (UI, APIs) using it's own site Apache process. Global access to this site Apache is provided via the system Apache which is opening the 80 and 443 ports for external requests, depending on your system configuration. To learn about the site Apache, the system Apache reads a reverse proxy configuration provided by the site user. This could be used by a site user to make the system Apache execute code as root user, since the System Apache is typically started initially with root privileges. To close this gap, we now need to separate the system Apache configuration from the site user access. To eliminate the privilege escalation, you will have to execute the command <tt>omd update-apache-config [SITE]</tt> once for each of your sites after the <tt>omd update</tt> command. Besides the one-time fix, this change has a consequence for the use of <tt>omd config</tt> and <tt>omd update</tt>. There are two situations where this is relevant: a) If you change the options APACHE_TCP_ADDR, APACHE_TCP_PORT or APACHE_MODE You will have to call <tt>omd update-apache-config [SITE]</tt> as root user after changing one of the site configuration options APACHE_TCP_ADDR, APACHE_TCP_PORT or APACHE_MODE. This needs to be done to update and apply the system Apache configuration. If you don't do this and start your site, your UI may be not available anymore. The <tt>omd config</tt> command will output a warning to notify you about this necessary step in the future. b) If you execute <tt>omd update</tt> and the proxy configuration changes The update is performed as site user. Which means that, after this werk, we can not update and apply the system apache configuration anymore automatically. To apply the latest apache configuration, the command <tt>omd update-apache-config [SITE]</tt> needs to be executed after the update. The <tt>omd update</tt> will automatically detect the need for this additional step and show you a confirmation dialog before starting the update to notify you about this necessary step and giving you the chance to interrupt the procedure in case you don't have the option to execute the command as root user. All maintained versions (>=1.6) are subject to this vulnerability. It is likely that also previous versions were vulnerable. Users of previous versions are highly recommended to update or consider other mitigations. We thank Jan-Philipp Litza (PLUTEX GmbH) for reporting this issue!

2 years, 2 months

Checkmk Werk 14409: Jenkins plugin now recognises jenkins.branch.Organizationfolder as a folder

by Max Linke

ID: 14409 Title: Jenkins plugin now recognises jenkins.branch.Organizationfolder as a folder Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Some jenkins plugins for git forges (i.e. gitea) use the jenkins.branch.Organizationfolder class as a folder. This was previously as a single job and parsing failed. This is fixed now. No user interaction required.

2 years, 2 months

Checkmk Werk 14488: Mega menu: Expand search bar width

by Kenneth Okoh

ID: 14488 Title: Mega menu: Expand search bar width Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 The search bars in the mega menus "Monitor" and "Setup" are set to a higher default width and they now grow with the mega menu's width. Users can now put in longer and more complex search terms without running out of space.

2 years, 2 months

Checkmk Werk 14447: mk_oracle: Cleanup long running processes on AIX

by Moritz Kiemer

ID: 14447 Title: mk_oracle: Cleanup long running processes on AIX Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The cleanup of long running processes forked by the mk_oracle plugin was not working reliably on AIX. With this werk we switch to the more robust approach used by the agents. We also remove the cache files of those jobs, as they are outdated anyway.

2 years, 2 months

Checkmk Werk 14165: BI configuration: Automatically show/hide "Business intelligence" menu entry

by Andreas Boesl

ID: 14165 Title: BI configuration: Automatically show/hide "Business intelligence" menu entry Component: BI Level: 1 Class: New feature Version: 2.2.0i1 The <tt>Business intelligence</tt> menu entry is only shown when at least one aggregation is activated.

2 years, 2 months

Checkmk Werk 14444: Unix agents: Change error handling for non-terminating asynchrounus agent plugins

by Moritz Kiemer

ID: 14444 Title: Unix agents: Change error handling for non-terminating asynchrounus agent plugins Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 This change affects asynchronously executed agent plugins for the Checkmk agents for Linux, AIX, Solaris, FreeBSD and OpenWRT. If such plugins did not terminate after a set amount of time, the corresponding process is killed by the agent. Previously, the cached data would still be transmitted, eventually letting the affected services go stale. With this werk we no longer transmit the outdated data, which will result in the services being UNKNOWN. This behaviour is consistent with a synchrounus plugin that crashes.

2 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1