Docker Logstash一开始就崩溃了
如标题所述,Logstash一启动就崩溃。Docker Logstash一开始就崩溃了,docker,crash,logstash,docker-compose,Docker,Crash,Logstash,Docker Compose,如标题所述,Logstash一启动就崩溃。 我正在通过Docker进行调查 这是我的输出: logstash_1 | {:timestamp=>"2016-10-25T13:14:31.470000+0000", :message=>"Reading config file", :config_file=>"/etc/logstash/conf.d/logstash.conf", :level=>:debug, :file=>"logstash/co
我正在通过Docker进行调查 这是我的输出:
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.470000+0000", :message=>"Reading config file", :config_file=>"/etc/logstash/conf.d/logstash.conf", :level=>:debug, :file=>"logstash/config/loader.rb", :line=>"69", :method=>"local_config"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.570000+0000", :message=>"Plugin not defined in namespace, checking for plugin file", :type=>"output", :name=>"stdout", :path=>"logstash/outputs/stdout", :level=>:debug, :file=>"logstash/plugin.rb", :line=>"86", :method=>"lookup"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.584000+0000", :message=>"starting agent", :level=>:info, :file=>"logstash/agent.rb", :line=>"213", :method=>"execute"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.585000+0000", :message=>"starting pipeline", :id=>"main", :level=>:info, :file=>"logstash/agent.rb", :line=>"487", :method=>"start_pipeline"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.606000+0000", :message=>"Plugin not defined in namespace, checking for plugin file", :type=>"codec", :name=>"rubydebug", :path=>"logstash/codecs/rubydebug", :level=>:debug, :file=>"logstash/plugin.rb", :line=>"86", :method=>"lookup"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.632000+0000", :message=>"config LogStash::Codecs::RubyDebug/@metadata = false", :level=>:debug, :file=>"logstash/config/mixin.rb", :line=>"154", :method=>"config_init"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.789000+0000", :message=>"config LogStash::Outputs::Stdout/@codec = <LogStash::Codecs::RubyDebug metadata=>false>", :level=>:debug, :file=>"logstash/config/mixin.rb", :line=>"154", :method=>"config_init"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.791000+0000", :message=>"config LogStash::Outputs::Stdout/@workers = 1", :level=>:debug, :file=>"logstash/config/mixin.rb", :line=>"154", :method=>"config_init"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.796000+0000", :message=>"Will start workers for output", :worker_count=>1, :class=>"LogStash::Outputs::Stdout", :level=>:debug, :file=>"logstash/output_delegator.rb", :line=>"77", :method=>"register"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.812000+0000", :message=>"Starting pipeline", :id=>"main", :pipeline_workers=>2, :batch_size=>125, :batch_delay=>5, :max_inflight=>250, :level=>:info, :file=>"logstash/pipeline.rb", :line=>"188", :method=>"start_workers"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.816000+0000", :message=>"Pipeline main started", :file=>"logstash/agent.rb", :line=>"491", :method=>"start_pipeline"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.826000+0000", :message=>"Input plugins stopped! Will shutdown filter/output workers.", :level=>:info, :file=>"logstash/pipeline.rb", :line=>"148", :method=>"run"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.935000+0000", :message=>"Pushing flush onto pipeline", :level=>:debug, :file=>"logstash/pipeline.rb", :line=>"458", :method=>"flush"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.942000+0000", :message=>"Pushing shutdown", :thread=>"#<Thread:0x6d334b22 run>", :level=>:debug, :file=>"logstash/pipeline.rb", :line=>"395", :method=>"shutdown_workers"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.946000+0000", :message=>"Pushing shutdown", :thread=>"#<Thread:0x30e6a1db sleep>", :level=>:debug, :file=>"logstash/pipeline.rb", :line=>"395", :method=>"shutdown_workers"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.957000+0000", :message=>"Shutdown waiting for worker thread #<Thread:0x6d334b22>", :level=>:debug, :file=>"logstash/pipeline.rb", :line=>"400", :method=>"shutdown_workers"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.963000+0000", :message=>"Shutdown waiting for worker thread #<Thread:0x30e6a1db>", :level=>:debug, :file=>"logstash/pipeline.rb", :line=>"400", :method=>"shutdown_workers"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.970000+0000", :message=>"closing output delegator", :klass=>"LogStash::Outputs::Stdout", :level=>:debug, :file=>"logstash/output_delegator.rb", :line=>"137", :method=>"do_close"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.972000+0000", :message=>"closing", :plugin=>"LogStash::Outputs::Stdout", :level=>:debug, :file=>"logstash/plugin.rb", :line=>"37", :method=>"do_close"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:31.976000+0000", :message=>"Pipeline main has been shutdown", :file=>"logstash/agent.rb", :line=>"491", :method=>"start_pipeline"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:34.823000+0000", :message=>"stopping pipeline", :id=>"main", :file=>"logstash/agent.rb", :line=>"406", :method=>"shutdown_pipelines"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:34.830000+0000", :message=>"Closing inputs", :level=>:info, :file=>"logstash/pipeline.rb", :line=>"384", :method=>"shutdown"}
logstash_1 | {:timestamp=>"2016-10-25T13:14:34.832000+0000", :message=>"Closed inputs", :level=>:info, :file=>"logstash/pipeline.rb", :line=>"386", :method=>"shutdown"}
它在我运行logstash-tlogstash.conf时检查出来,所以配置文件没有问题
可能是什么问题?
目录meminfo
显示:
MemTotal: 3797716 kB
MemFree: 334368 kB
top - 15:22:36 up 1 day, 1:42, 2 users, load average: 0,52, 0,53, 0,80
Tasks: 298 total, 1 running, 297 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2,1 us, 2,4 sy, 0,0 ni, 94,4 id, 0,2 wa, 0,0 hi, 0,9 si, 0,0 st
KiB Mem : 3797716 total, 325552 free, 1956392 used, 1515772 buff/cache
KiB Swap: 4063228 total, 4059964 free, 3264 used. 1610224 avail Mem
顶部
显示:
MemTotal: 3797716 kB
MemFree: 334368 kB
top - 15:22:36 up 1 day, 1:42, 2 users, load average: 0,52, 0,53, 0,80
Tasks: 298 total, 1 running, 297 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2,1 us, 2,4 sy, 0,0 ni, 94,4 id, 0,2 wa, 0,0 hi, 0,9 si, 0,0 st
KiB Mem : 3797716 total, 325552 free, 1956392 used, 1515772 buff/cache
KiB Swap: 4063228 total, 4059964 free, 3264 used. 1610224 avail Mem
似乎不是硬件问题。
一个奇怪的事情是运行elasticsearch时的日志消息:
elasticsearch_1|[2016-10-25 12:37:01076][WARN][bootstrap]无法安装系统调用筛选器:seccomp不可用:您的内核有缺陷,您应该升级
但这不会对logstash的运行方式产生任何影响,实际上elasticsearch容器运行得很好
编辑:
docker compose.yaml
用于麋鹿堆叠:
##############
## ELK STACK
##############
version: '2'
services:
elasticsearch:
image: 'elasticsearch:latest'
ports:
- "xxxx:xxxx"
networks:
- net
logstash:
build: './logstash_image'
links:
- elasticsearch
ports:
#in1
- "xxxx:xxxx"
#in2
- "xxxx:xxxx"
#in3
- "xxxx:xxxx"
#in4
- "xxxx:xxxx"
#in5
- "xxxx:xxxx"
networks:
- net
# network_mode: host # set up same network values as host (debug only)
# TODO: limit/rotate docker logs:
# https://docs.docker.com/compose/compose-file/#/logopt
# https://docs.docker.com/compose/compose-file/#logdriver
kibana:
image: 'kibana:latest'
ports:
- 'xxxx:xxxx'
links:
- elasticsearch
volumes:
- ./kibana.yml:/opt/kibana/config/kibana.yml
networks:
- net
networks:
net:
driver: bridge
ipam:
driver: default
config:
- subnet: xxx.xxx.xxx.xxx/xx
ip_range: yyy.yyy.yyy.yyy/yy
gateway: zzz.zzz.zzz.zzz
Logstash不会崩溃,它只是退出,因为您的配置文件显式指定了一个空的输入源(input{}
)。日志管道没有任何类型的数据源(默认情况下,它至少将STDIN作为数据源),因此它只是退出
注意用input{}
显式定义空输入与不同不定义任何输入(在这种情况下,Logstash将假定input{stdin{type=>stdin}}
为默认值,并侦听stdin流上的数据输入)
此行为在Logstash的帮助输出(Logstash代理--help
)中定义(强调):
-e CONFIG_STRING
-使用给定字符串作为配置数据。与配置文件的语法相同如果未指定输入,则以下内容将用作默认输入:input{stdin{type=>stdin}}
[…]
Logstash不会崩溃,它只是退出,因为您的配置文件显式指定了一个空的输入源(input{}
)。日志管道没有任何类型的数据源(默认情况下,它至少将STDIN作为数据源),因此它只是退出
注意用input{}
显式定义空输入与不同不定义任何输入(在这种情况下,Logstash将假定input{stdin{type=>stdin}}
为默认值,并侦听stdin流上的数据输入)
此行为在Logstash的帮助输出(Logstash代理--help
)中定义(强调):
-e CONFIG_STRING
-使用给定字符串作为配置数据。与配置文件的语法相同如果未指定输入,则以下内容将用作默认输入:input{stdin{type=>stdin}}
[…]
如何在docker compose.yml中配置logstash?@EltonStoneman我现在将其添加到了问题中,不得不隐藏一些特定于实现的内容,但应该足以解决任何问题。撰写文件顺利通过并运行了容器。如何在docker compose.yml
中配置logstash?@EltonStoneman我现在已将其添加到问题中,必须隐藏一些特定于实现的内容,但应该足以解决任何问题。compose文件顺利通过并运行了容器。我只使用了我作为示例提供的barebonelogstash.conf
,实际上我使用的配置有5个输入源、2个过滤器和1个输出。似乎我在docker compose重建中做错了什么,因此我的新配置从未被复制过,因此错误的配置已经就位。谢谢你帮我解释这一点并帮我排除故障。顺便问一下,使用logstash代理
命令与仅使用logstash
即logstash-e foo
有什么不同?Afaiklogstash agent
是logstash使用的运行时,但我找不到太多相关文档。我只使用了我提供的barebonelogstash.conf
作为示例,实际上我使用的配置有5个输入源、2个过滤器和1个输出。似乎我在docker compose重建中做错了什么,因此我的新配置从未被复制过,因此错误的配置已经就位。谢谢你帮我解释这一点并帮我排除故障。顺便问一下,使用logstash代理
命令与仅使用logstash
即logstash-e foo
有什么不同?Afaiklogstash agent
是logstash使用的运行时,但是我找不到太多关于它的文档。