Logstast startup issue

Elastic Stack Logstash
1

We are getting the below exception while starting the logstash agent.
Any one can help me please?
LoadError: Could not load FFI Provider: (NotImplementedError) FFI not available: null
See http://jira.codehaus.org/browse/JRUBY-4583
require at org/jruby/RubyKernel.java:1085
require at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55
(root) at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/ffi/ffi.rb:69
require at org/jruby/RubyKernel.java:1085
(root) at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:1
require at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55
require at org/jruby/RubyKernel.java:1085
(root) at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/ffi.rb:1
(root) at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:1
require at file:/home/release/release_independent/elk/logstashagent/vendor/jar/jruby-complete-1.7.11.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55
require at org/jruby/RubyKernel.java:1085
LibC at /home/release/release_independent/elk/logstashagent/lib/logstash/util/prctl.rb:4
(root) at /home/release/release_independent/elk/logstashagent/lib/logstash/util/prctl.rb:3
main at /home/release/release_independent/elk/logstashagent/lib/logstash/runner.rb:79
(root) at /home/release/release_independent/elk/logstashagent/lib/logstash/runner.rb:215

2

Providing your config would be useful.

3

Interesting; there was a very similar report just a few days ago:

4

Thank you for the response.
This issue got resolved.
Issue is due to /tmp is mounted with certain mount options.
After adding '-Djava.io.tmpdir=' to an other directory in logstash startup script, able to start the logstash agent.

We are using the logstash from long time and recently we moved new H/W for hosting the services. Hence we faced this issue.
As I mentioned after adding java.io.tmpdir we are able to start the agents.

Thanks,
Ravi

1 Like