Title: Browsing man pages from command line
Class: fix
Compatible: compat
Component: checks
Date: 1701023104
Edition: cre
Level: 1
Version: 2.3.0b1
Viewing a check plugins man page using <tt>cmk -M my_check</tt> left the terminal in a bad state.
Browsing man pages using <tt>cmk -m</tt> did not work at all (still leaving the terminal in a bad state).
This is fixed.
After running the commands <tt>cmk -M my_check</tt> or <tt>cmk -m</tt> the tty was not properly restored.
Affected users can fix their prompt running <tt>stty sane</tt> or <tt>restore</tt>.
Werk 16300 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs
Class: fix
Compatible: compat
Component: metrics
Date: 1700760668
Edition: cee
Level: 1
Version: 2.1.0p37
This change reverts werk #16150, since this werk made forecast graphs basically unusable.
Furthermore, this change fixes the error mentioned above. This error occurred when computing a
forecast based on constant and incomplete input data.
------------------------------------<diff>-------------------------------------------
- Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs
+ Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs
? +
Class: fix
Compatible: compat
Component: metrics
Date: 1700760668
Edition: cee
Level: 1
Version: 2.1.0p37
This change reverts werk #16150, since this werk made forecast graphs basically unusable.
Furthermore, this change fixes the error mentioned above. This error occurred when computing a
forecast based on constant and incomplete input data.
Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs
Class: fix
Compatible: compat
Component: metrics
Date: 1700760668
Edition: cee
Level: 1
Version: 2.1.0p37
This change reverts werk #16150, since this werk made forecast graphs basically unusable.
Furthermore, this change fixes the error mentioned above. This error occurred when computing a
forecast based on constant and incomplete input data.
Werk 15977 was deleted. The following Werk is no longer relevant.
Title: db2_backup: Correct timezone difference for last backup date
Class: fix
Compatible: compat
Component: checks
Date: 1697190433
Edition: cre
Knowledge: doc
Level: 1
Version: 2.1.0p37
This werk is relevant for users monitoring the age of the last backup time of db2 databases in different timezones.
The date/time of the last backup of a db2 database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone.
When using different timezones, this leads to incorrect values for "Time since last backup".
The db2 agent plugin will now store the time in UTC and the db2_backup check will interpret the time accordingly.
You will need to update the agent mk_db2.linux or mk_db2.aix to receive the corrected times.
Werk 15976 was deleted. The following Werk is no longer relevant.
Title: mssql_backup: Correct timezone difference for last backup date
Class: fix
Compatible: compat
Component: checks
Date: 1696949130
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.1.0p37
This werk is relevant for users monitoring the age of the last backup time of mssql databases in different timezones.
The date/time of the last backup of a mssql database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone.
When using different timezones, this leads to incorrect values for "Age of last database backup" and if the age is negative, in newer Checkmk versions to the warning "Cannot reasonably calculate time since last backup (hosts time running ahead)".
The mssql agent plugin will now store the time in UTC and the mssql_backup check will interpret the time accordingly.
You will need to update the agent plugin mssql.vbs to receive the corrected times.
Werk 16008 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: HW/SW Inventory Retention Intervals: Take all matching entries into account
Class: fix
Compatible: compat
Component: inv
Date: 1700662432
Edition: cre
Level: 1
Version: 2.2.0p15
------------------------------------<diff>-------------------------------------------
Title: HW/SW Inventory Retention Intervals: Take all matching entries into account
Class: fix
Compatible: compat
Component: inv
Date: 1700662432
Edition: cre
Level: 1
- Version: 2.2.0p16
? ^
+ Version: 2.2.0p15
? ^
-
Werk 16300 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs
Class: fix
Compatible: compat
Component: metrics
Date: 1700760668
Edition: cee
Level: 1
Version: 2.2.0p15
This change reverts werk #16150, since this werk made forecast graphs basically unusable.
Furthermore, this change fixes the error mentioned above. This error occurred when computing a
forecast based on constant and incomplete input data.
------------------------------------<diff>-------------------------------------------
Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs
Class: fix
Compatible: compat
Component: metrics
Date: 1700760668
Edition: cee
Level: 1
- Version: 2.2.0p16
? ^
+ Version: 2.2.0p15
? ^
This change reverts werk #16150, since this werk made forecast graphs basically unusable.
Furthermore, this change fixes the error mentioned above. This error occurred when computing a
forecast based on constant and incomplete input data.
Werk 16297 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: juniper_trpz_cpu_util: fix TypeError ('>=' not supported between instances of 'float' and 'NoneType')
Class: fix
Compatible: compat
Component: checks
Date: 1700660050
Edition: cre
Level: 1
Version: 2.2.0p15
This werk fixes the crash mentioned above.
------------------------------------<diff>-------------------------------------------
Title: juniper_trpz_cpu_util: fix TypeError ('>=' not supported between instances of 'float' and 'NoneType')
Class: fix
Compatible: compat
Component: checks
Date: 1700660050
Edition: cre
Level: 1
- Version: 2.2.0p16
? ^
+ Version: 2.2.0p15
? ^
This werk fixes the crash mentioned above.
Werk 16290 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Limit login to single session: modify sessions lookup to enable the option
Class: fix
Compatible: compat
Component: wato
Date: 1700659867
Edition: cre
Level: 1
Version: 2.2.0p15
Prior to this werk, the user got logged out from the UI as soon as the global
setting option 'Limit login to single session at a time' was enabled. This was
due to the fact that the active sessions lookup returned an empty result which
prevented any further notification. This werk fixes this behaviour and reinstates
the behaviour of the 2.1 version.
------------------------------------<diff>-------------------------------------------
Title: Limit login to single session: modify sessions lookup to enable the option
Class: fix
Compatible: compat
Component: wato
Date: 1700659867
Edition: cre
Level: 1
- Version: 2.2.0p16
? ^
+ Version: 2.2.0p15
? ^
Prior to this werk, the user got logged out from the UI as soon as the global
setting option 'Limit login to single session at a time' was enabled. This was
due to the fact that the active sessions lookup returned an empty result which
prevented any further notification. This werk fixes this behaviour and reinstates
the behaviour of the 2.1 version.