Renegade
Well-known member
Every morning, between 5AM to 9AM, the elasticsearch service stops. I could see only the following in the syslog regarding elastic search.
My servers config is as below and I have over 2M posts.
I have noticed that if I try to start the elasticsearch service manually then it fails to start with 'start operation timed out' error. However if I reboot the server, then the service starts fine. I am assuming that this is because the server has more free RAM when it reboots as opposed to a server which has been running for over 20 hours.
hhjjp-172-26-6-79:/var/log# grep -i elasticsearch syslog
Oct 10 11:50:55 ip-172-26-6-79 systemd[1]: Starting Elasticsearch...
Oct 10 11:51:37 ip-172-26-6-79 systemd[1]: Started Elasticsearch.
Oct 11 00:38:24 ip-172-26-6-79 systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
Oct 11 00:38:24 ip-172-26-6-79 systemd[1]: elasticsearch.service: Unit entered failed state.
Oct 11 00:38:24 ip-172-26-6-79 systemd[1]: elasticsearch.service: Failed with result 'signal'.
My servers config is as below and I have over 2M posts.
2GB RAM, Ubuntu (bitnami LAMP stack)
-Xms512m
-Xmx512m
I have noticed that if I try to start the elasticsearch service manually then it fails to start with 'start operation timed out' error. However if I reboot the server, then the service starts fine. I am assuming that this is because the server has more free RAM when it reboots as opposed to a server which has been running for over 20 hours.