Hello There,
We have CheckMK Enterprise 2.0.
I have a question when we do search in setup it displays currently indexing, please try again shortly.
We have below hosts count in CheckMK.
Will it be a reason because of number of hosts we have. We have a dedicated master node. How can I increase the resources or make config change that can help in fixing this search issue.
Thank you,
Shivdev
I have exactly the same problem with me that the search never seems to stop indexing, I have 5 sites with about 45,000 services.
OS: Debian 10
Checkmk: 2.0.0p19
regards
Michael
Hello
please have alook here: Currently indexing, please try again shortly - Checkmk Knowledge Base - Checkmk Knowledge Base
BR
Thomas
have similar problem but didn`t find where to fix
OMD[main]:~$ tail -f /var/log/web.log
tail: cannot open '/var/log/web.log' for reading: No such file or directory
tail: no files remaining
OMD[main]:~$ tail -f var/log/web.log
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 1340, in <genexpr>
if rulespec.title
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 460, in title
return self.valuespec.title()
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 453, in valuespec
return self._valuespec()
File "<string>", line 88, in _valuespec_active_checks_snmp
File "/omd/sites/main/lib/python3.9/typing.py", line 685, in __call__
raise TypeError(f"Type {self._name} cannot be instantiated; "
TypeError: Type Tuple cannot be instantiated; use tuple() instead
I guess there’s a small but significant typo in that KB article.
Instead of tail -f +/var/log/web.log it should read tail -f ~/var/log/web.log, i.e. tilde instead of plus character, so it references the log below the site dir, not the system-wide log (which probably doesn’t exist at that path anyway)
@mschlenker: not sure if that might be something for you to check/fix?
but looks like the same message … and I have no idea how it comes from…
2023-02-15 15:11:19,311 [40] [cmk.web.background-job 9519] Exception in background function
Traceback (most recent call last):
File "/omd/sites/main/lib/python3/cmk/gui/background_job.py", line 246, in _execute_function
func_ptr(*args, **kwargs)
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 496, in _build_index_background
IndexBuilder(match_item_generator_registry).build_full_index()
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 244, in build_full_index
self._build_index(self._registry.values())
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 129, in _build_index
self._do_build_index(match_item_generators)
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 147, in _do_build_index
self._add_language_dependent_item_generators_to_redis(
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 184, in _add_language_dependent_item_generators_to_redis
self._add_match_item_generator_to_redis(
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 206, in _add_match_item_generator_to_redis
cls._add_match_items_to_redis(
File "/omd/sites/main/lib/python3/cmk/gui/watolib/search.py", line 222, in _add_match_items_to_redis
for idx, match_item in enumerate(match_item_generator.generate_match_items()):
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 1327, in generate_match_items
yield from (
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 1340, in <genexpr>
if rulespec.title
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 460, in title
return self.valuespec.title()
File "/omd/sites/main/lib/python3/cmk/gui/watolib/rulespecs.py", line 453, in valuespec
return self._valuespec()
File "<string>", line 88, in _valuespec_active_checks_snmp
File "/omd/sites/main/lib/python3.9/typing.py", line 685, in __call__
raise TypeError(f"Type {self._name} cannot be instantiated; "
TypeError: Type Tuple cannot be instantiated; use tuple() instead
^C
OMD[main]:~$ tail -f ~/var/log/web.log
Yeah, sorry, haven’t looked further into this. I just wanted to quickly point out that typo in the KB.
I have found the problem … grrr it was an older extension-pack
seeU at CMKC#9…
The KB is not the realm of the KNW team, I pinged my colleagues from the consulting team. Let’s see, how fast it’ll get fixed.
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.