【问题标题】:ELK data pod keep on getting into crashloopbackoffELK 数据 pod 不断进入 crashloopbackoff
【发布时间】:2021-05-15 01:17:39
【问题描述】:

我已经在 k8s 上实现了 ELK,但是我的数据 pod 不断进入 crashloopbackoff 状态。

[]$ kubectl get pod -n  es
NAME                                               READY   STATUS             RESTARTS   AGE
logging-es-opendistro-es-client-76ff944d-rwjvz     1/1     Running            0          134m
logging-es-opendistro-es-data-0                    0/1     CrashLoopBackOff   3          18m
logging-es-opendistro-es-data-1                    0/1     Init:1/2           0          5m24s
logging-es-opendistro-es-kibana-5cfbd8dc49-g5rdl   1/1     Running            0          39m
logging-es-opendistro-es-master-0                  1/1     Running            0          134m
logging-es-opendistro-es-master-1                  1/1     Running            0          127m


Logs from data pod
[2021-02-15T08:02:46,683][INFO ][o.e.p.PluginsService     ] [logging-es-opendistro-es-data-1] loaded plugin [opendistro_security]
[2021-02-15T08:02:46,683][INFO ][o.e.p.PluginsService     ] [logging-es-opendistro-es-data-1] loaded plugin [opendistro_sql]
[2021-02-15T08:02:47,027][INFO ][o.e.e.NodeEnvironment    ] [logging-es-opendistro-es-data-1] using [1] data paths, mounts [[/usr/share/elasticsearch/data (//fbeff48040de841b395c700.file.core.windows.net/kubernetes-dynamic-pvc-0f5e7e46-5138-0dfbe0aadff3)]], net usable_space [37.1gb], net total_space [50gb], types [cifs]
[2021-02-15T08:02:47,027][INFO ][o.e.e.NodeEnvironment    ] [logging-es-opendistro-es-data-1] heap size [4gb], compressed ordinary object pointers [true]

【问题讨论】:

标签: elasticsearch kubernetes elk


【解决方案1】:

Failed to pull image "/infrastructure/busybox:1.27.2"。您的图像名称看起来不对。图片名称不应以 / 开头。

如果您需要从特定注册表中获取图像,可以查看此doc

【讨论】:

  • 图片网址没问题
猜你喜欢
  • 2021-05-05
  • 1970-01-01
  • 2018-12-10
  • 1970-01-01
  • 1970-01-01
  • 2020-02-28
  • 2020-10-28
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多