movieseals

Well, that is the source of all my problems. After speaking with tech support at my host, I finally learned that previous versions of ES, at least the free ones, are not secured. The server will not accept anything below 6.8 because there is no security in the older versions unless it is the paid versions. So it is impossible to make it work with the module at this point. For the record, it would have been nice to know which versions of ES are supported in the documentation - it would have saved me a week of stumbling in the dark...

I managed to reinstall the module and it seems to work, although it still refuses to connect. The only version of elasticsearch I can manage to install on the server that actually connects properly on port 9200 is 6.8.0. No other version will work: neither before or after (7.1.1). I tried to delete the vendor folder, set a composer.json with 6.8.0, run composer update then composer install, and I get this error: Your requirements could not be resolved to an installable set of packages. Problem 1 - The requested package elasticsearch/elasticsearch 6.8.0 exists as elasticsearch/elasticsearch[0.4.x-dev, 1.0.x-dev, 2.0.x-dev, 5.0.x-dev,6.0.x-dev, 6.5.x-dev, 6.7.x-dev, 7.0.x-dev, dev-loekvangool-patch-1, dev-master, dev-sarwarbhuiyan-patch-1, dev-sarwarbhuiyan-patch-2, dev-sarwarbhuiyan-patch-2-1, dev-travis, v0.4.0, v0.4.1, v0.4.2, v0.4.3, v0.4.4, v0.4.5, v1.0, v1.0.1, v1.0.2, v1.1.0, v1.2.0, v1.2.1, v1.2.2, v1.3.0, v1.3.1, v1.3.2, v1.3.3, v1.3.4, v1.4.0, v1.4.1, v2.0.0, v2.0.0-beta1, v2.0.0-beta2, v2.0.0-beta3, v2.0.0-beta4, v2.0.0-beta5, v2.0.1, v2.0.2, v2.0.3, v2.1.0, v2.1.1, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.2.0, v2.2.1, v2.2.2, v2.2.3, v2.3.0, v2.3.1, v2.3.2, v2.4.0, v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.3.0, v5.3.1, v5.3.2, v5.4.0, v6.0.0, v6.0.0-beta1, v6.0.1, v6.1.0, v6.5.0, v6.7.0, v6.7.1, v7.0.0, v7.0.1] but these arerejected by your constraint. So clearly the 6.8 package is not there... Like stated, I tried various other versions but they will not connect on port 9200 server side. As for the elasticsearch module, it used to see the elasticsearch version, now all its states is: Elasticsearch version:Unknown It still refused to connect to anything, regardless, claiming: Unable to connect with the Elasticsearch server. Has the connection been configured? Yet, if I run curl -X GET "localhost:9200/", I get the following: { "name" : "2ZwYVKY", "cluster_name" : "elasticsearch", "cluster_uuid" : "OTZDSTDgQieIL1C7AL4rZw", "version" : { "number" : "6.8.0", "build_flavor" : "default", "build_type" : "rpm", "build_hash" : "65b6179", "build_date" : "2019-05-15T20:06:13.172855Z", "build_snapshot" : false, "lucene_version" : "7.7.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" } Which is apparently what needs to be returned when the connection works... 😞 This has been an incredibly frustrating ordeal. In the meantime I found this: https://webkul.com/blog/prestashop-elastic-search/ It seems a little more well thought out and appears to be compatible with PS 1.6 - which most of the time works with TB. However, my level of success with developers being willing to fix things for TB versions has been pretty low so I am not sure if I want to risk $200 plus on a module considering the struggles I have encountered so far with elasticsearch. So currently looking for alternatives to the default search engine that actually works with TB without all the elasticsearch headaches. Any suggestions?

I tried for many days now. I give up. It is not normal that a plugin has to have anyone jump through so many hoops without any clear path. I tried versions 5, 6 and 7 (I tried the composer.json trick another poster mentionned in here), I tried several things for days. Nothing works. They do say it is a beta but it does not work and there are no clear indications as to why in the errors logs. Is there any other alternatives to the native search engine that actually works with TB?

I reinstalled 6.8 because that was the only one that had some sign of life in that stupid module. 5 will not connect at all, even after wiping everything. This is clearly not a workable solution. I tried about half a dozen times. It just won't do anything with 5. Elasticsearch, as promising as it sounds, is clearly not ready for primetime in Thirtybees!

No, the port is clean. Nothing else on it. I went on github to get the latest version of the module. Things got worst. Now I get an error message: [PrestaShop] Fatal error in module file :/home/zbookstore/public_html/modules/elasticsearch/elasticsearch.php:require_once(): Failed opening required '/home/zbookstore/public_html/modules/elasticsearch/vendor/autoload.php' (include_path='/home/zbookstore/public_html/vendor/pear/archive_tar:/home/zbookstore/public_html/vendor/pear/console_getopt:/home/zbookstore/public_html/vendor/pear/pear-core-minimal/src:/home/zbookstore/public_html/vendor/pear/pear_exception:.:/opt/cpanel/ea-php71/root/usr/share/pear') I am going to have to look at something else - this thing is buggy as hell and clearly cannot do the job! Over 12 hours on it and still not even close! It makes no sense that a module be so complicated to setup!!!

I truly appreciate everybody's help. Just been trying to figure this out for over 9 hours... I am able to connect with Redis and Memcache to the same localhost, granted through different ports, so that cannot be the issue. I know the port for elastic search is open, the server says so.

I tried with or without https (just in case and for good measure!): http://127.0.0.1:9200 https://127.0.0.1:9200 https://localhost:9200 http://localhost:9200 Regardless of the combinations, I get a connection error as if nothing has been configured at all! I tried with or without Ajax proxy. I really cannot tell what I am doing wrong!

The CURL works in terminal - I get a confirmation that elasticsearch is running and ready to go. I finally got the module to give me an error after hours of trying stuff: Error! Unable to connect with the Elasticsearch server. Has the connection been configured? The weird part is, from the server side, everything appears to be fine! [root@odedi54851 ~]# sudo /etc/init.d/elasticsearch status ● elasticsearch.service - Elasticsearch Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2019-06-09 16:37:50 EDT; 9h ago Docs: http://www.elastic.co Main PID: 735517 (java) CGroup: /system.slice/elasticsearch.service ├─735517 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.netw... └─735616 /usr/share/elasticsearch/modules/x-pack-ml/platform/linux-x86_64/bin/controller And the CURL command gets me this: Jun 09 16:37:50 odedi54851.mywhc.ca systemd[1]: Started Elasticsearch. [root@odedi54851 ~]# curl -XGET http://127.0.0.1:9200 { "name" : "2ZwYVKY", "cluster_name" : "elasticsearch", "cluster_uuid" : "OTZDSTDgQieIL1C7AL4rZw", "version" : { "number" : "6.8.0", "build_flavor" : "default", "build_type" : "rpm", "build_hash" : "65b6179", "build_date" : "2019-05-15T20:06:13.172855Z", "build_snapshot" : false, "lucene_version" : "7.7.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" So everything is running fine on the server!

I have reset the module. I have disabled all caches. I put the site in debug mode and get nothing. My feeling is that the connection is just not happening somehow.

I wish I was getting to 33%. 🙂 I have disabled all the caches, will try again.

The argument makes sense but the code at line 377 of my version does not seem to accommodate that. I did try, same results. This fix is from 2018. Perhaps more was added since?

Read that, followed it to the letter, everything seems to work except the actual indexing... The frustrating part is that there is no error message, no way of knowing if anything is happening. It just spins and spins and spins. Nothing happens in the database. Yet, on the server side, everything appears to be working fine.

The logs only indicated the failures (until around 16:30 when I reinstalled 6): -- Logs begin at Fri 2019-06-07 17:40:08 EDT, end at Sun 2019-06-09 16:45:10 EDT. -- Jun 09 10:39:34 odedi54851.mywhc.ca systemd[1]: Started Elasticsearch. Jun 09 15:42:15 odedi54851.mywhc.ca systemd[1]: Stopping Elasticsearch... Jun 09 15:42:15 odedi54851.mywhc.ca systemd[1]: Stopped Elasticsearch. Jun 09 15:43:57 odedi54851.mywhc.ca systemd[1]: Starting Elasticsearch... Jun 09 15:43:57 odedi54851.mywhc.ca systemd[1]: Started Elasticsearch. Jun 09 15:44:01 odedi54851.mywhc.ca systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE Jun 09 15:44:01 odedi54851.mywhc.ca systemd[1]: Unit elasticsearch.service entered failed state. Jun 09 15:44:01 odedi54851.mywhc.ca systemd[1]: elasticsearch.service failed. Jun 09 16:37:50 odedi54851.mywhc.ca systemd[1]: Started Elasticsearch.

With version 6 I would get this with that command: [root@odedi54851 ~]# curl -X GET "localhost:9200/" { "name" : "2ZwYVKY", "cluster_name" : "elasticsearch", "cluster_uuid" : "OTZDSTDgQieIL1C7AL4rZw", "version" : { "number" : "6.8.0", "build_flavor" : "default", "build_type" : "rpm", "build_hash" : "65b6179", "build_date" : "2019-05-15T20:06:13.172855Z", "build_snapshot" : false, "lucene_version" : "7.7.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" } With version 5, I get a cannot connect. However, everything is fine in the firewall. I just reinstalled 6 to see if anything had changed, and lo and behold, it still works and I can connect.

I saw that. It is still failing.

I installed Elastic Search 5. I get a Failed connect to 127.0.0.1:9200; Connection refused, which was not a problem with version 6. I checked the firewall and the port is authorized both ways.

I will uninstall Elastic Search 6 and try installing 5.

Yes, I did tune MariaDB with mysqltuner/ Server is unmanaged, with some limited support. In cpanel, I have changed to MPM_Event.

How big is your tb_product_lang table? 58.3 MB Did you have a look at the Preferences->Search entry in your backoffice. Maybe you can set some weights to zero... Will have a look

There is an extensive blacklist there, wich I guess should not be indexed in the tb_search_index table.

OS: CentOS Ram: 30 GB Cpu: Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz (8 processors) Cpanel PHP version: 7.1 MariaDB 10.3.15, InnoDB, all rows Compressed Thanks for the help!

I tried to change the server settings to 127.0.0.1:9200 as it does correspond to my localhost and it seemed to have worked for someone here in the forum. No dice.

curl is active on the server, and all the java dependencies, everything is up to the latest version.

Here is the situation with the database, despite almost an hour of "indexing"...

OK. I installed Elastic Search 6.8.0 on my server. Everything seems to work normally, access via port 9200, which i enabled in the firewall. From the terminal, everything connects and Elastic Search is active and working. I now have installed the Elastic Search module for TB. It does see the version of Elastic Search. I have set the server to connect as follows:https://localhost:9200 I setup and followed all the other parameters in the instructions. Everything seems to work except two things: My theme requires search to be in the hook displaynav instead of displaytop - I was thinking of adding the following after the displayTop instructions: public function hookDisplayNav() { return $this->hookDisplayTop(); } Second thing, more worrisome, nothing seems to be indexing. It spins and spins and spins but nothing happens. Index in Database remains empty. See attachment.