Closed jerrac closed 8 years ago
not solved on Elasticsearch 5.4.1 deb package (Ubuntu 14.04.2 LTS)
After upgrade to 5.5.0 i have this problem.
What helped me : Uninstall openjdk9 install openjdk8
Symlink config : ln -s /etc/elasticsearch /usr/share/elasticsearch/config
Correcting rights :
chmod g+rwx /usr/share/elasticsearch/config/elasticsearch.yml /usr/share/elasticsearch/config/logging.yml
chmod g+rwx /usr/share/elasticsearch/config/elasticsearch.yml /usr/share/elasticsearch/config/elasticsearch.yml
I had same issue today. When I did upgrade ubuntu 14.04 to 16.04, installed elasticsearch with 'apt-get install elasticsearch' and 'systemctl start elasticsearch' has no problem, but it was old version, so I had to update with 5.1.1. 'dpgk -i elasticsearch-5.5.1.deb' then, failed to start service. (exactly same issue. no configf file even start as a service)
So, remove completely with below commands. 'apt remove --purge elasticsearch' 'apt autoremove' 'apt-get install elasticsearch' -> then faced to 'stateoverride' problem. . to solve it, 'vi /var/lib/dpkg/stateoverride', remove lines which include 'elasticsearch'
'dpgk -i elasticsearch-5.5.1.deb' 'systemctl start elasticsearch' no problem.
It is really stupid. Today, this issue is still exists with elasticsearch-5.5.2.
@kelp404 @seunghan-go can you please provide the playbook you are using for which this issue arises.
@seunghan-go your post suggests you aren't even using ansible - this repo is for the ansible role for ES NOT generic issues with installing ES.
@olendorf cp /etc/elasticsearch/elasticsearch.yml /user/share/elasticshare/config is giving error it should be cp /etc/elasticsearch/elasticsearch.yml /usr/share/elasticsearch/config
I think this may be caused by an old /etc/elasticsearch/elasticsearch.yml
where no entry for path.logs
exists. On a fresh deb install it should be path.logs: /var/log/elasticsearch
. With that set, this error should not occur.
I had the similar problem with elasticsearch 5.6.0. No logs were getting generated and while running it using init.d scrips it was showing no file found /usr/share/elasticsearch/config
. So, I did two things:-
ln -s /etc/elasticsearch /usr/share/elasticsearch/config
and after this the following commands
sudo chown -R elasticsearch:elasticsearch /var/lib/elasticsearch
sudo chown -R elasticsearch:elasticsearch /var/run/elasticsearch
sudo chown -R elasticsearch:elasticsearch /etc/elasticsearch
I had the same issue, just because I did not start the binary with sudo.
@pranvendra Thanks, this works like a charm. Nice solution.
I just did an initial test install with this role. I configured three nodes and ran the play. When I tried checking the health of the cluster, it became apparent that elasticsearch was not started.
So I tried starting it manually, and I got this:
Here are the ansible vars, just replace node1 with node2 or node3 to get the other nodes config:
Did I miss some required var?
I did try
/etc/init.d/node1_elasticsearch start
and it did not work, nor did it output any errors. JustStarting ... [OK]
./var/logs/elasticsearch
is empty so I can't figure anything out from there.So, what obvious step am I missing?
Should this kind of question be posted on discuss.elastic.co somewhere instead of here? If so, what forum?