How to fix the "No alive nodes found in your cluster" error?
The "No alive nodes found in your cluster" error in Magento 2 typically occurs when Magento is unable to connect to the Elasticsearch service. This issue can arise from various factors such as Elasticsearch not running, network issues, incorrect configuration settings, or version compatibility issues between Magento and Elasticsearch. Here’s how to troubleshoot and fix this error:
1. Verify Elasticsearch Service Status
First, ensure that the Elasticsearch service is up and running. Use the following command to check the status:
sudo systemctl status elasticsearchIf Elasticsearch is not active, you may consider restarting it with:
sudo systemctl restart elasticsearchImportant Notice: Be cautious when running the sudo systemctl restart elasticsearch command on a live Magento 2 instance. Restarting Elasticsearch can lead to temporary search functionality downtime and might affect the overall performance of your store during peak times. It is recommended to perform such actions during off-peak hours or schedule maintenance to minimize disruption.
2. Confirm Elasticsearch Configuration in Magento
Navigate to Stores > Settings > Configuration > Amasty Extensions > Elastic Search in the Admin Panel and check that the connection is successful:
3. Test Connectivity and Verify Elasticsearch Version
Ensure Magento can reach Elasticsearch by running a curl command from the Magento server:
curl -XGET localhost:9200Replace localhost with the actual IP or hostname and 9200 with the port configured in Magento. This command should also return the version of Elasticsearch, which must be compatible with your version of Magento as specified in Magento's official documentation.
4. Check Magento Logs
Look into the Magento logs for any additional information regarding the connection issue. The logs can provide clues as to what might be going wrong. Check var/log and var/report directories within your Magento installation.
5. Ensure Network Accessibility
If Elasticsearch is hosted on a different server, ensure that the network connection between Magento and Elasticsearch is not blocked by firewalls or network ACLs.
6. Reindex Magento Indexers
After ensuring that Elasticsearch is running and properly configured, reindex the Magento indexers:
bin/magento indexer:reindex
By following these steps, you should be able to diagnose and resolve the "No alive nodes found in your cluster" error in Magento 2.
Related Articles
How to fix the Magento 2.4.5 Layered Navigation showing incorrect results issue?
After upgrading Magento to version 2.4.5 you can see the error: TypeError: Magento\Elasticsearch\Model\ResourceModel\Fulltext\Collection\SearchResultApplier::categoryProductByCustomSortOrder(): Argument #1 ($categoryId) must be of type int, array ...Generating a feed returns an error "Something went wrong: SQLSTATE[42S02]: Base table or view not found: 1146 Table '****inventory_stock_1' does not exist". How to fix this issue?
This error occurs when the inventory module is enabled, yet the inventory is not used. The issue can be resolved by adjusting the InventoryResolver.php file that is located either in the app/code/Amasty/Feed/Model/ or vendor/amasty/feed/Model/ ...The map isn't loading and there's a "Something went wrong" error, what should I check?
You might come across the following error on the Store Locator page: If you see it, open dev tools in your browser and check in the console if the following error is present: If you don't see any errors or if there's another error, please, submit a ...How to fix the "Unable to apply data patch Amasty\ShopbyBase\Setup\Patch\Data\AnchorRootCategories..." error?
According to the Shop by Brand code base, the extension checks the root categories on the Magento instance and makes them anchored. Due to some instance-specific factors, the process may fail resulting in the following error while running the bin ...Test connection fails with error "Unable to open SFTP connection as...", what might be the issue?
This error message appears as a result of an unsuccessful test connection. First thing is to double-check the credentials from the FTP settings tab. There's a chance that one of these values was entered with a typo, either the password or user name ...
Announcements
⚡ Have you enlarged the functionality of the Amasty extension with your own code? Share your improvements with us!
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket