If I do the exact same thing, with that one change, I get 502 Bad Gateway
errors from nginx. If I connect via SSH to one of the instances, I notice
elasticsearch is not even running and starting it manually doesn't seem to
work.
[ec2-user@search1 run]$ sudo service elasticsearch status -v
elasticsearch not running
[ec2-user@search1 run]$ sudo service elasticsearch start
PID file found in /usr/local/var/run/search1_localdomain.pid, elasticsearch
already running?
Starting elasticsearch...
[ec2-user@search1 run]$ sudo service elasticsearch status -v
elasticsearch not running
Should there be log files somewhere I can find? Any ideas how to diagnose
this?
Just as a follow up, the issue I was running in to was related to the the
ES service failing to start due to an incompatible plugin. I had to change
the version of the AWS plugin https://github.com/elasticsearch/elasticsearch-cloud-aws in
/attributes/aws.rb from1.14.0 to 2.1.1
On Wednesday, July 16, 2014 11:33:54 PM UTC+3, Ryan V wrote:
If I do the exact same thing, with that one change, I get 502 Bad Gateway
errors from nginx. If I connect via SSH to one of the instances, I notice
elasticsearch is not even running and starting it manually doesn't seem to
work.
[ec2-user@search1 run]$ sudo service elasticsearch status -v
elasticsearch not running
[ec2-user@search1 run]$ sudo service elasticsearch start
PID file found in /usr/local/var/run/search1_localdomain.pid,
elasticsearch already running?
Starting elasticsearch...
[ec2-user@search1 run]$ sudo service elasticsearch status -v
elasticsearch not running
Should there be log files somewhere I can find? Any ideas how to diagnose
this?
What if you just change the Elasticsearch version in your setup
(attributes, role overrides, etc)? There is no patch/commit needed to
install 1.x versions with the cookbook. (There are just special cases where
overriding attributes doesn't work as expected.)
Is there anything printed to the Elasticsearch log? Are you able to start
Elasticsearch directly by executing the bin/elasticsearch script?
Karel
On Wednesday, July 16, 2014 10:33:54 PM UTC+2, Ryan V wrote:
If I do the exact same thing, with that one change, I get 502 Bad Gateway
errors from nginx. If I connect via SSH to one of the instances, I notice
elasticsearch is not even running and starting it manually doesn't seem to
work.
[ec2-user@search1 run]$ sudo service elasticsearch status -v
elasticsearch not running
[ec2-user@search1 run]$ sudo service elasticsearch start
PID file found in /usr/local/var/run/search1_localdomain.pid,
elasticsearch already running?
Starting elasticsearch...
[ec2-user@search1 run]$ sudo service elasticsearch status -v
elasticsearch not running
Should there be log files somewhere I can find? Any ideas how to diagnose
this?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.