Windows host CPU, DISK and Memory graphs not rendering

Hi,

I installed checkmk 2.1.0p16 just a few days ago. Yesterday I was bulk adding windows machines and after that I noticed that in the Windows Host dashboard the graphs for the CPU, Disk and Memory had problem rendering. Since this is my first take on checkmk I do not know if this is a bug or something
else. I have no idea how to fix this by myself.

CMK version: 2.1.0p16
OS version: Centos Rocky Linux 8.6

Error message:

2022-12-01 10:03:03,924 [40] [cmk.web 657031] http://<checkmk-server>/checkmk/check_mk/dashboard.py/checkmk/check_mk/dashboard.py?name=windows_hosts_overview Problem while rendering dashboard element 10 of type combined_graph
Traceback (most recent call last):
  File "/omd/sites/checkmk/lib/python3/cmk/gui/plugins/dashboard/graph.py", line 199, in _init_graph
    graph_recipes = resolve_graph_recipe(self._dashlet_spec["_graph_identification"])
  File "/omd/sites/checkmk/lib/python3/cmk/gui/plugins/metrics/html_render.py", line 605, in resolve_graph_recipe
    return graph_identification_types.create_graph_recipes(
  File "/omd/sites/checkmk/lib/python3/cmk/gui/plugins/metrics/identification.py", line 58, in create_graph_recipes
    return type_cls().create_graph_recipes(spec_info, destination=destination)
  File "/omd/sites/checkmk/lib/python3/cmk/gui/cee/plugins/metrics/graphs.py", line 841, in create_graph_recipes
    graphed_objects = list(find_objects_for_combined_graph(ident_info, graph_template))
  File "/omd/sites/checkmk/lib/python3/cmk/gui/cee/plugins/metrics/graphs.py", line 726, in find_objects_for_combined_graph
    for row in _get_matching_objects_for_combined_graphs(specification):
  File "/omd/sites/checkmk/lib/python3/cmk/gui/cee/plugins/metrics/graphs.py", line 1105, in _get_matching_objects_for_combined_graphs
    raise MKGeneralException(
cmk.utils.exceptions.MKGeneralException: Sorry, you cannot create combined graphs for more than 100 objects

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/omd/sites/checkmk/lib/python3/cmk/gui/dashboard.py", line 761, in _render_dashlet
    content = _render_dashlet_content(board, dashlet, is_update=is_update, mtime=board["mtime"])
  File "/omd/sites/checkmk/lib/python3/cmk/gui/dashboard.py", line 776, in _render_dashlet_content
    dashlet.show()
  File "/omd/sites/checkmk/lib/python3/cmk/gui/plugins/dashboard/graph.py", line 355, in show
    raise self._init_exception
  File "/omd/sites/checkmk/lib/python3/cmk/gui/plugins/dashboard/graph.py", line 190, in __init__
    self._init_graph()
  File "/omd/sites/checkmk/lib/python3/cmk/gui/plugins/dashboard/graph.py", line 207, in _init_graph
    raise MKGeneralException(_("Failed to calculate a graph recipe."))
cmk.utils.exceptions.MKGeneralException: Failed to calculate a graph recipe.

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

OMD[checkmk]:~$ /opt/omd/versions/2.1.0p16.cfe/bin/cmk --debug -vvn icevermg17
Checkmk version 2.1.0p16
Try license usage history update.
Trying to acquire lock on /omd/sites/checkmk/var/check_mk/license_usage/next_run
Got lock on /omd/sites/checkmk/var/check_mk/license_usage/next_run
Trying to acquire lock on /omd/sites/checkmk/var/check_mk/license_usage/history.json
Got lock on /omd/sites/checkmk/var/check_mk/license_usage/history.json
Next run time has not been reached yet. Abort.
Releasing lock on /omd/sites/checkmk/var/check_mk/license_usage/history.json
Released lock on /omd/sites/checkmk/var/check_mk/license_usage/history.json
Releasing lock on /omd/sites/checkmk/var/check_mk/license_usage/next_run
Released lock on /omd/sites/checkmk/var/check_mk/license_usage/next_run
Updating IPv4 DNS cache for icevermg17: 127.0.0.1
Trying to acquire lock on /omd/sites/checkmk/var/check_mk/ipaddresses.cache
Got lock on /omd/sites/checkmk/var/check_mk/ipaddresses.cache
Releasing lock on /omd/sites/checkmk/var/check_mk/ipaddresses.cache
Released lock on /omd/sites/checkmk/var/check_mk/ipaddresses.cache
+ FETCHING DATA
  Source: SourceType.HOST/FetcherType.PIGGYBACK
[cpu_tracking] Start [7fdd12fd3820]
[PiggybackFetcher] Fetch with cache settings: NoCache(icevermg17, base_path=/omd/sites/checkmk/tmp/check_mk/data_source_cache/piggyback, max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=True, use_outdated=False, simulation=False)
Not using cache (Cache usage disabled)
[PiggybackFetcher] Execute data source
No piggyback files for 'icevermg17'. Skip processing.
No piggyback files for '127.0.0.1'. Skip processing.
Not using cache (Cache usage disabled)
[cpu_tracking] Stop [7fdd12fd3820 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))]
+ PARSE FETCHER RESULTS
  Source: SourceType.HOST/FetcherType.PIGGYBACK
No persisted sections
  -> Add sections: []
Received no piggyback data
[cpu_tracking] Start [7fdd12e980a0]
value store: synchronizing
Trying to acquire lock on /omd/sites/checkmk/tmp/check_mk/counters/icevermg17
Got lock on /omd/sites/checkmk/tmp/check_mk/counters/icevermg17
value store: loading from disk
Releasing lock on /omd/sites/checkmk/tmp/check_mk/counters/icevermg17
Released lock on /omd/sites/checkmk/tmp/check_mk/counters/icevermg17
No piggyback files for 'icevermg17'. Skip processing.
No piggyback files for '127.0.0.1'. Skip processing.
[cpu_tracking] Stop [7fdd12e980a0 - Snapshot(process=posix.times_result(user=0.10000000000000009, system=0.020000000000000018, children_user=0.0, children_system=0.0, elapsed=0.11999999918043613))]
execution time 0.1 sec | execution_time=0.120 user_time=0.100 system_time=0.020 children_user_time=0.000 children_system_time=0.000 cmk_time_agent=0.000

Yea the dashboard Tribe has developed are for small, small customers with a few hosts, if you click on the windows or linux dashboard in a bigger environment things can just crash or you get stupid error messages.

Best way is to call that dashboard using filters

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.