ID: 5444
Title: SNMP commands: Prevent zombie processes in case of timeouts
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i2
This concerns the RAW edition or users which use CEE/CME edition of Check_MK
with deactivated inline SNMP.
When executing SNMP commands like get, getnext, walk or bulkwalk to get agent data
from hosts it may happen that these commands remain open as zombie processes.
Check_MK has been extended to deal with this situation and clean up these processes.
Details: When the command execution takes too long Check_MK sends a SIGTERM to the
process group of the executed program. After sending the signal Check_MK is now
waiting for the process to finish.
ID: 5543
Title: Host rename: Reduced duration of core downtime during host renamings
Component: Core & setup
Level: 1
Class: New feature
Version: 1.5.0i2
The most time consuming action during renaming of hosts, the rewrite of the
monitoring history, is now done while the core is running. After this is done,
the core is being stopped and the remaining history files (current one) is
updated.
ID: 5542
Title: Table quick search: Is now using regex matching instead of substring search
Component: WATO
Level: 1
Class: New feature
Version: 1.5.0i2
The quick search feature of tables is now treating the given search term as regular
expression. A case insensitive infix search is being performed with the given string.
ID: 5521
Title: logwatch: Fix exception in WATO's check parameter display
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i2
Previously, WATO's check parameter display would complain about invalid check parameters,
due to logwatch's parameter precompilation working well with the check itself, but
breaking the GUI's validation. This was a purely cosmetic issue.
ID: 5540
Title: "Graph time range" display option had no effect on Check_MK graphs
Component: metrics
Level: 1
Class: Bug fix
Version: 1.5.0i2
The graph time range configured in the view is the "default" time range and
the display option is meant to override this view default.
ID: 5413
Title: Windows agent: nocontext tag did not work for multibyte encoded logfiles
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i2
If a Windows logfile was encoded with a multibyte character encoding
the nocontext flag had no effect, always outputting the full context.
The nocontext tag now works correctly, in a way similar to single-byte
encoded logfiles.
ID: 5412
Title: Windows agent: fix logfile glob patterns without '*' at the end
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i2
Windows logfile patterns have required a wildcard '*' at the end in
order to work correctly. It was not possible to require an exact match
to the end of a line without wildcard '*' at the end. The reason was a
carriage-return (CR) character at the end of each read line that
prevented a match unless a '*' was present at the end of the pattern.
Now also patterns without a wildcard '*' at the end work correctly.