Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

No Logs in Elasticsearch

Written By

Liferay Support

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

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

This article documents a known issue with Elasticsearch operating mode when switching from REMOTE to EMBEDDED operation. Any changes in configuration do not take effect unless the elasticsearch module is restarted on the server. Also, when going from default EMBEDDED to REMOTE configurations do not seemingly get used until the elasticsearch module is restarted in gogo shell.

Steps to Reproduce

  1. Start up server with normal configs for Elasticsearch.
  2. Go to System Settings -> Foundation -> Elasticsearch
  3. Configure REMOTE connection and save.

Expected Result: The log file for remote Elasticsearch has evidence of use, reindecing, searching, etc.
Actual Result: No logs exists.

Important Note: Never use EMBEDDED mode in Production.

Resolution

Status: Workaround available

Please subscribe to the article to be notified of the latest updates on fixes and workarounds for this issue. 

  1.  Log in to Gogo shell
  2.  Restart Elasticsearch module

Remote ES log now should have signs of it operating.

Additional Information

See LPS-65459 for more information and the latest status on the issue.

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?