# Auto\_flush\_interval is invalid with Logstash 7.5.1 **URL:** \ **Category:** Logstash\ **Created:** [July 21, 2020, 3:24pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057 "2020-07-21T15:24:08Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 3:24pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/1 "2020-07-21T15:24:08Z")
Hello, I've been running Logstash 7.5.1 on IBM Power systems for a couple of months. But, the last time I restarted Logstash, it kept shutdown and restarting. So I run it with ```auto config.debug = true log.level: trace ``` and found errors in _logstash-plain.log_ about invalid config setting _auto\_flush\_interval_. ```auto [2020-07-20T18:06:04,589][INFO][logstash.runner] Starting Logstash {"logstash.version"=>"7.5.1"} [2020-07-20T18:06:07,562][INFO][org.reflections.Reflections] Reflections took 72 ms to scan 1 urls, producing 20 keys and 40 values [2020-07-20T18:06:08,250][ERROR][logstash.filters.grok] Unknown setting 'auto_flush_interval' for grok [2020-07-20T18:06:08,264][ERROR][logstash.agent] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"Java::JavaLang::IllegalStateException", :message=>"Unable to configure plugins: (ConfigurationError) Something is wrong with your configuration.",... ``` I've looked in all Logstash \*.conf and \*.yml files and didn't see _auto\_flush\_interval_ defined anywhere. Could this property be set up internal of a plugin? We do have a Logstash plugin to read in input data but I have no details about it. ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 21, 2020, 3:32pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/2 "2020-07-21T15:32:39Z")
auto\_flush\_interval is an option on a multiline codec, not a grok filter. If you have enabled config.debug it should be showing you the configuration it is using and you can search that for auto\_flush\_interval. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 3:34pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/3 "2020-07-21T15:34:53Z")
Thank you for the reply. I just saw that I might have a typo when defining config.debug (with = instead of :). Will fix that and see if it'll print out which config file auto\_flush\_interval was in. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 5:41pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/4 "2020-07-21T17:41:29Z")
Interesting... After I changed "config.debug = true" to "config.debug: true" and restarted Logstash, the error _auto\_flush\_interval_ didn't occur. However, Logstash still failed as before: ```auto [2020-07-21T11:35:47,225][DEBUG][org.logstash.ackedqueue.QueueUpgrade] PQ version file with correct version information (v2) found. [2020-07-21T11:35:47,228][DEBUG][org.logstash.ackedqueue.Queue] opening head page: 68, in: /var/log/logstash/logstash-queue/main, with checkpoint: pageNum=68, firstUnackedPageNum=68, firstUnackedSeqNum=8385120, minSeqNum=8348433, elementCount=36687, isFullyAcked=yes [2020-07-21T11:35:47,462][ERROR][logstash.agent] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"Java::JavaLang::NoSuchMethodError", :message=>"java.nio.MappedByteBuffer.position(I)Ljava/nio/MappedByteBuffer;", :backtrace=>["org.logstash.ackedqueue.io.MmapPageIOV2.recover(MmapPageIOV2.java:135)", "org.logstash.ackedqueue.Queue.open(Queue.java:210)", "org.logstash.ackedqueue.ext.JRubyAckedQueueExt.open(JRubyAckedQueueExt.java:101)", "org.logstash.ackedqueue.ext.JRubyWrappedAckedQueueExt.initialize(JRubyWrappedAckedQueueExt.java:42)", "org.logstash.ackedqueue.QueueFactoryExt.create(QueueFactoryExt.java:39)", "org.logstash.execution.AbstractPipelineExt.openQueue(AbstractPipelineExt.java:174)", "org.logstash.execution.AbstractPipelineExt$INVOKER$i$0$0$openQueue.call(AbstractPipelineExt$INVOKER$i$0$0$openQueue.gen)", "org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:354)", "org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:143)", "org.jruby.ir.interpreter.InterpreterEngine.processCall(InterpreterEngine.java:345)", ... ``` I wonder if it's some problem with _jruby_ and why it didn't fail month ago. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 6:09pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/5 "2020-07-21T18:09:19Z")
There are other _java_ errors after the above _jruby_ error: ```auto [2020-07-21T14:03:56,433][ERROR][logstash.agent] An exception happened when converging configuration {:exception=>LogStash::Error, :message=>"Don't know how to handle `Java::JavaLang::NoSuchMethodError` for `PipelineAction::Create
`", :backtrace=>["org/logstash/execution/ConvergeResultExt.java:109:in `create'", "org/logstash/execution/ConvergeResultExt.java:37:in `add'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:339:in `block in converge_state'"]} [2020-07-21T14:03:56,443][FATAL][logstash.runner] An unexpected error occurred! {:error=>#`>, :backtrace=>["org/logstash/execution/ConvergeResultExt.java:109:in `create'", "org/logstash/execution/ConvergeResultExt.java:37:in `add'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:339:in `block in converge_state'"]} [2020-07-21T14:03:56,440][DEBUG][logstash.agent] Starting puma [2020-07-21T14:03:56,451][DEBUG][logstash.agent] Trying to start WebServer {:port=>9600} [2020-07-21T14:03:56,453][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit ``` I didn't know that _logstash_ also runs a web server. Is this right? So it can't start the web server at port 9600 for some reasons? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 21, 2020, 6:33pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/6 "2020-07-21T18:33:54Z")
Yes, logstash runs a webserver for the [monitoring API](https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html). That exception is occuring [here](https://github.com/elastic/logstash/blob/76a1d0a664ce55c36b0670edf116869eca430f68/logstash-core/src/main/java/org/logstash/execution/ConvergeResultExt.java#L109). It is trying to throw an exception, but the NoSuchMethodError means you do not get to see what exception it wanted to throw. Is the JVM you are using [supported](https://www.elastic.co/support/matrix#matrix_jvm)? I do not think it will change anything, but can you try running with "--java\_execution false"? ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 6:47pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/7 "2020-07-21T18:47:52Z")
The JVM is official release on RHEL 8.1: ```auto openjdk 13.0.2 2020-01-14 OpenJDK Runtime Environment 19.9 (build 13.0.2+8) OpenJDK 64-Bit Server VM 19.9 (build 13.0.2+8, mixed mode, sharing) ``` I run Logstash with _systemctl_. Sorry, I'm not sure how to run with "--java\_execution false". Can I set that in _logstash.yml_? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 21, 2020, 6:50pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/8 "2020-07-21T18:50:42Z")
> [@thanhlam](#): > > Can I set that in _logstash.yml_ ? Yes. ``` pipeline.java_execution: false ``` ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 7:00pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/9 "2020-07-21T19:00:46Z")
Running with java\_execution: false resulted in the same error. Following is the "long" _jruby_ error that I didn't want to post here. But, may be there's clue in there as per which method was causing problem. Could you take a look please: ```auto [2020-07-21T14:55:45,315][ERROR][logstash.agent] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"Java::JavaLang::NoSuchMethodError", :message=>"java.nio.MappedByteBuffer.position(I)Ljava/nio/MappedByteBuffer;", :backtrace=>["org.logstash.ackedqueue.io.MmapPageIOV2.create(MmapPageIOV2.java:171)", "org.logstash.ackedqueue.Queue.newCheckpointedHeadpage(Queue.java:315)", "org.logstash.ackedqueue.Queue.open(Queue.java:166)", "org.logstash.ackedqueue.ext.JRubyAckedQueueExt.open(JRubyAckedQueueExt.java:101)", "org.logstash.ackedqueue.ext.JRubyWrappedAckedQueueExt.initialize(JRubyWrappedAckedQueueExt.java:42)", "org.logstash.ackedqueue.QueueFactoryExt.create(QueueFactoryExt.java:39)", "org.logstash.execution.AbstractPipelineExt.openQueue(AbstractPipelineExt.java:174)", "org.logstash.execution.AbstractPipelineExt$INVOKER$i$0$0$openQueue.call(AbstractPipelineExt$INVOKER$i$0$0$openQueue.gen)", "org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:354)", "org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:143)", "org.jruby.ir.interpreter.InterpreterEngine.processCall(InterpreterEngine.java:345)", "org.jruby.ir.interpreter.StartupInterpreterEngine.interpret(StartupInterpreterEngine.java:72)", "org.jruby.internal.runtime.methods.MixedModeIRMethod.INTERPRET_METHOD(MixedModeIRMethod.java:105)", "org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:92)", "org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332)", "org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:86)", "org.jruby.RubyClass.newInstance(RubyClass.java:915)", "org.jruby.RubyClass$INVOKER$i$newInstance.call(RubyClass$INVOKER$i$newInstance.gen)", "org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:332)", "org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:86)", "org.jruby.ir.instructions.CallBase.interpret(CallBase.java:540)", "org.jruby.ir.interpreter.InterpreterEngine.processCall(InterpreterEngine.java:361)", "org.jruby.ir.interpreter.StartupInterpreterEngine.interpret(StartupInterpreterEngine.java:72)", "org.jruby.ir.interpreter.InterpreterEngine.interpret(InterpreterEngine.java:92)", "org.jruby.internal.runtime.methods.MixedModeIRMethod.INTERPRET_METHOD(MixedModeIRMethod.java:204)", "org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:191)", "org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:208)", "org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:396)", "org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:205)", "org.jruby.ir.interpreter.InterpreterEngine.processCall(InterpreterEngine.java:325)", "org.jruby.ir.interpreter.StartupInterpreterEngine.interpret(StartupInterpreterEngine.java:72)", "org.jruby.ir.interpreter.Interpreter.INTERPRET_BLOCK(Interpreter.java:114)", "org.jruby.runtime.MixedModeIRBlockBody.commonYieldPath(MixedModeIRBlockBody.java:151)", "org.jruby.runtime.IRBlockBody.call(IRBlockBody.java:79)", "org.jruby.runtime.Block.call(Block.java:129)", "org.jruby.RubyProc.call(RubyProc.java:295)", "org.jruby.RubyProc.call(RubyProc.java:274)", "org.jruby.RubyProc.call(RubyProc.java:270)", "org.jruby.internal.runtime.RubyRunnable.run(RubyRunnable.java:105)", "java.lang.Thread.run(Thread.java:748)"]} ``` ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 7:01pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/10 "2020-07-21T19:01:39Z")
I manually broke apart the long string. Maybe that is worth to take a look? Thanks! ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 21, 2020, 7:32pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/11 "2020-07-21T19:32:21Z")
> [@thanhlam](#): > > ```auto > :exception=>"Java::JavaLang::NoSuchMethodError", > :message=>"java.nio.MappedByteBuffer.position(I)Ljava/nio/MappedByteBuffer;", > :backtrace=>["org.logstash.ackedqueue.io.MmapPageIOV2.create(MmapPageIOV2.java:171)", > > ``` OK, so MmapPageIOV2.java:171 is [this](https://github.com/elastic/logstash/blob/9d4452bba44f46b3ad6d4649beadc80c1b1fc5b5/logstash-core/src/main/java/org/logstash/ackedqueue/io/MmapPageIOV2.java#L171) line of code. It is calling .position on a java.nio.MappedByteBuffer and passing it an int. The problem is, it is looking for a method that returns a java.nio.MappedByteBuffer, and since position is inherited I suspect it can only find a .position method that returns a Buffer. Can you try running this with Java 1.8? There are some this in issue lists for a couple of other projects that make this sound like it might be a workaround. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 7:41pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/12 "2020-07-21T19:41:05Z")
My _logstash_ is built for the Power systems (ppc64le) and RHEL 8.1 particularly. I wasn't able to install it with _Java 1.8_. That's why I upgraded to Java-13. It probably will not work if I go back to Java 1.8. I'm still wondering how did it work for the time before this error happened when I restarted _logstash_. It's possible some other software installations changed java or _jruby_. I don't have control on all software installations. But, I'm thinking, maybe I can reinstall _Java-13_. Do you think that's worth a try? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 21, 2020, 8:33pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/13 "2020-07-21T20:33:56Z")
> [@thanhlam](#): > > But, I'm thinking, maybe I can reinstall _Java-13_ . Do you think that's worth a try? You could try it, but I am not optimistic. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 21, 2020, 10:03pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/14 "2020-07-21T22:03:21Z")
There is actually another version of Java (1.8) on the same system. I've been keeping the ELK stack to run with Java-13 by using $JAVA\_HOME and $PATH. I just tried setting ```auto export JAVA_HOME=/usr/lib/jvm/java-1.8.0 export PATH=/usr/lib/jvm/java-1.8.0/bin:$PATH ``` Then, started Logstash. It got the same error. Is this what you suggested to try? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 21, 2020, 10:22pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/15 "2020-07-21T22:22:59Z")
> [@thanhlam](#): > > Is this what you suggested to try? Yes. Unfortunately I have no further ideas. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 22, 2020, 5:39pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/16 "2020-07-22T17:39:08Z")
Thanks for helping to look into a couple problems! I uninstalled and installed _java-13_ and still got the same error. Because it's questionable that the error is a result of Logstash failed to get an integer returned from a java function, I'll open a GitHub issue to get a further look into the problem. I also ran out of ideas to try. ---
**Author:** ![thanhlam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thanhlam/32/78982_2.png) [@thanhlam](https://discuss.elastic.co/u/thanhlam)\ **Post date:** [July 22, 2020, 7:09pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/17 "2020-07-22T19:09:53Z")
GitHub ticket opened: [https://github.com/elastic/logstash/issues/12133](https://github.com/elastic/logstash/issues/12133) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 19, 2020, 7:16pm UTC](https://discuss.elastic.co/t/auto-flush-interval-is-invalid-with-logstash-7-5-1/242057/18 "2020-08-19T19:16:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.