ID: 4219
Title: Trap processing with community "public" is now only default and not accepted in all cases anymore
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.4.0i4
Since several versions you can configure the Event Console to receive only SNMP traps having
specific SNMP communities set. Previous versions were simply processing all traps.
The community "public" was somehow special since traps with this community were accepted in
any cases. We have now changed the community public to just be accepted by default. In case
you add additional communities, these will also be accepted. But in the moment you remove
the public community, the traps containing this community will not be accepted anymore.
ID: 4218
Title: Disabling replication with a site did not clear the changes for this site (1.4.0i3 regression)
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.4.0i4
ID: 4217
Title: WATO rules can now be moved via drag&drop
Component: WATO
Level: 1
Class: New Feature
Version: 1.4.0i4
Other list elements will be movable like this soon too.
ID: 4008
Title: Windows Agent, dotnet_clrmemory section: prevent indefinite freeze of windows agent
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i4
The windows agent could freeze in the dotnet_clrmemory section while querying WMI counters.
This freeze is presumably caused by an earlier WMI query for the skype section which failed, due to a non-existing wmi counter.
ID: 4007
Title: Windows Agent: Reduced number of needless WMI Queries when Skype performance counters are missing
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i4
The windows agent now skips the processing of the skype section earlier, if the
performancecounters are not available. This presumably fixes an error where the windows
agents hangs in a followup WMI query.
ID: 4006
Title: Windows Agent: Fixed possible memory leak when using logwatch with vista api setting
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i4
ID: 4119
Title: check_mk_agent.solaris: fixed run_cached function
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i4
Previously the run_cached function simply exited if cache file $CACHEFILE.new was too old.
This has been fixed now, the function acts just like in the Linux agent - it removes the process of the file as well as the file itself.