# Elasticsearch service start failed **URL:** \ **Category:** Elasticsearch\ **Created:** [June 9, 2016, 10:24am UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314 "2016-06-09T10:24:20Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Prateek\_Kshtriya](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@Prateek\_Kshtriya](https://discuss.elastic.co/u/Prateek_Kshtriya)\ **Post date:** [June 9, 2016, 10:24am UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/1 "2016-06-09T10:24:20Z")
Hi All, I tried to start the elasticsearch service on command line(service start) which returned below error in log file- [2016-06-09 15:46:04] [error] [6328] Failed to start 'elasticsearch-service-x64' service [2016-06-09 15:46:04] [error] [6328] The data area passed to a system call is too small. [2016-06-09 15:46:04] [info] [6328] Start service finished. [2016-06-09 15:46:04] [error] [6328] Commons Daemon procrun failed with exit value: 5 (Failed to start service) [2016-06-09 15:46:04] [error] [6328] The data area passed to a system call is too small. I have gone through some of the previous topics created with same subject line suggesting to delete & reinstall elasticsearch again but I have indexed data which might get lost if I perform the activity. Please suggest. Regards, Prateek Divya ---
**Author:** ![Prateek\_Kshtriya](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@Prateek\_Kshtriya](https://discuss.elastic.co/u/Prateek_Kshtriya)\ **Post date:** [June 9, 2016, 10:40am UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/2 "2016-06-09T10:40:50Z")
I found out in the event log - The Elasticsearch 2.1.0 (elasticsearch-service-x64) service terminated with service-specific error Incorrect function. 2016-06-09 16:05:37 Commons Daemon procrun stderr initialized Java HotSpot(TM) 64-Bit Server VM warning: Using the ParNew young collector with the Serial old collector is deprecated and will likely be removed in a future release Exception in thread "main" iptor.properties at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(Unknown Source) at java.nio.file.Files.newByteChannel(Unknown Source) at java.nio.file.Files.newByteChannel(Unknown Source) at java.nio.file.spi.FileSystemProvider.newInputStream(Unknown Source) at java.nio.file.Files.newInputStream(Unknown Source) at org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:86) at org.elasticsearch.plugins.PluginsService.getPluginBundles(PluginsService.java:302) at org.elasticsearch.plugins.PluginsService.(PluginsService.java:108) at org.elasticsearch.node.Node.(Node.java:148) at org.elasticsearch.node.Node.(Node.java:129) at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:145) at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178) at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:285) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35) Refer to the log for complete error details. The data area passed to a system call is too small. Failed to start service ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [June 9, 2016, 11:46am UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/3 "2016-06-09T11:46:16Z")
> [@Prateek\_Kshtriya](#): > > Java HotSpot(TM) 64-Bit Server VM warning: Using the ParNew young collector with the Serial old collector is deprecated and will likely be removed in a future release It looks like you've changed the GC settings? The serial old collector is not a good collector for use with a server application like Elasticsearch. > [@Prateek\_Kshtriya](#): > > Exception in thread "main" iptor.properties This is truncated. Can you share the entire exception? It looks like you're encountering some sort of I/O exception while attempting to read a plugin descriptor file, but it's hard to say without seeing the part of the exception that was truncated exactly what happened. ---
**Author:** ![Prateek\_Kshtriya](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@Prateek\_Kshtriya](https://discuss.elastic.co/u/Prateek_Kshtriya)\ **Post date:** [June 9, 2016, 12:07pm UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/4 "2016-06-09T12:07:24Z")
> [@jasontedor](#): > > It looks like you've changed the GC settings? The serial old collector is not a good collector for use with a server application like Elasticsearch. There was a java auto update happened on system which I suppose had impacted the GC setting.[quote="jasontedor, post:3, topic:52314"] This is truncated. Can you share the entire exception? It looks like you're encountering some sort of I/O exception while attempting to read a plugin descriptor file, but it's hard to say without seeing the part of the exception that was truncated exactly what happened. [/quote] Thanks for the help. I just checked out the ELASTICSEARCH.log which is having entry for - [2016-06-09 17:05:12,361][ERROR][bootstrap] Exception java.lang.IllegalStateException: Unable to initialize plugins at org.elasticsearch.plugins.PluginsService.(PluginsService.java:111) at org.elasticsearch.node.Node.(Node.java:148) at org.elasticsearch.node.Node.(Node.java:129) at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:145) at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178) at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:285) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35) Caused by: java.nio.file.NoSuchFileException: ELK\Elasticsearch\elasticsearch-2.1.0\plugins\graph-2.3.3.zip\plugin-descriptor.properties at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(Unknown Source) at java.nio.file.Files.newByteChannel(Unknown Source) at java.nio.file.Files.newByteChannel(Unknown Source) at java.nio.file.spi.FileSystemProvider.newInputStream(Unknown Source) at java.nio.file.Files.newInputStream(Unknown Source) at org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:86) at org.elasticsearch.plugins.PluginsService.getPluginBundles(PluginsService.java:302) at org.elasticsearch.plugins.PluginsService.(PluginsService.java:108) ... 6 more Regards, Prateek ---
**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\ **Post date:** [June 9, 2016, 12:21pm UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/5 "2016-06-09T12:21:44Z")
> [@Prateek\_Kshtriya](#): > > There was a java auto update happened on system which I suppose had impacted the GC setting. That can't be, Elasticsearch specifies its own GC settings in the startup scripts / service definition. > [@Prateek\_Kshtriya](#): > > Caused by: java.nio.file.NoSuchFileException: ELK\Elasticsearch\elasticsearch-2.1.0\plugins\graph-2.3.3.zip\plugin-descriptor.properties Your problem is this, you appear to have a botched plugin installation. I suggest removing that plugin and trying again. Also, I note that you appear to be running version 2.1.0 of Elasticsearch with version 2.3.3 of a plugin? If that's the official graph plugin, that will not work. ---
**Author:** ![Prateek\_Kshtriya](https://avatars.discourse-cdn.com/v4/letter/p/c37758/32.png) [@Prateek\_Kshtriya](https://discuss.elastic.co/u/Prateek_Kshtriya)\ **Post date:** [June 9, 2016, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/6 "2016-06-09T12:30:10Z")
> [@jasontedor](#): > > That can't be, Elasticsearch specifies its own GC settings in the startup scripts / service definition. I am sure I have not touched even a letter here 🙂 > [@jasontedor](#): > > Your problem is this, you appear to have a botched plugin installation. I suggest removing that plugin and trying again. Also, I note that you appear to be running version 2.1.0 of Elasticsearch with version 2.3.3 of a plugin? If that's the official graph plugin, that will not work. yes that's completely official graph 🙂 ) Also it was not working with 2.1.0 but kibana was working well before alongside. I had planned an upgrade using [Rolling Restarts | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/_rolling_restarts.html) but it went down completely. It worked when I removed Graph. Thank you for the help. Regards, Prateek ---
**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, 10:45pm UTC](https://discuss.elastic.co/t/elasticsearch-service-start-failed/52314/7 "2017-07-05T22:45:03Z")