主頁 > 作業系統 > CentOS 7.9 安裝 ELK

CentOS 7.9 安裝 ELK

2022-10-13 06:52:08 作業系統

一、CentOS 7.9 安裝 elasticsearch-7.8.1

地址

  • https://www.elastic.co

  • https://www.elastic.co/cn/downloads/past-releases

  • https://github.com/elastic

  • https://github.com/medcl/elasticsearch-analysis-ik
  • https://www.elastic.co/guide/en/logstash/7.8/index.html

 

二、安裝準備

JDK 11+:由于elasticsearch 運行需要JDK環境,如果 JDK 低于 1.8 會有一些問題,

future versions of Elasticsearch will require Java 11; your Java version from [/opt/jdk1.8.0_333/jre] does not meet this requirement

 

版本需要和elasticserach版本一致,否則會報錯

 

三、安裝ElasticSearch

1 下載

wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.8.1-linux-x86_64.tar.gz

2 解壓

tar -zxvf /opt/software/elastic/elasticsearch-7.8.1-linux-x86_64.tar.gz -C /opt/elastic/

3 進入elasticsearch目錄中

目錄中自帶了jdk

4 修改配置:jvm.options

因為默認的jvm引數-Xms和Xmx都是1G,自己搭的虛擬機可能記憶體分配不多,會導致啟動失敗,根據自己的機器情況合理分配,

vim /opt/elastic/elasticsearch-7.8.1/config/jvm.options
################################################################

# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space

-Xms512m
-Xmx512m

################################################################

5 修改配置:elasticsearch.yml

vim /opt/elastic/elasticsearch-7.8.1/config/elasticsearch.yml
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /opt/elastic/es/data # 資料存放位置
#
# Path to log files:
#
path.logs: /opt/elastic/es/logs # 日志存放位置

# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 192.168.0. # 開放外網訪問
#
# Set a custom port for HTTP:
#
http.port: 9200 # 設定埠
#
# For more information, consult the network module documentation.

 

五、ES嘗試啟動

1 require 必須 Java 11

2 運行elasticsearch不能使用root用戶啟動

查看代碼
 [root@ecs-65685 bin]# /opt/elastic/elasticsearch-7.8.1/bin/elasticsearch
future versions of Elasticsearch will require Java 11; your Java version from [/opt/jdk1.8.0_333/jre] does not meet this requirement
future versions of Elasticsearch will require Java 11; your Java version from [/opt/jdk1.8.0_333/jre] does not meet this requirement
[2022-10-11T17:40:42,664][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [ecs-65685] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.RuntimeException: can not run elasticsearch as root
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:174) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) ~[elasticsearch-cli-7.8.1.jar:7.8.1]
	at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.8.1.jar:7.8.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.8.1.jar:7.8.1]
Caused by: java.lang.RuntimeException: can not run elasticsearch as root
	at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:111) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393) ~[elasticsearch-7.8.1.jar:7.8.1]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) ~[elasticsearch-7.8.1.jar:7.8.1]
	... 6 more
uncaught exception in thread [main]
java.lang.RuntimeException: can not run elasticsearch as root
	at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:111)
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178)
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393)
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170)
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161)
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86)
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127)
	at org.elasticsearch.cli.Command.main(Command.java:90)
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126)
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92)
For complete error details, refer to the log at /opt/elastic/es/logs/elasticsearch.log
[root@ecs-65685 bin]# 2022-10-11 09:40:42,993994 UTC [6056] ERROR CLogger.cc@311 Cannot log to named pipe /tmp/elasticsearch-1369077120224648390/controller_log_5893 as it could not be opened for writing
2022-10-11 09:40:42,994085 UTC [6056] INFO  Main.cc@104 Parent process died - ML controller exiting

 

3 創建一個用戶

groupadd es      # 創建一個組
useradd es -g es # 用戶屬于es組
passwd es        # 密碼
# R(遞回)分配目錄下所有檔案/目錄的擁有者
chown -R es:es /opt/elastic/elasticsearch-7.8.1
# 授權存盤資料權限
chmod -R 777 /opt/elastic/es

4 再次啟動es

/opt/elastic/elasticsearch-7.8.1/bin/elasticsearch

 

[1] 說你的系統太low了,給爺增加點增加虛擬記憶體,至少262144

vim /etc/sysctl.conf
vm.max_map_count=655360

# 使設定的虛擬記憶體生效
[root@ecs-65685 config]# sysctl -p
vm.swappiness = 0
net.core.somaxconn = 1024
net.ipv4.tcp_max_tw_buckets = 5000
net.ipv4.tcp_max_syn_backlog = 1024
vm.max_map_count = 655360

[2] 解決:在elasticsearch的config目錄下,修改  elasticsearch.yml組態檔

# 取消注釋,并保留一個節點
# skipping cluster bootstrapping as local node does not match bootstrap requirements: [node-1]
cluster.initial_master_nodes: ["node-1"]

5 再次啟動es

/opt/elastic/elasticsearch-7.8.1/bin/elasticsearch
/opt/elastic/elasticsearch-7.8.1/bin/elasticsearch -d

6 訪問

curl 192.168.0...:9200

公網地址:114.116...:9200

 

注意:放行9200

 

五、Kibana安裝

1 下載

wget https://artifacts.elastic.co/downloads/kibana/kibana-7.8.1-linux-x86_64.tar.gz

2 解壓

tar -zxvf /opt/software/elastic/kibana-7.8.1-linux-x86_64.tar.gz -C /opt/elastic/

3 配置 kibana.yml

vim /opt/elastic/kibana-7.8.1-linux-x86_64/config/kibana.yml
# 埠
server.port: 5601
# 開放外網訪問
server.host: "0.0.0.0" 
# es的服務器
elasticsearch.hosts: ["http://192.168.0...:9200"]

4 啟動

查看代碼
 # 如果是要用root用戶啟動 就在后面加 --allow-root ,要么就切換用戶執行
[root@ecs-65685 bin]# /opt/elastic/kibana-7.8.1-linux-x86_64/bin/kibana
Kibana should not be run as root.  Use --allow-root to continue.

[root@ecs-65685 bin]# /opt/elastic/kibana-7.8.1-linux-x86_64/bin/kibana --allow-root
  log   [17:31:37.776] [warning][plugins-discovery] Expect plugin "id" in camelCase, but found: apm_oss
  log   [17:31:37.787] [warning][plugins-discovery] Expect plugin "id" in camelCase, but found: triggers_actions_ui
  log   [17:32:03.147] [info][plugins-service] Plugin "visTypeXy" is disabled.
  log   [17:32:03.148] [info][plugins-service] Plugin "endpoint" is disabled.
  log   [17:32:03.148] [info][plugins-service] Plugin "ingestManager" is disabled.
  log   [17:32:03.149] [info][plugins-service] Plugin "lists" is disabled.
  log   [17:32:05.837] [warning][config][deprecation] Config key [monitoring.cluster_alerts.email_notifications.email_address] will be required for email notifications to work in 8.0."
  log   [17:32:05.904] [info][plugins-system] Setting up [94] plugins: [taskManager,licensing,observability,eventLog,encryptedSavedObjects,code,usageCollection,ossTelemetry,telemetryCollectionManager,telemetry,telemetryCollectionXpack,kibanaLegacy,devTools,translations,uiActions,statusPage,share,newsfeed,mapsLegacy,mapsLegacyLicensing,kibanaUtils,kibanaReact,inspector,embeddable,advancedUiActions,embeddableEnhanced,drilldowns,indexPatternManagement,esUiShared,discover,charts,bfetch,expressions,data,home,cloud,console,consoleExtensions,apm_oss,searchprofiler,painlessLab,grokdebugger,management,upgradeAssistant,reporting,licenseManagement,indexManagement,remoteClusters,crossClusterReplication,indexLifecycleManagement,watcher,advancedSettings,telemetryManagementSection,fileUpload,dataEnhanced,visualizations,visTypeVislib,visTypeVega,visTypeTimeseries,rollup,visTypeTimelion,features,security,snapshotRestore,transform,ingestPipelines,canvas,visTypeTagcloud,visTypeTable,visTypeMetric,visTypeMarkdown,inputControlVis,savedObjects,navigation,lens,graph,maps,visualize,dashboard,dashboardEnhanced,savedObjectsManagement,spaces,actions,case,alerting,alertingBuiltins,triggers_actions_ui,infra,monitoring,logstash,uptime,ml,siem,apm]
  log   [17:32:05.914] [warning][config][encryptedSavedObjects][plugins] Generating a random key for xpack.encryptedSavedObjects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml
  log   [17:32:06.058] [warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml
  log   [17:32:06.059] [warning][config][plugins][security] Session cookies will be transmitted over insecure connections. This is not recommended.
  log   [17:32:06.109] [warning][actions][actions][plugins] APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml.
  log   [17:32:06.122] [warning][alerting][alerting][plugins][plugins] APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml.
  log   [17:32:06.149] [info][monitoring][monitoring][plugins] config sourced from: production cluster
  log   [17:32:06.150] [warning][monitoring][monitoring][plugins] X-Pack Monitoring Cluster Alerts will not be available: undefined
  log   [17:32:06.188] [info][crossClusterReplication][plugins] Your basic license does not support crossClusterReplication. Please upgrade your license.
  log   [17:32:06.189] [info][plugins][watcher] Your basic license does not support watcher. Please upgrade your license.
  log   [17:32:06.196] [info][kibana-monitoring][monitoring][monitoring][plugins] Starting monitoring stats collection
  log   [17:32:06.393] [info][savedobjects-service] Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations...
  log   [17:32:06.412] [info][savedobjects-service] Starting saved objects migrations
  log   [17:32:06.447] [info][savedobjects-service] Creating index .kibana_task_manager_1.
  log   [17:32:06.450] [info][savedobjects-service] Creating index .kibana_1.
  log   [17:32:06.899] [info][savedobjects-service] Pointing alias .kibana_task_manager to .kibana_task_manager_1.
  log   [17:32:06.947] [info][savedobjects-service] Pointing alias .kibana to .kibana_1.
  log   [17:32:06.999] [info][savedobjects-service] Finished in 552ms.
  log   [17:32:07.022] [info][savedobjects-service] Finished in 577ms.
  log   [17:32:07.025] [info][plugins-system] Starting [72] plugins: [taskManager,licensing,observability,eventLog,encryptedSavedObjects,code,usageCollection,ossTelemetry,telemetryCollectionManager,telemetry,telemetryCollectionXpack,kibanaLegacy,translations,share,discover,bfetch,expressions,data,home,cloud,console,consoleExtensions,apm_oss,searchprofiler,painlessLab,grokdebugger,management,upgradeAssistant,reporting,licenseManagement,indexManagement,remoteClusters,crossClusterReplication,indexLifecycleManagement,watcher,advancedSettings,fileUpload,dataEnhanced,visualizations,visTypeVislib,visTypeVega,visTypeTimeseries,rollup,visTypeTimelion,features,security,snapshotRestore,transform,ingestPipelines,canvas,visTypeTagcloud,visTypeTable,visTypeMetric,visTypeMarkdown,inputControlVis,lens,graph,visualize,dashboard,savedObjectsManagement,spaces,actions,case,alerting,alertingBuiltins,infra,monitoring,logstash,uptime,ml,siem,apm]
  log   [17:32:09.117] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:09.121] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:32:09.121] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready
  log   [17:32:09.123] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:09.133] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:09.136] [warning][plugins][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.reporting.encryptionKey in kibana.yml
  log   [17:32:09.138] [warning][plugins][reporting] Chromium sandbox provides an additional layer of protection, but is not supported for Linux Centos 7.9.2009 OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'.
  log   [17:32:09.139] [warning][reporting] Enabling the Chromium sandbox provides an additional layer of protection.
  log   [17:32:10.356] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.383] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.385] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.391] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.393] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.438] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.446] [info][plugins][taskManager][taskManager] TaskManager is identified by the Kibana UUID: 66a6ab9a-0339-47c1-9fa8-ef059a59152e
  log   [17:32:10.449] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.451] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.454] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.456] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.459] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.464] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [17:32:10.470] [info][listening] Server running at http://192.168.0...:5601
  log   [17:32:10.901] [info][server][Kibana][http] http server running at http://192.168.0...:5601

5 瀏覽器訪問:IP:5601

 

六、elasticsearch-analysis-ik 分詞器插件安裝

作用:如果直接使用Elasticsearch的分詞器在處理中文內容的搜索時,ES會將中文詞語分成一個一個的漢字,當用Kibana作圖,按照term來分組的時候,也會將一個漢字單獨分成一組,這對于我們的使用是及其不方便的,因此我們引入es之中文的分詞器插件es-ik就能解決這個問題,

1 elasticsearch-analysis-ik分詞器下載地址:https://github.com/medcl/elasticsearch-analysis-ik/releases

2 創建分詞器目錄

分詞器安裝在ES目錄下即可,所有在ES目錄下創建分詞器目錄

mkdir /opt/elastic/elasticsearch-7.8.1/plugins/ik

3 解壓安裝包

unzip /opt/software/elastic/elasticsearch-analysis-ik-7.8.1.zip -d /opt/elastic/elasticsearch-7.8.1/plugins/ik/

4 重新對ES目錄授權

chown -R es:es /opt/elastic/elasticsearch-7.8.1

5 關閉ES和Kibana

可以先通過Kill命令殺掉ES和Kibana行程

ps -ef | grep elastic
kill -9

6 啟動

/opt/elastic/elasticsearch-7.8.1/bin/elasticsearch -d
/opt/elastic/kibana-7.8.1-linux-x86_64/bin/kibana

此時的ES日志是可以查看到是有加載分詞器插件的

 

七、Logstash安裝

1 下載

wget https://artifacts.elastic.co/downloads/logstash/logstash-7.8.1.tar.gz

2 解壓

tar -zxvf /opt/software/elastic/logstash-7.8.1.tar.gz -C /opt/elastic/

3 配置 logstash.yml

vim  /opt/elastic/logstash-7.8.1/config/logstash.yml

系統配置不高可以適當減少

4 啟動

  • -t 測驗組態檔是否正確,
  • -f 指定logstash的組態檔,

  • -e 格式是后面跟字串,這個字串就被當做是logstash的配置,如果"",那么默認使用stdin作為輸出,

logstash啟動命令位于安裝路徑的bin目錄中,直接啟動會報錯,需要按照如下方式提供引數,

命令列啟動日志中看到 "Successfully started Logstash API endpoint {:port=>9600}" ,就說明啟動成功,

上面命令列定義的是一個標準輸入插件(即 stdin)和一個標準輸出插件(即 stdout),

意思就是從命令列提取輸入,并從命令列直接將提取的資料輸出,可以測驗下,啟動后如下圖,界面在等待輸入,

/opt/elastic/logstash-7.8.1/bin/logstash -e "input {stdin {}} output {stdout {}}"

5 連接 Elasticsearch

logstash可以通過命令列并使用 -e 引數傳入配置字串,指定了標準輸入 stdin 插件和 stdout 插件,

但在實際應用中,通常使用組態檔指定插件,組態檔的語法形式與命令列相同,要使用的插件名稱來指定,一般組態檔均放置到部署目錄的config目錄中,配置中找到名為 logstash-sample.conf 的檔案,也可新建組態檔

啟動組態檔 logstash-sample.conf

vim /opt/elastic/logstash-7.8.1/config/logstash-sample.conf 
input {
  file {
    type => "systemlog-xyz"  #標簽
    path => "/opt/elastic/logstash/logs/xyz"  #采集點
    start_position => "beginning"  #開始收集點
    stat_interval => "2"  #掃描間隔時間,默認是1s,建議5s
  }
}

output {
  elasticsearch {
    hosts => ["192.168.0.98:9200"]  #指定資訊發送到es
    index => "app-xyz-log-%{+YYYY.MM.dd}"  #定義格式
 }
  file {
    path => "/opt/elastic/logstash/logs/xyz/xyz.log"
  }
}

6 啟動命令

/opt/elastic/logstash-7.8.1/bin/logstash -f ../config/logstash-sample.conf -t
/opt/elastic/logstash-7.8.1/bin/logstash -f ../config/logstash-sample.conf

 

八、Filebeat安裝

下載

wget https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.8.1-linux-x86_64.tar.gz

 

解壓

tar -zxvf /opt/software/elastic/filebeat-7.8.1-linux-x86_64.tar.gz -C /opt/elastic/
ll /opt/elastic/filebeat-7.8.1-linux-x86_64/

 

 

 

 

 

 

 

 

 

 

 

 

報錯

1 failed; error='Not enough space

虛擬機記憶體不足,修改虛擬機分配記憶體大小的引數是,-Xmx和-Xms

[es@ecs-65685 ~]$ /opt/elastic/elasticsearch-7.8.1/bin/elasticsearch
Exception in thread "main" java.lang.RuntimeException: starting java failed with [1]
output:
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 549755813888 bytes for committing reserved memory.
# An error report file with more information is saved as:
# logs/hs_err_pid12013.log
error:
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f38ee000000, 549755813888, 0) failed; error='Not enough space' (errno=12)
	at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:126)
	at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:88)
	at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:59)
	at org.elasticsearch.tools.launchers.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:137)
	at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:95)
[es@ecs-65685 ~]$ 

 

2 Permission denied

es用戶啟動 elasticsearch時,es目錄沒有權限:chmod -R 777 /opt/elastic/es

[es@ecs-65685 ~]$ /opt/elastic/elasticsearch-7.8.1/bin/elasticsearch
2022-10-11 23:54:04,818 main ERROR RollingFileManager (/opt/elastic/es/logs/elasticsearch_deprecation.log) java.io.FileNotFoundException: /opt/elastic/es/logs/elasticsearch_deprecation.log (Permission denied) java.io.FileNotFoundException: /opt/elastic/es/logs/elasticsearch_deprecation.log (Permission denied)
	at java.base/java.io.FileOutputStream.open0(Native Method)
	at java.base/java.io.FileOutputStream.open(FileOutputStream.java:291)
	at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:234)
	at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:155)

 

 

3 logstash直接啟動會報錯

[root@ecs-65685 ~]# /opt/elastic/logstash-7.8.1/bin/logstash
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.headius.backport9.modules.Modules (file:/opt/elastic/logstash-7.8.1/logstash-core/lib/jars/jruby-complete-9.2.11.1.jar) to method sun.nio.ch.NativeThread.signal(long)
WARNING: Please consider reporting this to the maintainers of com.headius.backport9.modules.Modules
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Sending Logstash logs to /opt/elastic/logstash-7.8.1/logs which is now configured via log4j2.properties
ERROR: Pipelines YAML file is empty. Location: /opt/elastic/logstash-7.8.1/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
[2022-10-12T14:31:11,184][ERROR][org.logstash.Logstash    ] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

 

 

 

 

 

 

 

 

 

 

 

 

轉載請註明出處,本文鏈接:https://www.uj5u.com/caozuo/514041.html

標籤:其他

上一篇:引論(一)

下一篇:谷歌瀏覽器Chrome時無法翻譯如何解決?

標籤雲
其他(157675) Python(38076) JavaScript(25376) Java(17977) C(15215) 區塊鏈(8255) C#(7972) AI(7469) 爪哇(7425) MySQL(7132) html(6777) 基礎類(6313) sql(6102) 熊猫(6058) PHP(5869) 数组(5741) R(5409) Linux(5327) 反应(5209) 腳本語言(PerlPython)(5129) 非技術區(4971) Android(4554) 数据框(4311) css(4259) 节点.js(4032) C語言(3288) json(3245) 列表(3129) 扑(3119) C++語言(3117) 安卓(2998) 打字稿(2995) VBA(2789) Java相關(2746) 疑難問題(2699) 细绳(2522) 單片機工控(2479) iOS(2429) ASP.NET(2402) MongoDB(2323) 麻木的(2285) 正则表达式(2254) 字典(2211) 循环(2198) 迅速(2185) 擅长(2169) 镖(2155) 功能(1967) .NET技术(1958) Web開發(1951) python-3.x(1918) HtmlCss(1915) 弹簧靴(1913) C++(1909) xml(1889) PostgreSQL(1872) .NETCore(1853) 谷歌表格(1846) Unity3D(1843) for循环(1842)

熱門瀏覽
  • CA和證書

    1、在 CentOS7 中使用 gpg 創建 RSA 非對稱密鑰對 gpg --gen-key #Centos上生成公鑰/密鑰對(存放在家目錄.gnupg/) 2、將 CentOS7 匯出的公鑰,拷貝到 CentOS8 中,在 CentOS8 中使用 CentOS7 的公鑰加密一個檔案 gpg -a ......

    uj5u.com 2020-09-10 00:09:53 more
  • Kubernetes K8S之資源控制器Job和CronJob詳解

    Kubernetes的資源控制器Job和CronJob詳解與示例 ......

    uj5u.com 2020-09-10 00:10:45 more
  • VMware下安裝CentOS

    VMware下安裝CentOS 一、軟硬體準備 1 Centos鏡像準備 1.1 CentOS鏡像下載地址 下載地址 1.2 CentOS鏡像下載程序 點擊下載地址進入如下圖的網站,選擇需要下載的版本,這里選擇的是Centos8,點擊如圖所示。 決定選擇Centos8后,選擇想要的鏡像源進行下載,此 ......

    uj5u.com 2020-09-10 00:12:10 more
  • 如何使用Grep命令查找多個字串

    如何使用Grep 命令查找多個字串 大家好,我是良許! 今天向大家介紹一個非常有用的技巧,那就是使用 grep 命令查找多個字串。 簡單介紹一下,grep 命令可以理解為是一個功能強大的命令列工具,可以用它在一個或多個輸入檔案中搜索與正則運算式相匹配的文本,然后再將每個匹配的文本用標準輸出的格式 ......

    uj5u.com 2020-09-10 00:12:28 more
  • git配置http代理

    git配置http代理 經常遇到克隆 github 慢的問題,這里記錄一下幾種配置 git 代理的方法,解決 clone github 過慢。 目錄 git配置代理 git單獨配置github代理 git配置全域代理 配置終端環境變數 git配置代理 主要使用 git config 命令 git單獨 ......

    uj5u.com 2020-09-10 00:12:33 more
  • Linux npm install 裝包時提示Error EACCES permission denied解

    npm install 裝包時提示Error EACCES permission denied解決辦法 ......

    uj5u.com 2020-09-10 00:12:53 more
  • Centos 7下安裝nginx,使用yum install nginx,提示沒有可用的軟體包

    Centos 7下安裝nginx,使用yum install nginx,提示沒有可用的軟體包。 18 (flaskApi) [root@67 flaskDemo]# yum -y install nginx 19 已加載插件:fastestmirror, langpacks 20 Loading ......

    uj5u.com 2020-09-10 00:13:13 more
  • Linux查看服務器暴力破解ssh IP

    在公網的服務器上經常遇到別人爆破你服務器的22埠,用來挖礦或者干其他嘿嘿嘿的事情~ 這種情況下正確的做法是: 修改默認ssh的22埠 使用設定密鑰登錄或者白名單ip登錄 建議服務器密碼為復雜密碼 創建普通用戶登錄服務器(root權限過大) 建立堡壘機,實作統一管理服務器 統計爆破IP [root ......

    uj5u.com 2020-09-10 00:13:17 more
  • CentOS 7系統常見快捷鍵操作方式

    Linux系統中一些常見的快捷方式,可有效提高操作效率,在某些時刻也能避免操作失誤帶來的問題。 ......

    uj5u.com 2020-09-10 00:13:31 more
  • CentOS 7作業系統目錄結構介紹

    作業系統存在著大量的資料檔案資訊,相應檔案資訊會存在于系統相應目錄中,為了更好的管理資料資訊,會將系統進行一些目錄規劃,不同目錄存放不同的資源。 ......

    uj5u.com 2020-09-10 00:13:35 more
最新发布
  • vim的常用命令

    Vim的6種基本模式 1. 普通模式在普通模式中,用的編輯器命令,比如移動游標,洗掉文本等等。這也是Vim啟動后的默認模式。這正好和許多新用戶期待的操作方式相反(大多數編輯器默認模式為插入模式)。 2. 插入模式在這個模式中,大多數按鍵都會向文本緩沖中插入文本。大多數新用戶希望文本編輯器編輯程序中一 ......

    uj5u.com 2023-04-20 08:43:21 more
  • vim的常用命令

    Vim的6種基本模式 1. 普通模式在普通模式中,用的編輯器命令,比如移動游標,洗掉文本等等。這也是Vim啟動后的默認模式。這正好和許多新用戶期待的操作方式相反(大多數編輯器默認模式為插入模式)。 2. 插入模式在這個模式中,大多數按鍵都會向文本緩沖中插入文本。大多數新用戶希望文本編輯器編輯程序中一 ......

    uj5u.com 2023-04-20 08:42:36 more
  • docker學習

    ###Docker概述 真實專案部署環境可能非常復雜,傳統發布專案一個只需要一個jar包,運行環境需要單獨部署。而通過Docker可將jar包和相關環境(如jdk,redis,Hadoop...)等打包到docker鏡像里,將鏡像發布到Docker倉庫,部署時下載發布的鏡像,直接運行發布的鏡像即可。 ......

    uj5u.com 2023-04-19 09:26:53 more
  • 設定Windows主機的瀏覽器為wls2的默認瀏覽器

    這里以Chrome為例。 1. 準備作業 wsl是可以使用Windows主機上安裝的exe程式,出于安全考慮,默認情況下改功能是無法使用。要使用的話,終端需要以管理員權限啟動。 我這里以Windows Terminal為例,介紹如何默認使用管理員權限打開終端,具體操作如下圖所示: 2. 操作 wsl ......

    uj5u.com 2023-04-19 09:25:49 more
  • docker學習

    ###Docker概述 真實專案部署環境可能非常復雜,傳統發布專案一個只需要一個jar包,運行環境需要單獨部署。而通過Docker可將jar包和相關環境(如jdk,redis,Hadoop...)等打包到docker鏡像里,將鏡像發布到Docker倉庫,部署時下載發布的鏡像,直接運行發布的鏡像即可。 ......

    uj5u.com 2023-04-19 09:19:04 more
  • Linux學習筆記

    IP地址和主機名 IP地址 ifconfig可以用來查詢本機的IP地址,如果不能使用,可以通過install net-tools安裝。 Centos系統下ens33表示主網卡;inet后表示IP地址;lo表示本地回環網卡; 127.0.0.1表示代指本機;0.0.0.0可以用于代指本機,同時在放行設 ......

    uj5u.com 2023-04-18 06:52:01 more
  • 解決linux系統的kdump服務無法啟動的問題

    問題:專案麒麟系統服務器的kdump服務無法啟動,沒有相關日志無法定位問題。 1、查看服務狀態是關閉的,重啟系統也無法啟動 systemctl status kdump 2、修改grub引數,修改“crashkernel”為“512M(有的機器數值太大太小都會導致報錯,建議從128M開始試,或者加個 ......

    uj5u.com 2023-04-12 09:59:50 more
  • 解決linux系統的kdump服務無法啟動的問題

    問題:專案麒麟系統服務器的kdump服務無法啟動,沒有相關日志無法定位問題。 1、查看服務狀態是關閉的,重啟系統也無法啟動 systemctl status kdump 2、修改grub引數,修改“crashkernel”為“512M(有的機器數值太大太小都會導致報錯,建議從128M開始試,或者加個 ......

    uj5u.com 2023-04-12 09:59:01 more
  • 你是不是暴露了?

    作者:袁首京 原創文章,轉載時請保留此宣告,并給出原文連接。 如果您是計算機相關從業人員,那么應該經歷不止一次網路安全專項檢查了,你肯定是收到過資訊系統技術檢測報告,要求你加強風險監測,確保你提供的系統服務堅實可靠了。 沒檢測到問題還好,檢測到問題的話,有些處理起來還是挺麻煩的,尤其是線上正在運行的 ......

    uj5u.com 2023-04-05 16:52:56 more
  • 細節拉滿,80 張圖帶你一步一步推演 slab 記憶體池的設計與實作

    1. 前文回顧 在之前的幾篇記憶體管理系列文章中,筆者帶大家從宏觀角度完整地梳理了一遍 Linux 記憶體分配的整個鏈路,本文的主題依然是記憶體分配,這一次我們會從微觀的角度來探秘一下 Linux 內核中用于零散小記憶體塊分配的記憶體池 —— slab 分配器。 在本小節中,筆者還是按照以往的風格先帶大家簡單 ......

    uj5u.com 2023-04-05 16:44:11 more