Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15927 discussions

Check_MK Werk 2953: netextreme_psu_in: Fixed discovery of Power Supply Input checks

by Lars Michelsen

ID: 2953 Title: netextreme_psu_in: Fixed discovery of Power Supply Input checks Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i4

8 years, 8 months

Check_MK Werk 2948: oracle_tablespaces: Fixed exception when section contained empty line

by Lars Michelsen

ID: 2948 Title: oracle_tablespaces: Fixed exception when section contained empty line Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i4

8 years, 8 months

Check_MK Werk 2951: ibm_svc_disks: Fixed exception with disks having a TB capacity

by Lars Michelsen

ID: 2951 Title: ibm_svc_disks: Fixed exception with disks having a TB capacity Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i4

8 years, 8 months

Check_MK Werk 2950: citrix_controller.sessions: Fixed crash in case active/inactive infos are missing

by Lars Michelsen

ID: 2950 Title: citrix_controller.sessions: Fixed crash in case active/inactive infos are missing Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i4

8 years, 8 months

Check_MK Werk 2949: oracle_logswitches oracle_sessions oracle_version: Improved handling of legacy oracle plugin error cases

by Lars Michelsen

ID: 2949 Title: oracle_logswitches oracle_sessions oracle_version: Improved handling of legacy oracle plugin error cases Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i4

8 years, 8 months

Check_MK Werk 2937: mrpe: check now supports service descriptions using percent-encoded characters

by Sebastian Herbord

ID: 2937 Title: mrpe: check now supports service descriptions using percent-encoded characters Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i4 mrpe services can now contain any character using percent encoding. This is particularly useful to include spaces in the service description as that was previously impossible due to the way mrpe.cfg was parsed. This change is incompatible as any %xx sequence will now be converted whereas it was previously included in the service description as unchanged.

8 years, 8 months

Check_MK Werk 2892: qlogic_fcport: now supports QLogic FC Switch SANBox 5802 series

by Simon Betz

ID: 2892 Title: qlogic_fcport: now supports QLogic FC Switch SANBox 5802 series Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i4

8 years, 8 months

Check_MK Werk 2947: LDAP: Simplified automatic sync logic

by Lars Michelsen

ID: 2947 Title: LDAP: Simplified automatic sync logic Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.7i4 By default once an LDAP connection has been configured the LDAP synchronization was performed automatically in background in different situations: <ul> <li>During regular page processing (every 5 minutes)</li> <li>When opening the users configuration page</li> <li>Before activating the changed configuration</li> <li>On a remote site, when it receives a new configuration</li> </ul> This was configuable using the config option Automatic User Synchronization. One problem with the default configuration was that it enabled the sync also for slave sites in distributed environments. Having the sync enabled on a slave site a change in LDAP would trigger a change on the slave site which is then preventing further activating of changes from the master. One had to drop this change entry manually to solve this situation. Another problem was that such LDAP sync was executed in some kind of random way when any HTTP request could trigger it. This felt odd in cases where the LDAP sync could take a longer time when for example saving of a view took 50 seconds instead of less than one second. The sync during activating of the configuration was slowing down the workflow when the sync took longer. So we decided to change the automatic user synchronization to work this way now: It is now scheduled by the generic multisite cron job which is executed once a minute. The LDAP sync then triggered and starts when the previous synchronization has finished more than 5 minutes before. This interval can still be configured for each LDAP connection. The new default configuration is that the automatic LDAP synchronization is performed only on the master site in distributed setups. But you can change the option Automatic User Synchronization to either On all sites to make it be executed on all your sites or completely disable the automatic synchronization. You have the option to change this setting for individual sites using the site specific global settings. Once at least one LDAP connection is configured the Sync Users button is shown on the users page. It can be used to trigger the user synchronization manually.

8 years, 8 months

Check_MK Werk 2946: LDAP: User created during login does not trigger full user synchronisation anymore

by Lars Michelsen

ID: 2946 Title: LDAP: User created during login does not trigger full user synchronisation anymore Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.7i4 Previously, when a LDAP user logged in for the first time and the user was not created by an LDAP sync before, it triggered a full LDAP sync which might have created a lot of other users. This has been changed now to only synchronize this single user based on the sync configuration.

8 years, 8 months

Check_MK Werk 2945: LDAP: Fixed broken sync for LDAP connections named "ldap"

by Lars Michelsen

ID: 2945 Title: LDAP: Fixed broken sync for LDAP connections named "ldap" Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.7i4 Custom LDAP connections created with the ID "ldap" could not synchronize users correctly.

8 years, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1