# Can't get Chef deployed ElasticSearch service to start **URL:** \ **Category:** Elasticsearch\ **Created:** [July 16, 2014, 8:33pm UTC](https://discuss.elastic.co/t/cant-get-chef-deployed-elasticsearch-service-to-start/18710 "2014-07-16T20:33:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Ryan\_V](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_v/32/1376_2.png) [@Ryan\_V](https://discuss.elastic.co/u/Ryan_V)\ **Post date:** [July 16, 2014, 8:33pm UTC](https://discuss.elastic.co/t/cant-get-chef-deployed-elasticsearch-service-to-start/18710/1 "2014-07-16T20:33:53Z")
I posted this over on Github, but thought I might get more eyeballs here. I'm deploying an ES cluster to EC2 via OpsWorks using the method described here: [http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks](http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks) Out of the box, it all works perfectly, but my client requires ES 1.0+ so I've updated the ES version in the cookbook from 0.90.12 to 1.1.1 by using the commit here: [https://github.com/elasticsearch/cookbook-elasticsearch/pull/213](https://github.com/elasticsearch/cookbook-elasticsearch/pull/213) 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? Thanks! -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7d07c010-abd4-4ce2-a070-3a29537ba8b0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7d07c010-abd4-4ce2-a070-3a29537ba8b0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![eiTan\_LaVi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eitan_lavi/32/1088_2.png) [@eiTan\_LaVi](https://discuss.elastic.co/u/eiTan_LaVi)\ **Post date:** [November 26, 2014, 9:56am UTC](https://discuss.elastic.co/t/cant-get-chef-deployed-elasticsearch-service-to-start/18710/2 "2014-11-26T09:56:15Z")
see if this helps: [Upgrade to Elasticsearch 1.1.1 by n1koo · Pull Request #213 · sous-chefs/elasticsearch · GitHub](https://github.com/elasticsearch/cookbook-elasticsearch/pull/213) \*ryanvanderpol [https://github.com/ryanvanderpol](https://github.com/ryanvanderpol) \*commented on 17 Jul [https://github.com/elasticsearch/cookbook-elasticsearch/pull/213#issuecomment-49336142](https://github.com/elasticsearch/cookbook-elasticsearch/pull/213#issuecomment-49336142) 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](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: > I posted this over on Github, but thought I might get more eyeballs here. > I'm deploying an ES cluster to EC2 via OpsWorks using the method described > here: > [http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks](http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks) > > Out of the box, it all works perfectly, but my client requires ES 1.0+ so > I've updated the ES version in the cookbook from 0.90.12 to 1.1.1 by using > the commit here: > [Upgrade to Elasticsearch 1.1.1 by n1koo · Pull Request #213 · sous-chefs/elasticsearch · GitHub](https://github.com/elasticsearch/cookbook-elasticsearch/pull/213) > > 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? > > Thanks! -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4bb09e5a-a5b5-4580-a1cf-ae4a7e5aa67e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4bb09e5a-a5b5-4580-a1cf-ae4a7e5aa67e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Karel\_Minarik\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karel_minarik_2/32/1078_2.png) [@Karel\_Minarik\_2](https://discuss.elastic.co/u/Karel_Minarik_2)\ **Post date:** [November 27, 2014, 6:06am UTC](https://discuss.elastic.co/t/cant-get-chef-deployed-elasticsearch-service-to-start/18710/3 "2014-11-27T06:06:53Z")
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: > I posted this over on Github, but thought I might get more eyeballs here. > I'm deploying an ES cluster to EC2 via OpsWorks using the method described > here: > [http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks](http://blogs.aws.amazon.com/application-management/post/Tx3MEVKS0A4G7R5/Deploying-Elasticsearch-with-OpsWorks) > > Out of the box, it all works perfectly, but my client requires ES 1.0+ so > I've updated the ES version in the cookbook from 0.90.12 to 1.1.1 by using > the commit here: > [Upgrade to Elasticsearch 1.1.1 by n1koo · Pull Request #213 · sous-chefs/elasticsearch · GitHub](https://github.com/elasticsearch/cookbook-elasticsearch/pull/213) > > 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? > > Thanks! -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/85569672-cde5-4254-98df-acb28d2876d5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/85569672-cde5-4254-98df-acb28d2876d5%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:47am UTC](https://discuss.elastic.co/t/cant-get-chef-deployed-elasticsearch-service-to-start/18710/4 "2017-07-06T00:47:22Z")