# Cannot start Elasticsearch after upgrade to 2.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 30, 2015, 10:43am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359 "2015-10-30T10:43:30Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [October 30, 2015, 10:43am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/1 "2015-10-30T10:43:30Z")
I did a upgrade from 1.7.3 to 2.0 via apt-get and after this I cannot start it via init.d script. [2015-10-30 11:37:36,442][INFO][bootstrap] es.default.config is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed. When I check the init.d script it seems correct and the elasticsearch.yml is present in /etc/elasticsearch. ---
**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\ **Post date:** [October 30, 2015, 10:55am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/2 "2015-10-30T10:55:52Z")
Could it be that you have the same issues like here: > ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [October 30, 2015, 11:09am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/3 "2015-10-30T11:09:30Z")
I haven't installed Marvel. I checked and found some difference between [https://github.com/elastic/elasticsearch/blob/e95af69fb71d67c3fb2a2806da24214dc4805140/distribution/deb/src/main/packaging/init.d/elasticsearch](https://github.com/elastic/elasticsearch/blob/e95af69fb71d67c3fb2a2806da24214dc4805140/distribution/deb/src/main/packaging/init.d/elasticsearch) and my local file, however if I replace mine with that one I get "Bad substitution" error ---
**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\ **Post date:** [October 30, 2015, 11:17am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/4 "2015-10-30T11:17:06Z")
> [@zappe](#): > > I haven't installed Marvel. Yeah - the title of the issue is misleading. I meant the answer given here > > > Hi > > I've got an odd issue, I'm running a vanilla install on Elasticsearch 2.0 pu…lled from the deb repository, it start after the initial installation, but then I installed Marvel and now seeing the following > > \[2015-10-28 23:11:13,025\]\[INFO \]\[bootstrap \] es.default.config is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed. > > The only config file I have for Elasticsearch is /etc/elasticsearch/elasticsearch.yml, I've also tried uninstall Marvel and still seeing the same issue. > > Cheers might actually be related to your problem as well. > [@zappe](#): > > I checked and found some difference What exactly was the difference? Isabel ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [October 30, 2015, 11:25am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/5 "2015-10-30T11:25:04Z")
> [@mainec](#): > > Yeah - the title of the issue is misleading. I meant the answer given here I've tried to do a search for es.default.config in /etc/ but didn't find anything. > [@mainec](#): > > What exactly was the difference? See [DiffNow](https://www.diffnow.com/?report=0wh98). Mine is to the left. ---
**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\ **Post date:** [October 30, 2015, 11:26am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/6 "2015-10-30T11:26:47Z")
> [@zappe](#): > > Mine is to the left. At least line 100 is what's giving you the parsing error. ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [October 30, 2015, 11:32am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/7 "2015-10-30T11:32:35Z")
> [@mainec](#): > > At least line 100 is what's giving you the parsing error. On the one from repository? ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [November 2, 2015, 8:21am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/8 "2015-11-02T08:21:11Z")
Anyone else have any suggestions? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 2, 2015, 8:37am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/9 "2015-11-02T08:37:57Z")
@tlrx gave a great answer there: [https://github.com/elastic/elasticsearch/issues/14347#issuecomment-152946882](https://github.com/elastic/elasticsearch/issues/14347#issuecomment-152946882) ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [November 2, 2015, 9:49am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/10 "2015-11-02T09:49:16Z")
> [@dadoonet](#): > > @tlrx gave a great answer there: [Elasticsearch 2.0 fails to start after install Marvel 2.0 · Issue #14347 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/14347#issuecomment-152946882) But I installed it via a packet manager, so as far as I understand I shouldn't start it that way? Anyway, if I try I get errors about logging. ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [November 5, 2015, 8:12am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/11 "2015-11-05T08:12:40Z")
Anyone? ---
**Author:** ![zappe](https://avatars.discourse-cdn.com/v4/letter/z/439d5e/32.png) [@zappe](https://discuss.elastic.co/u/zappe)\ **Post date:** [November 20, 2015, 11:57am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/12 "2015-11-20T11:57:25Z")
Bump. ---
**Author:** ![justnj](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@justnj](https://discuss.elastic.co/u/justnj)\ **Post date:** [November 26, 2015, 11:57am UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/13 "2015-11-26T11:57:12Z")
Hi Did you run the migration check before running the upgrade of ES from 1.7 to 2.0 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:35pm UTC](https://discuss.elastic.co/t/cannot-start-elasticsearch-after-upgrade-to-2-0/33359/14 "2017-07-05T23:35:39Z")