Logstash突然停止工作

时间:2017-02-02 09:15:57

标签: logstash kibana devops elastic-stack logstash-configuration

我已经下载了logstash,Kibana和Elastic搜索版本5.1.2。我完全能够使用完整的logstash,弹性搜索和kibana管道来运行它们。 不知道我的配置出了什么问题,但我从未做过任何具体的更改。当我尝试启动logstash时,它会给我以下错误。 我使用命令在Windows上运行 logstash -f logstash-simple.conf

* logstash-simple.conf是我的conf文件,它具有非常基本的stdin操作。 但是,通过这个命令,我突然得到了异常,并且很难理解失败的根本原因。

*

NameError: missing class name (`org.apache.logging.log4j.Level')
  get_proxy_or_package_under_package at org/jruby/javasupport/JavaUtilities.java:54
                      method_missing at file:/D:/Case Study/ELK/tools/logstash-5.1.2/vendor/jruby/lib/jruby.jar!/jruby/java/java_package_module_template.rb:14
                             Logging at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/logging/logger.rb:6
                            LogStash at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/logging/logger.rb:5
                              (root) at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/logging/logger.rb:4
                             require at org/jruby/RubyKernel.java:1040
                              (root) at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/util/loggable.rb:1
                             require at org/jruby/RubyKernel.java:1040
                              (root) at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/util/loggable.rb:2
                             require at org/jruby/RubyKernel.java:1040
                              (root) at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/settings.rb:1
                             require at org/jruby/RubyKernel.java:1040
                              (root) at D:/Case Study/ELK/tools/logstash-5.1.2/logstash-core/lib/logstash/settings.rb:2
                             require at org/jruby/RubyKernel.java:1040
                              (root) at D:\Case Study\ELK\tools\logstash-5.1.2\lib\bootstrap\environment.rb:70*

*

任何帮助将不胜感激

1 个答案:

答案 0 :(得分:0)

可能有多种原因。

  1. 解析模板不可用
  2. 有时Java会因堆/内存问题而崩溃。理想情况下,您应该将其作为守护程序运行,以便它自己重新生成,如果您的守护程序继续崩溃,那么您应该尝试更改堆大小。