# Can not start Elasticsearch 5.5 service

**URL:** <https://discuss.elastic.co/t/can-not-start-elasticsearch-5-5-service/107921>\
**Category:** Elasticsearch\
**Created:** [November 16, 2017, 11:47am UTC](https://discuss.elastic.co/t/can-not-start-elasticsearch-5-5-service/107921 "2017-11-16T11:47:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jmart](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@Jmart](https://discuss.elastic.co/u/Jmart)\
**Post date:** [November 16, 2017, 11:47am UTC](https://discuss.elastic.co/t/can-not-start-elasticsearch-5-5-service/107921/1 "2017-11-16T11:47:49Z")

</div>

Hello all,

I've recently installed elasticsearch 5.5 on a Windows Server 2012 with 16GB RAM. It has been working for a 3-4 weeks correctly. Yesterday server was restarted and the elasticsearch service can not start. We see this errors:

Service cannot be started. Elastic.ProcessHosts.Process.StartupException: Could not start process within (00:02:00): D:\Program Files\Java\jdk1.8.0\_141\bin\java.exe -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -XX:+HeapDumpOnOutOfMemoryError -Xmx8192m -Xms8192m -Delasticsearch -Des.path.home="D:\Elasticsearch-5.5" -cp "D:\Elasticsearch-5.5\lib\elasticsearch-5.5.0.jar;D:\Elasticsearch-5.5\lib\HdrHistogram-2.1.9.jar;D:\Elasticsearch-5.5\lib\hppc-0.7.1.jar;D:\Elasticsearch-5.5\lib\jackson-core-2.8.6.jar;D:\Elasticsearch-5.5\lib\jackson-dataformat-cbor-2.8.6.jar;D:\Elasticsearch-5.5\lib\jackson-dataformat-smile-2.8.6.jar;D:\Elasticsearch-5....

Application: elasticsearch.exe  
Framework Version: v4.0.30319  
Description: The process was terminated due to an unhandled exception.  
Exception Info: Elastic.ProcessHosts.Process.StartupException  
Stack:  
at Elastic.ProcessHosts.Process.ProcessBase.HandleException(System.Exception)  
at System.Reactive.Observer`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnError(System.Exception) at System.Reactive.Linq.ObservableImpl.AsObservable`1+\_[[System.\_\_Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnError(System.Exception)  
at System.Reactive.AutoDetachObserver`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnErrorCore(System.Exception) at Elastic.ProcessHosts.Process.ObservableProcess+<>c__DisplayClass22_0.<CreateProcessExitSubscription>b__0(System.Reactive.EventPattern`1\<System.Object\>)  
at System.Reactive.AnonymousSafeObserver`1[[System.\_\_Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnNext(System.\_\_Canon)  
at System.EventHandler.Invoke(System.Object, System.EventArgs)  
at System.Diagnostics.Process.RaiseOnExited()  
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)  
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)  
at System.Threading.\_ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(System.Object, Boolean)

Faulting application name: elasticsearch.exe, version: 5.5.0.0, time stamp: 0x5956e851  
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794  
Exception code: 0xe0434352  
Fault offset: 0x00000000000095fc  
Faulting process id: 0xc3c  
Faulting application start time: 0x01d35e2bd2da71ef  
Faulting application path: D:\Elasticsearch-5.5\bin\elasticsearch.exe  
Faulting module path: C:\Windows\system32\KERNELBASE.dll  
Report Id: 256e286d-ca1f-11e7-80f4-0050569757d6  
Faulting package full name:  
Faulting package-relative application ID:

Fault bucket , type 0  
Event Name: CLR20r3  
Response: Not available  
Cab Id: 0

Problem signature:  
P1: elasticsearch.exe  
P2: 5.5.0.0  
P3: 5956e851  
P4: Elastic.ProcessHosts  
P5: 1.0.0.0  
P6: 5956e850  
P7: 57  
P8: 24  
P9: 4CY0JEX2JKCFD2IPWRSCWFYWSHBZ0QKL  
P10:

Attached files:

These files may be available here:  
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash\_elasticsearch.ex\_746e7346f392df7b3de3e7e27adb669f51275a5\_45fdfff9\_16cbe6eb

Analysis symbol:  
Rechecking for solution: 0  
Report Id: 256e286d-ca1f-11e7-80f4-0050569757d6  
Report Status: 4100  
Hashed bucket:

Environment information:

## D:\Elasticsearch-5.5\bin\>elasticsearch.exe --debug-env

## Elasticsearch

ES\_HOME (in order of precedence)

- HomeDirectoryProcessVariable = D:\Elasticsearch-5.5\
- HomeDirectoryUserVariable =
- HomeDirectoryMachineVariable = D:\Elasticsearch-5.5\
- From executable location = D:\Elasticsearch-5.5  
ES\_CONFIG (in order of precedence)
- ConfigDirectoryProcessVariable = D:\Elasticsearch-5.5\config
- ConfigDirectoryUserVariable =
- ConfigDirectoryMachineVariable = D:\Elasticsearch-5.5\config
- Fallback to ES\_HOME = D:\Elasticsearch-5.5\config

* * *

## Java

Java paths

- current = D:\Program Files\Java\jdk1.8.0\_141\bin\java.exe  
Java Candidates (in order of precedence)
- JavaHomeProcessVariable =
- JavaHomeUserVariable =
- JavaHomeMachineVariable =
- JdkRegistry64 = D:\Program Files\Java\jdk1.8.0\_141
- JreRegistry64 = D:\Program Files\Java\jre1.8.0\_141
- JdkRegistry32 =
- JreRegistry32 =  
Java checks
- Using32BitJava = False
- JAVA\_HOME as machine and user variable = Fals

Any help will be welcome.

Thanks

---

<div class="post-metadata">

**Author:** ![LachlanL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lachlanl/32/22784_2.png) [@LachlanL](https://discuss.elastic.co/u/LachlanL)\
**Post date:** [December 12, 2017, 12:16am UTC](https://discuss.elastic.co/t/can-not-start-elasticsearch-5-5-service/107921/2 "2017-12-12T00:16:17Z")

</div>

Bumping. We are setting the same problem. Any help would be appreciated. I have tried increasing the Windows Service timeout setting, but no dice. This appears to be an internal ElasticSearch process startup timeout (Elastic.ProcessHosts.Process.StartupException: Could not start process within (00:02:00)). Is there any way to increase this value, or maybe tune my startup so it takes less time? ElasticSearch seems to be getting close to being ready:  
[2017-12-12T09:44:20,966][INFO][o.e.n.Node] [NORPEWMMON1] initializing ...  
[2017-12-12T09:44:21,302][INFO][o.e.e.NodeEnvironment] [NORPEWMMON1] using [1] data paths, mounts [[System (\m-part.active.preprod\mms)]], net usable\_space [28.7gb], net total\_space [139.9gb], spins? [unknown], types [NTFS]  
[2017-12-12T09:44:21,303][INFO][o.e.e.NodeEnvironment] [NORPEWMMON1] heap size [1.9gb], compressed ordinary object pointers [true]  
[2017-12-12T09:45:54,509][INFO][o.e.n.Node] [NORPEWMMON1] node name [NORPEWMMON1], node ID [862a0F6ZTvqkXVcIov6yfg]  
[2017-12-12T09:45:54,510][INFO][o.e.n.Node] [NORPEWMMON1] version[5.5.2], pid[5948], build[b2f0c09/2017-08-14T12:33:14.154Z], OS[Windows Server 2012 R2/6.3/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0\_144/25.144-b01]  
[2017-12-12T09:45:54,510][INFO][o.e.n.Node] [NORPEWMMON1] JVM arguments [-XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Xmx2048m, -Xms2048m, -Delasticsearch, -Des.path.home=D:\Mms\ElasticStack\Elasticsearch]  
[2017-12-12T09:45:55,951][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [aggs-matrix-stats]  
[2017-12-12T09:45:55,951][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [ingest-common]  
[2017-12-12T09:45:55,951][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [lang-expression]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [lang-groovy]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [lang-mustache]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [lang-painless]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [parent-join]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [percolator]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [reindex]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [transport-netty3]  
[2017-12-12T09:45:55,952][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded module [transport-netty4]  
[2017-12-12T09:45:55,953][INFO][o.e.p.PluginsService] [NORPEWMMON1] loaded plugin [x-pack]  
[2017-12-12T09:45:59,442][DEBUG][o.e.a.ActionModule] Using REST wrapper from plugin org.elasticsearch.xpack.XPackPlugin  
[2017-12-12T09:46:00,306][INFO][o.e.x.c.h.HttpClient] [NORPEWMMON1] Using default proxy for http input and slack/hipchat/pagerduty/webhook actions [nemproxy:8080]  
[2017-12-12T09:46:01,044][INFO][o.e.x.m.j.p.l.CppLogMessageHandler] [controller/6072] [[Main.cc](http://Main.cc)@128] controller (64 bit): Version 5.5.2 (Build 0d83940bb9d682) Copyright (c) 2017 Elasticsearch BV  
[2017-12-12T09:46:01,064][INFO][o.e.d.DiscoveryModule] [NORPEWMMON1] using discovery type [zen]

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 9, 2018, 12:16am UTC](https://discuss.elastic.co/t/can-not-start-elasticsearch-5-5-service/107921/3 "2018-01-09T00:16:19Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
