其他分享
首页 > 其他分享> > Logstash could not be started because there is already another instance using the configured data d

Logstash could not be started because there is already another instance using the configured data d

作者:互联网

[root@localhost logstash-7.12.1]# sudo ./bin/logstash
Using bundled JDK: /usr/local/logstash/logstash-7.12.1/jdk
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Sending Logstash logs to /usr/local/logstash/logstash-7.12.1/logs which is now configured via log4j2.properties
[2021-05-21T14:11:25,816][INFO ][logstash.runner          ] Log4j configuration path used is: /usr/local/logstash/logstash-7.12.1/config/log4j2.properties
[2021-05-21T14:11:25,835][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"7.12.1", "jruby.version"=>"jruby 9.2.13.0 (2.5.7) 2020-08-03 9a89c94bcc OpenJDK 64-Bit Server VM 11.0.10+9 on 11.0.10+9 +indy +jit [linux-x86_64]"}
[2021-05-21T14:11:26,550][FATAL][logstash.runner          ] Logstash could not be started because there is already another instance using the configured data directory.  If you wish to run multiple instances, you must change the "path.data" setting.
[2021-05-21T14:11:26,554][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:747) ~[jruby-complete-9.2.13.0.jar:?]
        at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:710) ~[jruby-complete-9.2.13.0.jar:?]
        at usr.local.logstash.logstash_minus_7_dot_12_dot_1.lib.bootstrap.environment.<main>(/usr/local/logstash/logstash-7.12.1/lib/bootstrap/environment.rb:89) ~[?:?]
[root@localhost logstash-7.12.1]# ls
bin  config  CONTRIBUTORS  data  Gemfile  Gemfile.lock  jdk  lib  LICENSE.txt  logs  logstash-core  logstash-core-plugin-api  modules  NOTICE.TXT  tools  vendor  x-pack
[root@localhost logstash-7.12.1]# cd data
[root@localhost data]# ls -alh
总用量 4.0K
drwxr-xr-x.  5 root wheel  84 5月  13 09:07 .
drwxr-xr-x. 14 root root  278 5月  10 17:00 ..
drwxr-xr-x.  2 root root    6 5月  10 17:00 dead_letter_queue
drwxr-xr-x.  2 root root   37 5月  10 17:39 lastrun
-rw-r--r--.  1 root root    0 5月  13 09:07 .lock
drwxr-xr-x.  3 root root   18 5月  11 14:22 queue
-rw-r--r--.  1 root root   36 5月  10 17:00 uuid
[root@localhost data]# rm .lock
rm:是否删除普通空文件 ".lock"?yes
[root@localhost data]# ls -alh
总用量 4.0K
drwxr-xr-x.  5 root wheel  71 5月  21 14:21 .
drwxr-xr-x. 14 root root  278 5月  10 17:00 ..
drwxr-xr-x.  2 root root    6 5月  10 17:00 dead_letter_queue
drwxr-xr-x.  2 root root   37 5月  10 17:39 lastrun
drwxr-xr-x.  3 root root   18 5月  11 14:22 queue
-rw-r--r--.  1 root root   36 5月  10 17:00 uuid
[root@localhost data]# 
[root@localhost data]# 

标签:10,because,started,data,could,drwxr,xr,root,logstash
来源: https://blog.csdn.net/SuperChen12356/article/details/117120462