[GUI Plugin] Power (Full-text) Search

[DNSB]

I played with Power Search 2.0/Elasticsearch 7.12.0 for a bit. I did the MSI with install as service and no joy. When I try to customize the plugin, clear search index takes about 20 seconds and returns:

calibre, version 5.14.0
ERROR: Power Search: Timed out waiting for ElasticSearch to start.

I added a dummy batch file containing "exit 0" to ensure that the attempt to start Elasticsearch returned success and no difference.

While waiting for the error message, I opened another tab in Firefox and it seemed to be happy as in the attached image.

I tried the zip file install, ran elasticsearch-service.bat install and then start and the service was installed and happily running. I then ran calibre, went into PowerSearch's configuration and exactly the same results.

If I try to run PowerSearch, I get a momentary popup and calibre closes.

[ownedbycats]

I tried copying the elasticsearch-service.bat files from the zip file to my existing msi installation. I got the usual error.

[DNSB]

If the service is running, running the batch file should not be necessary. What I've found is that PowerSearch does not seem to be detecting the running service even it is started before calibre is launched.

[mapozyan]

Sorry guys for making so much troubles setting things up. I must admit I didn't use MSI install. Copying elasticsearch-service.bat won't help either because there are some more files that are missing in MSI when you install it without "run as a service" option.

I am checking now how can I fix that.

[ownedbycats]

The weird thing is that i set it to run as a service and it's working. Just not in Power Search.

[Uncle Robin]

Originally Posted by mapozyan

Sorry guys for making so much troubles setting things up. I must admit I didn't use MSI install. Copying elasticsearch-service.bat won't help either because there are some more files that are missing in MSI when you install it without "run as a service" option.

I am checking now how can I fix that.

I wonder what is different about my configuration that it is running flawlessly as is?

[mapozyan]

Originally Posted by Uncle Robin

I wonder what is different about my configuration that it is running flawlessly as is?

Did you update to 2.0.0?

[Uncle Robin]

Originally Posted by mapozyan

Did you update to 2.0.0?

Yes. Power Search 2.0.0 and ElasticSearch 7.12.0, installed via MSI and running as a service. It not only works without any issues, but PowerSearch seems much faster than earlier versions.

[noonoo]

Hi!
I am also experiencing the issue with Power Search unable to connect to Elastic Search.
I installed Elastic Search 7.12.0 from the .zip archive. Power Search does start the service if it is stopped but will always end up displaying the dialog with the "Timed out ..." message (after 1 minute).
If I start the service prior to opening the Power Search dialog it will not try to start the service again but regardles of which action i perform (search, index books, delete index) I always get the "Timed out..." message.

OS: Windows 10
Calibre: 5.14
Elastic Search: 7.12.0
Power Search: 2.0.0

[mapozyan]

Issues fixed! Please update to version 2.0.1.

[mapozyan]

Originally Posted by Uncle Robin

I wonder what is different about my configuration that it is running flawlessly as is?

I guess many people installed new version of ElasticSearch and the problem was when you try to connect to clean ElasticSearch instance. If you are using same instance as before the update to 2.0.0 it would work normally.

[noonoo]

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.

[mapozyan]

Originally Posted by noonoo

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.

All correct, thats an expected behavior.

I just realized that its not always that obvious to detect the moment when ElasticSearch is completely up and running. There is ping method available for that, but even after it succeeds the next search sometimes might fail. So I am doing some fake search to make sure that the service is already responding in expected manner. And 404 error code is OK, i.e. we interpret it as a signal that ElasticSearch is running.

Thanks for your research though. It was very close to the actual issue, so in version 2.0.0 HTTP error code 404 was not ignored in some other cases.

[Uncle Robin]

Originally Posted by mapozyan

I guess many people installed new version of ElasticSearch and the problem was when you try to connect to clean ElasticSearch instance. If you are using same instance as before the update to 2.0.0 it would work normally.

Ah, but I wasn't using the same inatance. I installed version 2.0.0 of PowerSearch after having completely uninstalled ElasticSearch, including a registry clean. So version 2.0.0 of PowerSearch was connecting to a clean ElasticSearch, with no problems or issues at all. I am now hesitant to update PowerSearch since everything is working just fine as is for me.

[mapozyan]

Originally Posted by Uncle Robin

Ah, but I wasn't using the same inatance. I installed version 2.0.0 of PowerSearch after having completely uninstalled ElasticSearch, including a registry clean. So version 2.0.0 of PowerSearch was connecting to a clean ElasticSearch, with no problems or issues at all. I am now hesitant to update PowerSearch since everything is working just fine as is for me.

There might have been some working scenarios like if you did "reindex all" once you reinstalled all the stuff and before doing any search?