CentOS 7.9 安裝 ELK (補)

来源:https://www.cnblogs.com/huaxiayuyi/archive/2022/10/12/16778890.html
-Advertisement-
Play Games

一、CentOS 7.9 安裝 elasticsearch-7.8.1 地址 https://www.elastic.co https://www.elastic.co/cn/downloads/past-releases https://github.com/elastic https://git ...


一、CentOS 7.9 安裝 elasticsearch-7.8.1

地址

 

二、安裝準備

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

 

 

 

 

 

 

 

 

 

 

 

 


您的分享是我們最大的動力!

-Advertisement-
Play Games
更多相關文章
  • 在最新版的 .NET 平臺中,微軟在逐步放棄 System.Drawing.Imaging ,給出的理由如下: System.Drawing命名空間對某些操作系統和應用程式類型有一些限制。 在Windows, System.Drawing 依賴於GDI+操作系統附帶的本機庫。 某些Windows S ...
  • 支持.NET/.NET Framework/.NET Core RabbitMQ作為一款主流的消息隊列工具早已廣受歡迎。相比於其它的MQ工具,RabbitMQ支持的語言更多、功能更完善。 本文提供一種市面上最/極簡單的使用RabbitMQ的方式,只需要會調用以下三個方法,你就幾乎可以掌握整個Rabb ...
  • 一:背景 1.講故事 前段時間有位朋友微信找到我,說他的程式出現了 CPU 爆高,幫忙看下程式到底出了什麼情況?圖就不上了,我們直接進入主題。 二:WinDbg 分析 1. CPU 真的爆高嗎? 要確認是否真的爆高,可以使用 !tp 觀察。 0:000> !tp CPU utilization: 9 ...
  • 最近在學著使用blackwidow這個工具,在ubuntu20.02系統的安裝過程當中遇到了selenium使用的一些問題。 selenium是個什麼工具? Selenium是一個用於Web應用程式測試的工具。Selenium測試直接運行在瀏覽器中,就像真正的用戶在操作一樣。支持的瀏覽器包括IE(7 ...
  • Ubuntu官網會給各種公有雲平臺提供cloud鏡像, 例如AWS, MS Azure, Google Cloud, 以及本地虛機環境例如 QEMU, VMware, Vagrant等, 這些鏡像在 https://cloud-images.ubuntu.com 上可以下載. 這裡說明如何在 KVM... ...
  • 最近在配置Linux系統的ntp校時,涉及到開機啟動問題,總結一下 兩個環境: CentOS release 6.5 (Final) CentOS Linux release 7.9.2009 (Core) centos6.5 設置開機啟動使用chkconfig方式 chkconfig 是設置服務在 ...
  • nginx訪問控制,用戶認證,配置https,zabbix監控nginx狀態頁面 nginx訪問控制 用於location段 allow:設定允許哪台或哪些主機訪問,多個參數間用空格隔開 deny: 設定禁止哪台或哪些主機訪問,多個參數間用空格隔開 //測試 [root@nginx ~]# cd / ...
  • 1、進程結構特征: >>進程式控制制塊的作用: 動態性 進程最基本的特征是動態性 進程的生命周期 進程由創建而產生,由調度而執行,由撤銷而消亡的過程 併發性 獨立性 非同步性 2、進程的三種基本狀態 就緒狀態 執行狀態 阻塞狀態 ...
一周排行
    -Advertisement-
    Play Games
  • 移動開發(一):使用.NET MAUI開發第一個安卓APP 對於工作多年的C#程式員來說,近來想嘗試開發一款安卓APP,考慮了很久最終選擇使用.NET MAUI這個微軟官方的框架來嘗試體驗開發安卓APP,畢竟是使用Visual Studio開發工具,使用起來也比較的順手,結合微軟官方的教程進行了安卓 ...
  • 前言 QuestPDF 是一個開源 .NET 庫,用於生成 PDF 文檔。使用了C# Fluent API方式可簡化開發、減少錯誤並提高工作效率。利用它可以輕鬆生成 PDF 報告、發票、導出文件等。 項目介紹 QuestPDF 是一個革命性的開源 .NET 庫,它徹底改變了我們生成 PDF 文檔的方 ...
  • 項目地址 項目後端地址: https://github.com/ZyPLJ/ZYTteeHole 項目前端頁面地址: ZyPLJ/TreeHoleVue (github.com) https://github.com/ZyPLJ/TreeHoleVue 目前項目測試訪問地址: http://tree ...
  • 話不多說,直接開乾 一.下載 1.官方鏈接下載: https://www.microsoft.com/zh-cn/sql-server/sql-server-downloads 2.在下載目錄中找到下麵這個小的安裝包 SQL2022-SSEI-Dev.exe,運行開始下載SQL server; 二. ...
  • 前言 隨著物聯網(IoT)技術的迅猛發展,MQTT(消息隊列遙測傳輸)協議憑藉其輕量級和高效性,已成為眾多物聯網應用的首選通信標準。 MQTTnet 作為一個高性能的 .NET 開源庫,為 .NET 平臺上的 MQTT 客戶端與伺服器開發提供了強大的支持。 本文將全面介紹 MQTTnet 的核心功能 ...
  • Serilog支持多種接收器用於日誌存儲,增強器用於添加屬性,LogContext管理動態屬性,支持多種輸出格式包括純文本、JSON及ExpressionTemplate。還提供了自定義格式化選項,適用於不同需求。 ...
  • 目錄簡介獲取 HTML 文檔解析 HTML 文檔測試參考文章 簡介 動態內容網站使用 JavaScript 腳本動態檢索和渲染數據,爬取信息時需要模擬瀏覽器行為,否則獲取到的源碼基本是空的。 本文使用的爬取步驟如下: 使用 Selenium 獲取渲染後的 HTML 文檔 使用 HtmlAgility ...
  • 1.前言 什麼是熱更新 游戲或者軟體更新時,無需重新下載客戶端進行安裝,而是在應用程式啟動的情況下,在內部進行資源或者代碼更新 Unity目前常用熱更新解決方案 HybridCLR,Xlua,ILRuntime等 Unity目前常用資源管理解決方案 AssetBundles,Addressable, ...
  • 本文章主要是在C# ASP.NET Core Web API框架實現向手機發送驗證碼簡訊功能。這裡我選擇是一個互億無線簡訊驗證碼平臺,其實像阿裡雲,騰訊雲上面也可以。 首先我們先去 互億無線 https://www.ihuyi.com/api/sms.html 去註冊一個賬號 註冊完成賬號後,它會送 ...
  • 通過以下方式可以高效,並保證數據同步的可靠性 1.API設計 使用RESTful設計,確保API端點明確,並使用適當的HTTP方法(如POST用於創建,PUT用於更新)。 設計清晰的請求和響應模型,以確保客戶端能夠理解預期格式。 2.數據驗證 在伺服器端進行嚴格的數據驗證,確保接收到的數據符合預期格 ...