Thread Details
  • Replies 4 replies
  • Subscribers 354 subscribers
  • Views 1718 views
  • Users 0 members are here
Forum Actions
Related

Sugar 13 Enterprise On-site with Elastic Search 8.4.3 (Windows)

Alex Bryan

Hi.

We have resently upgraded our Sugar test environment to version 13. We have also attempted to install and run the Windows service for ES 8.4.3 (Elastic Search) but are unable to test the connection via Sugar Administration and perform the required Re-index after installation.

Our current PHP version is 8.0.28.

I have followed the usual process as per our previous upgrades but somehow this verison of ES runs differently to others. We are running the single node on our hosting server and It looks like the ES service consumes memory through the OpenJDK Platform binary which is different to our prod instance running ES 7.16.3 via the Commons Daemon Service Runner:



The Sugar logs are not helpful and I have followed the two links below during installation. Any assistance or suggestions would be appreciated for those running the same environment. 

Thanks

- Alex

Parents
  • Sugar Employee Badge

    Hi ,

    I noticed something similar when I was creating our Docker container for v13. My issue was that ES data folder was pre-existent with 7.16.3 and was somehow upgraded by the new version or has overridden some config file that is now requesting a username/password, causing my install to fail (connection failed/denied).

    I would say you create a new data folder (or at install, point to an empty data folder) and let Sugar create it.. it did the trick for me.

    rafa

    SugarCRM | Principal Developer Advocate

Reply
  • Sugar Employee Badge

    Hi ,

    I noticed something similar when I was creating our Docker container for v13. My issue was that ES data folder was pre-existent with 7.16.3 and was somehow upgraded by the new version or has overridden some config file that is now requesting a username/password, causing my install to fail (connection failed/denied).

    I would say you create a new data folder (or at install, point to an empty data folder) and let Sugar create it.. it did the trick for me.

    rafa

    SugarCRM | Principal Developer Advocate

Children
  • in reply to Rafael Fernandes

    Hi Rafael,

    Thank you for your reply. I followed your suggestion however it did not resolve the issue and retuned the same error when testing the ES connection from the Search settings in Sugar Administration.

    I did however identify that security is auto enabled by default with this ES which may have aligned with your suggestion. I then added the following line into the elasticsearch.yml file and my connection was successful:

    xpack.security.enabled: false

    I am not sure if this was enabled in the past . I wonder if there is a recommended security setting for ES and Onsite Sugar instances.

    - Alex