ID: 4756
Title: Fix possible timeouts when changing configurations or changing user profile properties
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i1
Check_MK is using generic functions to perform file IO, for example to save configuration files
of WATO or saving the user properties of the GUI. With 1.4.0b1 we introduced a change that was
intended to prevent loss of just written files during hard OS crashes. This change has now
been reverted because it behaves badly in high IO load situations and might also itself cause
high IO load in case files are written in a high frequency.
The IO behaviour in this situation has now simply been changed back to the old state before
1.4.0b1.
In future releases (1.5+) we'll find a solution to improve the handling of OS crash recovery
situations.
ID: 4819
Title: f5_bigip_cluster_status.v11_2: Fixed wrong syntax in naming of the check plugin
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
This bug led into the discovery error "missing check file". You will need
to rediscover your checks to get this service working.
ID: 4828
Title: User notification rules can now be canceled
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.5.0i1
Previously, the cancel notification rule did only apply to global notification rules.
ID: 4797
Title: Removed deprecated global service discovery setting and added new standard rule
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
Removed deprecated global service discovery setting for new created sites
and added a new standard rule which will execute every two hours a service
discovery.
ID: 4789
Title: check_mk_agent.aix: Fixed computation of uptime
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
once a day the computation of uptime has been wrong. This bug occured only
1 hour a day, when the output of uptime did contain days and minutes but
no hours.
ID: 4755
Title: Fixed possible error when processing piggyback monitoring data
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i1
An error "OSError: [Errno 2] No such file or directory: '/omd/sites/*/tmp/check_mk/piggyback/'"
could occur when using piggyback agent data (like it's done when monitoring ESX hosts / vcenters).
The error message was visible in the cmc.log and looked like this:
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> File "/omd/sites/mysite/share/check_mk/modules/check_mk_base.py", line 371, in get_host_info
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> ignore_check_interval=True)
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> File "/omd/sites/mysite/share/check_mk/modules/check_mk_base.py", line 506, in get_realhost_info
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> piggy_output = get_piggyback_info(hostname) + get_piggyback_info(ipaddress)
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> File "/omd/sites/mysite/share/check_mk/modules/check_mk_base.py", line 635, in get_piggyback_info
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> for sourcehost, file_path in get_piggyback_files(hostname):
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> File "/omd/sites/mysite/share/check_mk/modules/check_mk_base.py", line 612, in get_piggyback_files
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> for sourcehost in os.listdir(dir):
2017-06-06 06:39:36 [4] Check_MK helper [7231]: : >> OSError: [Errno 2] No such file or directory: '/omd/sites/mysite/tmp/check_mk/piggyback/backedhost'
This was some kind of race condition when one Check_MK helper cleaned up outdated piggyback files
while another helper was reading the piggyback data.
ID: 4754
Title: Fixed possible "Operation not permitted issue" during activation
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i1
In case a pid of a former activation process is reused by a process of
another user a "OSError: [Errno 1] Operation not permitted" exception
could occur.