submit-feedback
legacy-knowledge-base
Publicado Jul. 25, 0002

Liferay DXP does not start after configuring Elasticsearch connector to Remote Operation Mode

written-by

Matheus Monteiro

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

legacy-article

learn-legacy-article-disclaimer-text

Issue

  • After configuring Liferay Elasticsearch connector in Remote operation mode and restarting the  portal, if communication between Liferay and Elasticsearch fails, the portal becomes inaccessible and the error below will be shown in the log:
None of the configured nodes are available: [{#transport#-1}{q-38f4_ZQHatS-xk6SdJ1w}{IP_ADDRESS}{IP_ADDRESS:PORT}]]

Environment

  • DXP 7.1
  • Elasticsearch 6.x

Resolution

  • Create (or change if it already exists) the file: 
    [Liferay_Home]/osgi/configs/com.liferay.portal.search.elasticsearch6.configuration.ElasticsearchConfiguration.config
  • Change the IP address/port using the property transportAdresses="IP.of.elasticsearch.node:Port"
  • Save the file and restart Liferay DXP.

If you can not have a running and accessible Elasticsearch address and need to access the portal anyway, you can add/change the property:

operationMode="EMBEDDED"

It is important to remember that we do not support the embedded mode of Elasticsearch in Production environments. 

Additional Information

  • For more information about Liferay Elasticsearch connector, please refer to our official page.
did-this-article-resolve-your-issue
legacy-knowledge-base
did-this-article-resolve-your-issue