Logstash启动时遇到的两个问题

最新推荐文章于 2024-04-08 11:48:38 发布
最新推荐文章于 2024-04-08 11:48:38 发布
阅读量2.8k 收藏
点赞数
分类专栏： 可视化 文章标签： linux docker 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_33271275/article/details/128782899
版权

Logstash启动时遇到的两个问题

Logstash启动需要对/usr/share/logstash/data目录有读写权限

根据日志,logstash需要对这个文件有读写权限,根据日志logstash还会在这个目录写创建文件

Logstash启动时要求pipelines文件在/usr/share/logstash/config/pipelines.yml

根据日志,Logstash启动过程中,会去默认位置读取pipelines.yml文件,而在其他位置都不行

启动Logstash容器的命令

docker run --name logstash \ -v /root/elk_workspace/logstash/config:/usr/share/logstash/config \ -v /var/log/nginx:/usr/share/logstash/data \ -v /root/elk_workspace/logstash/pipeline:/usr/share/logstash/pipeline \ -d logstash:7.14.0

虚拟机中的文件目录及文件信息

[root@iZbp1eq14sxovxncihmbb1Z logstash]# pwd
/root/elk_workspace/logstash
[root@iZbp1eq14sxovxncihmbb1Z logstash]# ll
total 8
drwxr-xr-x 2 root root 4096 Jan 28 22:23 config
drwxr-xr-x 2 root root 4096 Jan 28 22:12 pipeline
[root@iZbp1eq14sxovxncihmbb1Z logstash]# cd config/
[root@iZbp1eq14sxovxncihmbb1Z config]# ll
total 8
-rw-r--r-- 1 root root 526 Jan 28 21:04 logstash.yml
-rw-r--r-- 1 root root  84 Jan 28 21:21 pipelines.yml
[root@iZbp1eq14sxovxncihmbb1Z config]# cat logstash.yml 
node.name: logstash-203
# 日志文件目录配置
path.logs: /usr/share/logstash/logs
# # 验证配置文件及存在性
config.test_and_exit: false
# # 配置文件改变时是否自动加载
config.reload.automatic: false
# # 重新加载配置文件间隔
config.reload.interval: 60s
# # debug模式 开启后会打印解析后的配置文件 包括密码等信息 慎用
# # 需要同时配置日志等级为debug
config.debug: true
log.level: debug
# # The bind address for the metrics REST endpoint.
http.host: 0.0.0.0
[root@iZbp1eq14sxovxncihmbb1Z config]# cat pipelines.yml 
- pipeline.id: pipline_1
  path.config: /usr/share/logstash/pipeline/pipline_1.conf
[root@iZbp1eq14sxovxncihmbb1Z config]# ll
total 8
-rw-r--r-- 1 root root 526 Jan 28 21:04 logstash.yml
-rw-r--r-- 1 root root  84 Jan 28 21:21 pipelines.yml
[root@iZbp1eq14sxovxncihmbb1Z config]# cd ..
[root@iZbp1eq14sxovxncihmbb1Z logstash]# ll
total 8
drwxr-xr-x 2 root root 4096 Jan 28 22:23 config
drwxr-xr-x 2 root root 4096 Jan 28 22:12 pipeline
[root@iZbp1eq14sxovxncihmbb1Z logstash]# cd pipeline/
[root@iZbp1eq14sxovxncihmbb1Z pipeline]# ll
total 4
-rw-r--r-- 1 root root 168 Jan 28 21:09 pipline_1.conf
[root@iZbp1eq14sxovxncihmbb1Z pipeline]# cat pipline_1.conf 
input {
    file{
        path => "/usr/share/logstash/data/test.log"
        codec => json
        start_position => "beginning"
    }
}
output {
    stdout {
        codec => rubydebug
    }
}
[root@iZbp1eq14sxovxncihmbb1Z pipeline]#

通过docker logs -f logstash查询出来的日志文件

Using bundled JDK: /usr/share/logstash/jdk
warning: no jvm.options file found
/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated
Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console
[INFO ] 2023-01-28 14:03:51.580 [main] runner - Starting Logstash {"logstash.version"=>"7.14.0", "jruby.version"=>"jruby 9.2.19.0 (2.5.8) 2021-06-15 55810c552b OpenJDK 64-Bit Server VM 11.0.11+9 on 11.0.11+9 +jit [linux-x86_64]"}
[DEBUG] 2023-01-28 14:03:51.587 [main] scaffold - Found module {:module_name=>"fb_apache", :directory=>"/usr/share/logstash/modules/fb_apache/configuration"}
[DEBUG] 2023-01-28 14:03:51.587 [main] registry - Adding plugin to the registry {:name=>"fb_apache", :type=>:modules, :class=>#<LogStash::Modules::Scaffold:0x2331ac37 @directory="/usr/share/logstash/modules/fb_apache/configuration", @module_name="fb_apache", @kibana_version_parts=["6", "0", "0"]>}
[DEBUG] 2023-01-28 14:03:51.587 [main] scaffold - Found module {:module_name=>"netflow", :directory=>"/usr/share/logstash/modules/netflow/configuration"}
[DEBUG] 2023-01-28 14:03:51.588 [main] registry - Adding plugin to the registry {:name=>"netflow", :type=>:modules, :class=>#<LogStash::Modules::Scaffold:0x588e4caa @directory="/usr/share/logstash/modules/netflow/configuration", @module_name="netflow", @kibana_version_parts=["6", "0", "0"]>}
[FATAL] 2023-01-28 14:03:51.591 [main] runner - An unexpected error occurred! {:error=>#<ArgumentError: Path "/usr/share/logstash/data" must be a writable directory. It is not writable.>, :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/settings.rb:530:in `validate'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:290:in `validate_value'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:201:in `block in validate_all'", "org/jruby/RubyHash.java:1415:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:200:in `validate_all'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:326:in `execute'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:274:in `run'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:in `run'", "/usr/share/logstash/lib/bootstrap/environment.rb:88:in `<main>'"]}
[FATAL] 2023-01-28 14:03:51.594 [main] Logstash - Logstash stopped processing because of an error: (SystemExit) exit
org.jruby.exceptions.SystemExit: (SystemExit) exit
    at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:747) ~[jruby-complete-9.2.19.0.jar:?]
    at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:710) ~[jruby-complete-9.2.19.0.jar:?]
    at usr.share.logstash.lib.bootstrap.environment.<main>(/usr/share/logstash/lib/bootstrap/environment.rb:89) ~[?:?]
​
​
Using bundled JDK: /usr/share/logstash/jdk
warning: no jvm.options file found
/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/bundler-1.17.3/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated
Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console
[INFO ] 2023-01-28 14:07:51.960 [main] runner - Starting Logstash {"logstash.version"=>"7.14.0", "jruby.version"=>"jruby 9.2.19.0 (2.5.8) 2021-06-15 55810c552b OpenJDK 64-Bit Server VM 11.0.11+9 on 11.0.11+9 +jit [linux-x86_64]"}
[DEBUG] 2023-01-28 14:07:51.968 [main] scaffold - Found module {:module_name=>"fb_apache", :directory=>"/usr/share/logstash/modules/fb_apache/configuration"}
[DEBUG] 2023-01-28 14:07:51.968 [main] registry - Adding plugin to the registry {:name=>"fb_apache", :type=>:modules, :class=>#<LogStash::Modules::Scaffold:0x7148320d @directory="/usr/share/logstash/modules/fb_apache/configuration", @module_name="fb_apache", @kibana_version_parts=["6", "0", "0"]>}
[DEBUG] 2023-01-28 14:07:51.969 [main] scaffold - Found module {:module_name=>"netflow", :directory=>"/usr/share/logstash/modules/netflow/configuration"}
[DEBUG] 2023-01-28 14:07:51.969 [main] registry - Adding plugin to the registry {:name=>"netflow", :type=>:modules, :class=>#<LogStash::Modules::Scaffold:0x24d642eb @directory="/usr/share/logstash/modules/netflow/configuration", @module_name="netflow", @kibana_version_parts=["6", "0", "0"]>}
[INFO ] 2023-01-28 14:07:51.975 [main] writabledirectory - Creating directory {:setting=>"path.queue", :path=>"/usr/share/logstash/data/queue"}
[INFO ] 2023-01-28 14:07:51.975 [main] writabledirectory - Creating directory {:setting=>"path.dead_letter_queue", :path=>"/usr/share/logstash/data/dead_letter_queue"}
[DEBUG] 2023-01-28 14:07:52.239 [LogStash::Runner] runner - -------- Logstash Settings (* means modified) ---------
[DEBUG] 2023-01-28 14:07:52.240 [LogStash::Runner] runner - *node.name: "logstash-203" (default: "56e81483a095")
[DEBUG] 2023-01-28 14:07:52.240 [LogStash::Runner] runner - path.data: "/usr/share/logstash/data"
[DEBUG] 2023-01-28 14:07:52.240 [LogStash::Runner] runner - modules.cli: <Java::OrgLogstashUtil::ModulesSettingArray:1 []>
[DEBUG] 2023-01-28 14:07:52.240 [LogStash::Runner] runner - modules: []
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - modules_list: []
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - modules_variable_list: []
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - modules_setup: false
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - config.test_and_exit: false
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - config.reload.automatic: false
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - *config.reload.interval: #<Java::OrgLogstashUtil::TimeValue:0x5195117> (default: #<Java::OrgLogstashUtil::TimeValue:0x7da1bf14>)
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - config.support_escapes: false
[DEBUG] 2023-01-28 14:07:52.243 [LogStash::Runner] runner - config.field_reference.parser: "STRICT"
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - metric.collect: true
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - pipeline.id: "main"
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - pipeline.system: false
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - pipeline.workers: 2
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - pipeline.batch.size: 125
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - pipeline.batch.delay: 50
[DEBUG] 2023-01-28 14:07:52.244 [LogStash::Runner] runner - pipeline.unsafe_shutdown: false
[DEBUG] 2023-01-28 14:07:52.248 [LogStash::Runner] runner - pipeline.java_execution: true
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - pipeline.reloadable: true
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - pipeline.plugin_classloaders: false
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - pipeline.separate_logs: false
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - pipeline.ordered: "auto"
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - pipeline.ecs_compatibility: "disabled"
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - path.plugins: []
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - *config.debug: true (default: false)
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - *log.level: "debug" (default: "info")
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - version: false
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - help: false
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - log.format: "plain"
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - http.enabled: true
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - *http.host: "0.0.0.0" (default: "127.0.0.1")
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - http.port: 9600..9700
[DEBUG] 2023-01-28 14:07:52.249 [LogStash::Runner] runner - http.environment: "production"
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.type: "memory"
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.drain: false
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.page_capacity: 67108864
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.max_bytes: 1073741824
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.max_events: 0
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.checkpoint.acks: 1024
[DEBUG] 2023-01-28 14:07:52.250 [LogStash::Runner] runner - queue.checkpoint.writes: 1024
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - queue.checkpoint.interval: 1000
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - queue.checkpoint.retry: false
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - dead_letter_queue.enable: false
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - dead_letter_queue.max_bytes: 1073741824
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - dead_letter_queue.flush_interval: 5000
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - slowlog.threshold.warn: #<Java::OrgLogstashUtil::TimeValue:0x4f98ae97>
[DEBUG] 2023-01-28 14:07:52.256 [LogStash::Runner] runner - slowlog.threshold.info: #<Java::OrgLogstashUtil::TimeValue:0x738f6e44>
[DEBUG] 2023-01-28 14:07:52.268 [LogStash::Runner] runner - slowlog.threshold.debug: #<Java::OrgLogstashUtil::TimeValue:0x4913778f>
[DEBUG] 2023-01-28 14:07:52.269 [LogStash::Runner] runner - slowlog.threshold.trace: #<Java::OrgLogstashUtil::TimeValue:0xa22be4c>
[DEBUG] 2023-01-28 14:07:52.269 [LogStash::Runner] runner - keystore.classname: "org.logstash.secret.store.backend.JavaKeyStore"
[DEBUG] 2023-01-28 14:07:52.269 [LogStash::Runner] runner - keystore.file: "/usr/share/logstash/config/logstash.keystore"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - path.queue: "/usr/share/logstash/data/queue"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - path.dead_letter_queue: "/usr/share/logstash/data/dead_letter_queue"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - path.settings: "/usr/share/logstash/config"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - path.logs: "/usr/share/logstash/logs"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.enabled: false
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.logstash.poll_interval: #<Java::OrgLogstashUtil::TimeValue:0x37ee58cf>
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.pipeline.id: ["main"]
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.elasticsearch.username: "logstash_system"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.elasticsearch.hosts: ["https://localhost:9200"]
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.elasticsearch.ssl.verification_mode: "certificate"
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.management.elasticsearch.sniffing: false
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.monitoring.enabled: false
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.monitoring.elasticsearch.hosts: ["http://localhost:9200"]
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.monitoring.collection.interval: #<Java::OrgLogstashUtil::TimeValue:0x7c5f244c>
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.monitoring.collection.timeout_interval: #<Java::OrgLogstashUtil::TimeValue:0x77cfbbba>
[DEBUG] 2023-01-28 14:07:52.270 [LogStash::Runner] runner - xpack.monitoring.elasticsearch.username: "logstash_system"
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - xpack.monitoring.elasticsearch.ssl.verification_mode: "certificate"
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - xpack.monitoring.elasticsearch.sniffing: false
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - xpack.monitoring.collection.pipeline.details.enabled: true
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - xpack.monitoring.collection.config.enabled: true
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - monitoring.enabled: false
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - monitoring.elasticsearch.hosts: ["http://localhost:9200"]
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - monitoring.collection.interval: #<Java::OrgLogstashUtil::TimeValue:0x1bd051c4>
[DEBUG] 2023-01-28 14:07:52.271 [LogStash::Runner] runner - monitoring.collection.timeout_interval: #<Java::OrgLogstashUtil::TimeValue:0x3be76b8d>
[DEBUG] 2023-01-28 14:07:52.278 [LogStash::Runner] runner - monitoring.elasticsearch.username: "logstash_system"
[DEBUG] 2023-01-28 14:07:52.278 [LogStash::Runner] runner - monitoring.elasticsearch.ssl.verification_mode: "certificate"
[DEBUG] 2023-01-28 14:07:52.278 [LogStash::Runner] runner - monitoring.elasticsearch.sniffing: false
[DEBUG] 2023-01-28 14:07:52.278 [LogStash::Runner] runner - monitoring.collection.pipeline.details.enabled: true
[DEBUG] 2023-01-28 14:07:52.279 [LogStash::Runner] runner - monitoring.collection.config.enabled: true
[DEBUG] 2023-01-28 14:07:52.279 [LogStash::Runner] runner - node.uuid: ""
[DEBUG] 2023-01-28 14:07:52.279 [LogStash::Runner] runner - --------------- Logstash Settings -------------------
[DEBUG] 2023-01-28 14:07:52.283 [LogStash::Runner] multilocal - Reading pipeline configurations from YAML {:location=>"/usr/share/logstash/config/pipelines.yml"}
ERROR: Failed to read pipelines yaml file. Location: /usr/share/logstash/config/pipelines.yml
usage:
  bin/logstash -f CONFIG_PATH [-t] [-r] [] [-w COUNT] [-l LOG]
  bin/logstash --modules MODULE_NAME [-M "MODULE_NAME.var.PLUGIN_TYPE.PLUGIN_NAME.VARIABLE_NAME=VALUE"] [-t] [-w COUNT] [-l LOG]
  bin/logstash -e CONFIG_STR [-t] [--log.level fatal|error|warn|info|debug|trace] [-w COUNT] [-l LOG]
  bin/logstash -i SHELL [--log.level fatal|error|warn|info|debug|trace]
  bin/logstash -V [--log.level fatal|error|warn|info|debug|trace]
  bin/logstash --help
[FATAL] 2023-01-28 14:07:52.304 [LogStash::Runner] Logstash - Logstash stopped processing because of an error: (SystemExit) exit
org.jruby.exceptions.SystemExit: (SystemExit) exit
    at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:747) ~[jruby-complete-9.2.19.0.jar:?]
    at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:710) ~[jruby-complete-9.2.19.0.jar:?]
    at usr.share.logstash.lib.bootstrap.environment.<main>(/usr/share/logstash/lib/bootstrap/environment.rb:89) ~[?:?]
​
爱灵1997
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
Logstash stopped processing because of an error: (SystemExit) exitorg.jruby.exceptions.SystemExit:
qq 117791303
08-05 2480
[2023-08-05T00:13:16,944][FATAL][org.logstash.Logstash ] Logstash stopped processing because of an error: (SystemExit) exit org.jruby.exceptions.SystemExit: (SystemExit) exit at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:790) ~[jruby.ja
logstash启动失败
slsunxia的博客
07-09 1088
【问题描述】 启动logstash失败，systemctl status logstash查看报错start request repeated too quickly for logstash.service 【问题分析】 1、执行/usr/share/logstash/bin/logstash --path.settings /etc/logstash显示启动成功 2、步骤1后查看进程ps -ef|grep logstash，可以查到相关进程 【解决方案】 到/usr/share/logstash/bi
ELK本地虚拟机部署（8.12版本）
最新发布
qq_42235364的博客
04-08 738
鉴于公司服务器上日志越来越多，需要搭建ELK对日志进行采集和分析，用于后续故障排查。程序下载地址：elasticsearch:Elasticsearch 8.12.0 | Elasticlogstash:Logstash 8.12.0 | Elastickibana:Kibana 8.12.0 | Elasticfilebeat:Filebeat 8.12.0 | Elastic 1.2 环境变量（elasticsearch集群所有节点） 1.3 程序配置 1.3.1 节点1配置 elast
windows logstash 启动报错： could not find java； set JAVA_HOME or ensure java is in PATH
new_baibai的博客
06-07 835
window 启动 logstash 报错
logstash报错问题解决：Logstash stopped processing because of an error: (SystemExit) exit
热门推荐
BigCabbageFy的博客
09-05 3万+
在启动logstash过程中出现了无法启动的情况，事情经过是这样的，首先我在第一次启动的过程中是正常的可以正常运行，就像下方代码显示：在输入hello word 后，logstash可以正常输出。 [root@hadoop bin]# logstash -e "" Thread.exclusive is deprecated, use Thread::Mutex Sending Logstash ...
Logstash报错：Logstash - java.lang.IllegalStateException: Logstash stopped processing because of an err
冷心笑看丽美人 ~ blog
08-23 5278
logstash -e 'input { stdin {} } output { stdout {} }'报错 ，竟然是输入包含中文？可笑
hadoop启动日志
06-14
4. **错误信息**: 记录了服务运行过程中遇到的错误，是解决问题的重要线索。 5. **事件记录**: 如任务的提交、启动、完成、失败等关键事件。 在`logs`目录下，你可以找到不同组件的日志文件，如`hadoop-root-...
Go-Go分级执行日志
08-14
1. 引入`golang.org/x/sys/unix`和`golang.org/x/sys/windows`库（根据平台），因为glog依赖这两个库进行文件I/O操作。 2. 初始化glog，一般在程序启动时进行。 3. 使用`glog.Info()`, `glog.Warning()`, `glog....
windows搭建的ElasticSearch集群
05-11
在我们的案例中，我们有三个节点，一个为主节点，两个为从节点。因此，主节点的`node.master`应设为`true`，`node.data`可设为`false`；从节点的`node.master`设为`false`，`node.data`设为`true`。 接下来，启动这...
snort2980 for windows
11-15
确保在安装前仔细阅读这个说明文件，以便了解可能遇到的问题和解决方案。 安装过程相对简单，双击`Snort_2_9_8_0_Installer.exe`执行安装向导，按照提示进行操作。安装过程中，你可能会被询问关于安装路径、组件...
PrincessLog.zip
09-09
在“PrincessLog.zip”中，我们看到两个主要的子文件夹：“src”和“build”。这可能代表项目的源代码目录和构建输出。 1. **src**：通常包含项目的源代码，程序员在此编写、组织和管理代码。日志记录可能被嵌入到...
启动logstash服务出现的问题
a1234012340a的博客
03-05 5283
启动后发现logstash占用cpu超级高，问了师傅。师傅说你这个logstash应该是没启动，他在一直尝试重启。导致出现cpu占用100 调查问题开始 cmd执行，一步一步调查 由于小白。出现问题，报错如下 各种懵逼。。下面解决问题 执行logstash不行那么咱们就换一种方法执行，如下 还是不行，这句话是直接指定配置文件。 后来网上查到。 所以这个方法也告一段...
Windows下logstash安装插件提示“No `java.exe‘ executable found on PATH.”
baalchina的专栏
01-28 2907
Windows下的logstash，运行bin/logstash正常执行都OK，但安装插件的时候就提示这个： e:\logstash-7.16.0-windows-x86_64\logstash-7.16.0\bin>logstash-plugin install logstash-output-elasticsearch "Using bundled JDK: ." No `java.exe' executable found on PATH. 而很显然java.exe是在的。 解决办法
解决 logstash java.lang.IllegalStateException: Logstash stopped processing because of an error: (Syste
davin12的博客
02-07 5998
@[TOC](java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit) mac os在安装logstash的时候，总会出现这条错误，在官网找到了答案 macOS Gatekeeper warnings 苹果对更严格的公证要求的推出影响了7.10.2 Logstash工件的公证。如果macOS Catalina在首次运行Logstash时显示一个对话框，中断该对话框，
启动logstash时报错
qq_50685659的博客
08-26 1913
之前运行的instance有缓冲，默认保存在data目录下。未知为elasticsearch设置’host’
logstash 启动报错解决
Blog_inG的博客
07-05 1万+
使用官方提供的logstash 5.6.10 zip格式版本。本机windows 10jdk配置好 三个变量 java_homeclasspath  path .使用jdk版本为jdk1.8.0_144.如果解压之后的目录所在  路径存在 空格， 在执行logstash时会报 不能加载主类的错误 错误: 找不到或无法加载主类 Files\Elastic\logstash-6.3.0\logstas...
winserver2008 安装logstash
devil6636252的博客
04-24 4456
一、安装 在官网下载：Download Logstash Free | Get Started Now | Elastic 并解压 二、运行： 在logstash>bin 1、目录下创建：logstash.conf 2、输入内容: input { stdin{ } } output { stdout{ } } 3、在命令行运行logstash -f logstash.conf 遇到问题（一） 报错： OpenJDK 64-Bi..
关于ElasticSearch logstash的一些错误
weixin_44812264的博客
02-04 1906
运行环境：windows 1.ES的版本要和logstash的版本一致。 2.运行mysql.conf错误: 找不到或无法加载主类 Files\Java\jdk1.8.0_211\lib;C:\Program 解决方法：打开用bin目录下的logstash.bat文件，将 %JAVA% %JAVA_OPTS% -cp %CLASSPATH% org.logstash.Logstash %* 改为...
怎么样启动两个logstash
03-20
要启动两个Logstash实例，你可以按照以下步骤进行操作： 1. 首先，确保你已经安装了Logstash并配置好了相关的配置文件。 2. 在Logstash的安装目录下，创建两个独立的配置文件，例如`logstash1.conf`和`logstash2.conf`。 3. 打开`logstash1.conf`文件，配置该实例的输入、过滤和输出插件，以及其他相关参数。同样地，打开`logstash2.conf`文件，配置第二个实例的参数。 4. 打开终端或命令行窗口，进入Logstash的安装目录。 5. 启动第一个Logstash实例，运行以下命令： ``` bin/logstash -f logstash1.conf ``` 6. 启动第二个Logstash实例，运行以下命令： ``` bin/logstash -f logstash2.conf ``` 这样，你就成功启动了两个独立的Logstash实例。每个实例将根据其对应的配置文件处理输入数据，并将结果输出到指定的位置。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值