I followed all the instruction you have mentioned here How to install Magento 2.4 and build a web server and everything is working fine but No alive nodes found in your cluster when i test catalog search and check elasticsearh service and its failed but it was active before. I have fixed again and again but the same problem coming up after every 30 minutes. As no alive node found, product are not displaying in category. I need your help to fix the issue.–>
sometime its failed and sometime its work when i restart…if its failed then make changes curl -X GET ‘http://localhost:9200’ and work again but same problem came up
Next time it happens, copy paste the the output from the last command I left. It’ll should give you a hint to what caused it to stop responding. If there isn’t much information provided with that one, then this one should give even more information:
journalctl -u elasticsearch.service -b -e
(You may have to Page Up/Down to locate the most recent log entries)
curl -X GET 'http://localhost:9200'
curl: (7) Failed to connect to localhost port 9200: Connection refused
journalctl -u elasticsearch.service -b -e
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
~
~
-- Logs begin at Fri 2020-10-16 06:21:09 UTC, end at Fri 2020-10-16 10:44:36 UTC. >
-- No entries --
lines 1-2/2 (END)
systemctl status elasticsearch
● elasticsearch.service - Elasticsearch
Loaded: loaded (/lib/systemd/system/elasticsearch.service; enabled; vendor prese>
Active: failed (Result: signal) since Fri 2020-10-16 11:26:14 UTC; 10min ago
Docs: http://www.elastic.co
Process: 36735 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}>
Main PID: 36735 (code=killed, signal=KILL
sudo journalctl -u elasticsearch.service -b -e
Oct 16 11:26:11 ubuntu systemd[1]: Starting Elasticsearch...
Oct 16 11:26:12 ubuntu elasticsearch[36735]: OpenJDK 64-Bit Server VM warning: Option UseC>
Oct 16 11:26:14 ubuntu systemd[1]: elasticsearch.service: Main process exited, code=killed>
Oct 16 11:26:14 ubuntu systemd[1]: elasticsearch.service: Failed with result 'signal'.
Oct 16 11:26:14 ubuntu systemd[1]: Failed to start Elasticsearch.
If you don’t have htop installed, just run the following as superuser:
sudo apt install htop
Running htop
If you wanted to, you could actually monitor the Linux Task Manager and watch your Memory usage completely fill up - And then you’d know the issue or at least rule it out.