ID: 6646
Title: CPU utilization per process can be weighted by total CPU number
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Processes that where monitored on CPU utilization did not have a consistent
behavior. On windows systems 100% CPU utilization implied all cores in the
system where at max load. On other systems every core contributed with a
100% at full load, thus the maximum load was N*100%.
This was also inconsistent with the system wide CPU utilization check
where, 100% is all cores at full load.
Consistency is brought is this werk, where 100% is all cores at full load
by default. For backwards compatibility with previous configurations, where
threshold rules were explicitly configured, the old behavior continues to
be used until the user explicitly chooses a particular behavior.
This option is available under CPU rescale maximum load in the process
discovery rules.
ID: 6414
Title: aix_memory: Fix graph colouring and labelling
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Map the performance value name of averaged memory
to the correct metric.
ID: 6849
Title: Analyze configuration: Fixed wrong results for liveproxyd and persistent connection tests
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previously all analyze configuration tests were executed locally on each site.
In case of the liveproxyd tests and persistent connection tests this was wrong
because the tests have to check the connection configuration for a specific
site on the central site.
ID: 6846
Title: More secure password hashing
Component: Multisite
Level: 2
Class: Security fix
Version: 1.6.0i1
Passwords of local users of the Check_MK GUI are now hashed using SHA256
(salted, 535000 rounds) to increase the security of the stored user logon
passwords.
All existing users will still be able to login using their already hashed
passwords. Once a user changes his password or a new user is created, these
will be hashed using the new algorithm.
Why SHA256? Check_MK supports different authentication frontends for verifying
the local credentials: a) basic authentication (done by apache) and b) the GUI
form + cookie based authentication.
The default is b). This option is toggled with the "omd config" option
MULTISITE_COOKIE_AUTH. In case the basic authentication is chosen it is only
possible to use hashing algorithms that are supported by apache which
performs the authentication in this situation.
For best compatibility in all mentioned situations we use the SHA256 scheme.
ID: 6671
Title: WATO Web API: Now able to configured rulesets with boolean settings
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Rules with a configurable positive/negative outcome where incorrectly translated
in a <tt>get_ruleset</tt> API call. Furthermore, <tt>set_ruleset</tt> had an error when
validating these kind of rules.
ID: 6507
Title: Fixed 100% CPU usage of the CMC after writing to its command pipe
Component: Core & setup
Level: 2
Class: Bug fix
Version: 1.6.0i1
After writing to its command pipe tmp/run/nagios.cmd, the CMC's CPU usage
went up to 100%. This has been fixed.
ID: 5516
Title: cmk-update-agent: Catch HTTPS redirect
Component: agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
A communication between the Agent Updater and the Check_MK-Server
won't succeed if the communication protocol is configured to HTTP
while the server enforces HTTPS. The reason is that the POST data
sent by the Agent Updater will be lost on the redirect.
So far, this is normal HTTP behavior. Nonetheless, the Agent Updater
now handles this situation by detecting the redirect and directly
sending its data via (unverified) HTTPS.
A warning will therefore be displayed to the user respectively written
to log.
ID: 6645
Title: Solaris Agent: Correctly separate cputime and elapsed time in agent info
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The process information delivered by the agent has been upgrated multiple times by requirements of users or information available from the OS. The ps agent tracked the memory outilization of a process by its name, but could not access information of process id and the time of life(elapsed time) of a running process, as such information was misplaced by the agent and thus ignored by the check. This fix brings this data into consideration by the check.