Liferay Enterprise Search
- [LES]: How to install and run the Elastic Support Diagnostics Troubleshooting Utility
- [LES] About Elasticsearch License expiration
- [LES] Elasticsearch Virtual Machine Considerations
- [LES] Getting Started with Liferay Enterprise Search
- [LES] How to use a load balancer with Elasticsearch?
- [LES] Installing the Learning-to-Rank plugin on Elasticsearch fails with "IllegalStateException: ltr requires Java 14"
- [LES] What is the recommended Java heap size for Elasticsearch?
- [LES] Which node types are charged as part of the Liferay Enterprise Search Subscription
- Easily customize Liferay's search behavior with Blueprints
- Elasticsearch 7.17 End of Life (EOL) Timeline and Liferay DXP Elasticsearch Compatibility Update & FAQ
- Liferay Enterprise Search Experiences (Blueprints) 1.1.0 for DXP 7.3 Release Highlights & Upgrade Instructions
[LES]: How to install and run the Elastic Support Diagnostics Troubleshooting Utility
This articles explains how to acquire and run the support diagnostics utility for your Elasticsearch cluster.
Overview
When submitting a ticket for Liferay Enterprise Search (LES) you will often be asked to provide a full set of diagnostics from the running Elasticsearch cluster. While all the commands to obtain this information can be run manually, it will be much simpler and easier to run the diagnostic utility provided by Elastic. It has no dependencies other than a JRE or JDK version 1.7 or greater. The diagnostic utility works against all supported versions of Elasticsearch (and from Logstash 5.0+).
Diagnostic utility releases, as well as Instructions for installing and running the utility can be found in the public Github repository. Please consult the README file on the landing page.
https://github.com/elastic/support-diagnostics
Download
https://github.com/elastic/support-diagnostics/releases/latest
Usage
Please consult the README file on the landing page.
Examples
Getting help
./diagnostics.sh --help
Using X-Pack Authentication:
./diagnostics.sh --host 192.168.1.10 -u <username> -p
Using X-Pack Authentication With SSL:
./diagnostics.sh --host localhost --port 9200 --noVerify -u <username> -p --sslSpecifying an output directory:
./diagnostics.sh --host 192.168.1.10 -o <full path to output directory>