# \[Logstash\] Insufficient memory for the Java Runtime Environment to continue **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [November 11, 2020, 2:29pm UTC](https://discuss.elastic.co/t/logstash-insufficient-memory-for-the-java-runtime-environment-to-continue/255084 "2020-11-11T14:29:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Albertoares](https://avatars.discourse-cdn.com/v4/letter/a/df788c/32.png) [@Albertoares](https://discuss.elastic.co/u/Albertoares)\ **Post date:** [November 11, 2020, 2:29pm UTC](https://discuss.elastic.co/t/logstash-insufficient-memory-for-the-java-runtime-environment-to-continue/255084/1 "2020-11-11T14:29:14Z")
Hi everyone, I have a hard time with logstash service. My server was set up to send filebeat to a kafka server and everything was fine until yesterday where I had the following error when debugging logstash: ` OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. OpenJDK 64-Bit Server VM warning: INFO: os::commit\_memory(0x00000000ca660000, 899284992, 0) failed; error='Not enough space' (errno=12) # # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 899284992 bytes for committing reserved memory.` Right now the physical memory looks like this: ``` ` total used free shared buff/cache available Mem: 3944 3028 465 2 450 684 Swap: 0 0 0` ``` in my jvm.options, the heap space was originally set as: `-Xms1g -Xmx1g` I tried to lower the heap space (any value below 1G), but if I do this then logstash starts to work but it stops very quickly and I get another type of error. It seems that logstash can not work with a lower heap space. In particular this is the error I get when lowering the heap space: ``` `[ERROR] 2020-11-11 15:21:29.024 [Ruby-0-Thread-8: :1] javapipeline - Worker loop initialization error {:pipeline_id=>"main", :error=>"Missing Filter End Vertex", :exception=>Java::JavaLang::IllegalStateException, :stacktrace=>"org.logstash.config.ir.CompiledPipeline$CompiledExecution.lambda$compileFilters$1(org/logstash/config/ir/CompiledPipeline.java:386)\njava.util.Optional.orElseThrow(java/util/Optional.java:408)\norg.logstash.config.ir.CompiledPipeline$CompiledExecution.compileFilters(org/logstash/config/ir/CompiledPipeline.java:386)\norg.logstash.config.ir.CompiledPipeline$CompiledExecution.(org/logstash/config/ir/CompiledPipeline.java:369)\norg.logstash.config.ir.CompiledPipeline$CompiledUnorderedExecution.(org/logstash/config/ir/CompiledPipeline.java:329)\norg.logstash.config.ir.CompiledPipeline.buildExecution(org/logstash/config/ir/CompiledPipeline.java:153)\norg.logstash.execution.WorkerLoop.(org/logstash/execution/WorkerLoop.java:63)\njdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)\njdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(jdk/internal/reflect/NativeConstructorAccessorImpl.java:62)\njdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(jdk/internal/reflect/DelegatingConstructorAccessorImpl.java:45)\njava.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:490)\norg.jruby.javasupport.JavaConstructor.newInstanceDirect(org/jruby/javasupport/JavaConstructor.java:253)\norg.jruby.RubyClass.newInstance(org/jruby/RubyClass.java:939)\norg.jruby.RubyClass$INVOKER$i$newInstance.call(org/jruby/RubyClass$INVOKER$i$newInstance.gen)\nusr.share.logstash.logstash_minus_core.lib.logstash.java_pipeline.init_worker_loop(/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:499)\nusr.share.logstash.logstash_minus_core.lib.logstash.java_pipeline.RUBY$method$init_worker_loop$0$ __VARARGS__ (usr/share/logstash/logstash_minus_core/lib/logstash//usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb)\nusr.share.logstash.logstash_minus_core.lib.logstash.java_pipeline.start_workers(/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:267)\norg.jruby.RubyProc.call(org/jruby/RubyProc.java:318)\njava.lang.Thread.run(java/lang/Thread.java:834)", :thread=>"#"}` ``` Is there anoyone can help me to fix this issue? ---
**Author:** ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)\ **Post date:** [November 11, 2020, 3:14pm UTC](https://discuss.elastic.co/t/logstash-insufficient-memory-for-the-java-runtime-environment-to-continue/255084/2 "2020-11-11T15:14:14Z")
Perhaps the data that logstash compute already pass the heap memory. Try to increase the xms and xmx to 2g. ---
**Author:** ![Albertoares](https://avatars.discourse-cdn.com/v4/letter/a/df788c/32.png) [@Albertoares](https://discuss.elastic.co/u/Albertoares)\ **Post date:** [November 11, 2020, 3:24pm UTC](https://discuss.elastic.co/t/logstash-insufficient-memory-for-the-java-runtime-environment-to-continue/255084/3 "2020-11-11T15:24:07Z")
Unfortunately I still have the same problem: There is insufficient memory for the Java Runtime Environment to continue. ---
**Author:** ![Albertoares](https://avatars.discourse-cdn.com/v4/letter/a/df788c/32.png) [@Albertoares](https://discuss.elastic.co/u/Albertoares)\ **Post date:** [November 18, 2020, 3:53pm UTC](https://discuss.elastic.co/t/logstash-insufficient-memory-for-the-java-runtime-environment-to-continue/255084/5 "2020-11-18T15:53:06Z")
Is there anyone who has an idea on that? Apparently logstash works only if I reboot the server. However, the problem occurs very often, therefore rebooting the server can not be a solution. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 16, 2020, 5:53pm UTC](https://discuss.elastic.co/t/logstash-insufficient-memory-for-the-java-runtime-environment-to-continue/255084/6 "2020-12-16T17:53:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.