View Single Post
Old 04-04-2021, 07:22 AM   #132
noonoo
Junior Member
noonoo began at the beginning.
 
Posts: 7
Karma: 10
Join Date: Apr 2021
Device: none
More research on the timed out message

I have done some research.... Wireshark shows that there is a conversation between power search and elastic search going on.

power search is issuing a query against elastic search but always receives a 404 not found.

query:
{"_source": false, "query": {"simple_query_string": {"query": "3f55fa2b-79ac-4f40-9244-6c0d7cbaa416"}}}


response:
HTTP/1.1 404 Not Found
content-type: application/json; charset=UTF-8
content-length: 371
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"n o such index [library]","resource.type":"index_or_alias","resource.id":" library","index_uuid":"_na_","index":"library"}],"type":"index_not_found_exception","reason":"n o such index [library]","resource.type":"index_or_alias","resource.id":" library","index_uuid":"_na_","index":"library"},"s tatus":404}

I think the issue here is the method you are employing to test for the availability of elastic search. I am not a developer, but it looks like the problem is in get_elasticsearch_client(). Not sure why you are using that specific query for the test... On a new system the index has not been created yet, correct?

Cheers.
noonoo is offline   Reply With Quote