# Can't Start ES 5.2 After Upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [February 2, 2017, 6:45pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737 "2017-02-02T18:45:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![krmathieu](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@krmathieu](https://discuss.elastic.co/u/krmathieu)\ **Post date:** [February 2, 2017, 6:45pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/1 "2017-02-02T18:45:51Z")
I just upgraded a VM from 5.0 to 5.2 and now can't start the service. I see this error at the command line after running "service elasticsearch start": "If the number of processes is expected to increase from one, then you should configure the number of GC threads appropriately using -XX:ParallelGCThreads=n" I had previously had similar issues when I went from 2.4 to 5.0 as detailed in this post: > [@Cant Start Fresh Install of ES 5.0](https://discuss.elastic.co/t/cant-start-fresh-install-of-es-5-0/64360): > > I spun up a new VirtualBox VM and installed ES 5.0 from yum and when I try to start it I get an error stating: "OpenJDK Server VM Warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using XX:ParallelGCThreads=N The service then appears to start after the warning but when I enter "service elasticsearch status" to see if it is actually running, I see "elasticsearch dead but subsys locked". I then remove… What do I need to address this particular issue? Do I need to make an update to the /etc/elasticsearch/jvm.options file? If so, what changes should be made? Any help would be appreciated. Thanks. Kevin ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 2, 2017, 7:49pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/2 "2017-02-02T19:49:17Z")
Is that what is in the ES log? What OS? What JVM? ---
**Author:** ![krmathieu](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@krmathieu](https://discuss.elastic.co/u/krmathieu)\ **Post date:** [February 2, 2017, 8:16pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/3 "2017-02-02T20:16:38Z")
No, I am seeing this right on the command line when trying to start the service. I don't see anything in the log files. I am running Centos 6.8 and Java 1.8.0\_111. Thoughts on how to fix this??? Thanks. ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [February 2, 2017, 8:40pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/4 "2017-02-02T20:40:00Z")
See > ---
**Author:** ![krmathieu](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@krmathieu](https://discuss.elastic.co/u/krmathieu)\ **Post date:** [February 2, 2017, 9:18pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/5 "2017-02-02T21:18:52Z")
Thanks. I am going to add -XX:-AssumeMP to the jvm.options file. Do you know if there is any specific location I need to add it??? ---
**Author:** ![krmathieu](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@krmathieu](https://discuss.elastic.co/u/krmathieu)\ **Post date:** [February 2, 2017, 10:19pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/6 "2017-02-02T22:19:49Z")
Ok, so I added -XX:-AssumeMP to the jvm.options file and it got rid of my error at the top of this chain. However, now ES 5.2 appears to start when I run "service elasticsearch start" as root from the command line, but when I check the status of the service I see: elasticsearch dead but pid file exists I tried running the following command and it does not return anything: netstat -ntlp | grep 9200 I also looked for the relevant file in /var/run/elasticsearch and it is not there. How do I fix this particular issue??? Kevin ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 2, 2017, 10:20pm UTC](https://discuss.elastic.co/t/cant-start-es-5-2-after-upgrade/73737/7 "2017-03-02T22:20:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.