kubernetes安装elasticsearch状态显示CrashLoopBackOff解决

最新推荐文章于 2024-05-07 10:53:47 发布
最新推荐文章于 2024-05-07 10:53:47 发布
阅读量3.4k 收藏 2
点赞数
分类专栏： kubernetes elasticsearch
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Tilyp/article/details/84961513
版权

 在利用kubernetes安装elasticsearch时遇到如下错误，我在安装之前已经在各个节点上测试镜像能否正常拉取

[root@dmp-dn-001 /]# docker pull docker.elastic.co/elasticsearch/elasticsearch:6.2.4
Trying to pull repository docker.elastic.co/elasticsearch/elasticsearch ... 
6.2.4: Pulling from docker.elastic.co/elasticsearch/elasticsearch
469cfcc7a4b3: Downloading  5.36 MB/73.17 MB
8e27facfa9e0: Downloading 5.386 MB/56.33 MB
cdd15392adc7: Download complete 
ddcc70fbd933: Downloading 4.315 MB/108.9 MB
3d3fa0383994: Waiting 
15d1376ebd55: Waiting 
^C^C^]^]^]
[root@dmp-dn-001 /]

 可以看到是可以正常拉取的，那这个时候就通过elasticsearch.yaml创建pod

vim elasticsearch.yaml

apiVersion: v1
kind: ReplicationController
metadata:
  name: elasticsearch 
  labels:
    name: elasticsearch-logging
    kubernetes.io/cluster-service: "true"
spec:
  replicas: 1
  selector:
    name: elasticsearch-logging
  template:
    metadata:
      name: es
      labels:
        name: elasticsearch-logging
        kubernetes.io/cluster-service: "true"
    spec:
      containers:
        - image: docker.elastic.co/elasticsearch/elasticsearch:6.2.4 
          # imagePullPolicy: Never
          name: elasticsearch-logging
          ports:
            - name: es-port
              containerPort: 9200
            - name: es-tran-port
              containerPort: 9300
          volumeMounts:
            - name: es-persistent-storage
              mountPath: /data
      volumes:
        - name: es-persistent-storage
          emptyDir: {}

 在节点机上已经创建好/data目录，这时创建该pod

[root@master elasticsearchyaml]# kubectl apply -f elasticsearch.yaml 
replicationcontroller "elasticsearch" created
[root@master elasticsearchyaml]#

查看创建的pod

[root@master elasticsearchyaml]# kubectl get pods
NAME                  READY     STATUS              RESTARTS   AGE
elasticsearch-dmrkr   0/1       ContainerCreating   0          8s
mysql-flf48           1/1       Running             2          1d
[root@master elasticsearchyaml]#

 过了一会镜像下载完成后pod的状态就变成`CrashLoopBackOff`了

[root@master elasticsearchyaml]# kubectl get pods
NAME                  READY     STATUS             RESTARTS   AGE
elasticsearch-wvw3s   0/1       CrashLoopBackOff   4          3m
mysql-flf48           1/1       Running            2          1d
[root@master elasticsearchyaml]#

 通过describe查看该pod发现如下错误，大概意思就是es的container启动失败 ：

Error syncing pod, skipping: failed to "StartContainer" for "elasticsearch-logging" with CrashLoopBackOff: "Back-off 10s restarting failed container=elasticsearch-logging pod=elasticsearch-dmrkr_default(e986d851-fd40-11e8-be8c-1866dae7200c)"

 于是我在该pod所在节点手动启动给镜像，

[root@dmp-dn-001 /]# docker images
REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
docker.io/mysql                                       5.7                 702fb0b7837f        6 weeks ago         372 MB
docker.io/mysql                                       latest              2dd01afbe8df        6 weeks ago         485 MB
docker.elastic.co/elasticsearch/elasticsearch         6.2.4               7cb69da7148d        8 months ago        515 MB
registry.access.redhat.com/rhel7/pod-infrastructure   latest              99965fb98423        14 months ago       209 MB
[root@dmp-dn-001 /]# docker run 7cb69da7148d
[2018-12-11T12:33:50,380][INFO ][o.e.n.Node               ] [] initializing ...
[2018-12-11T12:33:50,427][INFO ][o.e.e.NodeEnvironment    ] [QwRx60a] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [81.9gb], net total_space [99.9gb], types [rootfs]
[2018-12-11T12:33:50,427][INFO ][o.e.e.NodeEnvironment    ] [QwRx60a] heap size [989.8mb], compressed ordinary object pointers [true]
[2018-12-11T12:33:50,430][INFO ][o.e.n.Node               ] node name [QwRx60a] derived from node ID [QwRx60alQq6W6JvCifhBoA]; set [node.name] to override
[2018-12-11T12:33:50,430][INFO ][o.e.n.Node               ] version[6.2.4], pid[1], build[ccec39f/2018-04-12T20:37:28.497551Z], OS[Linux/3.10.0-327.el7.x86_64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_161/25.161-b14]
[2018-12-11T12:33:50,430][INFO ][o.e.n.Node               ] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.6qHwOYNF, -XX:+HeapDumpOnOutOfMemoryError, -XX:+PrintGCDetails, -XX:+PrintGCDateStamps, -XX:+PrintTenuringDistribution, -XX:+PrintGCApplicationStoppedTime, -Xloggc:logs/gc.log, -XX:+UseGCLogFileRotation, -XX:NumberOfGCLogFiles=32, -XX:GCLogFileSize=64m, -Des.cgroups.hierarchy.override=/, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [aggs-matrix-stats]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [analysis-common]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [ingest-common]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [lang-expression]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [lang-mustache]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [lang-painless]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [mapper-extras]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [parent-join]
[2018-12-11T12:33:52,274][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [percolator]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [rank-eval]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [reindex]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [repository-url]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [transport-netty4]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded module [tribe]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [ingest-geoip]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [ingest-user-agent]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-core]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-deprecation]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-graph]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-logstash]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-ml]
[2018-12-11T12:33:52,275][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-monitoring]
[2018-12-11T12:33:52,276][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-security]
[2018-12-11T12:33:52,276][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-upgrade]
[2018-12-11T12:33:52,276][INFO ][o.e.p.PluginsService     ] [QwRx60a] loaded plugin [x-pack-watcher]
[2018-12-11T12:33:54,344][INFO ][o.e.x.m.j.p.l.CppLogMessageHandler] [controller/281] [Main.cc@128] controller (64 bit): Version 6.2.4 (Build 524e7fe231abc1) Copyright (c) 2018 Elasticsearch BV
[2018-12-11T12:33:55,549][INFO ][o.e.d.DiscoveryModule    ] [QwRx60a] using discovery type [zen]
[2018-12-11T12:33:56,066][INFO ][o.e.n.Node               ] initialized
[2018-12-11T12:33:56,066][INFO ][o.e.n.Node               ] [QwRx60a] starting ...
[2018-12-11T12:33:56,230][INFO ][o.e.t.TransportService   ] [QwRx60a] publish_address {10.255.41.3:9300}, bound_addresses {[::]:9300}
[2018-12-11T12:33:56,241][INFO ][o.e.b.BootstrapChecks    ] [QwRx60a] bound or publishing to a non-loopback address, enforcing bootstrap checks
ERROR: [1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2018-12-11T12:33:56,250][INFO ][o.e.n.Node               ] [QwRx60a] stopping ...
[2018-12-11T12:33:56,315][INFO ][o.e.n.Node               ] [QwRx60a] stopped
[2018-12-11T12:33:56,315][INFO ][o.e.n.Node               ] [QwRx60a] closing ...
[2018-12-11T12:33:56,325][INFO ][o.e.n.Node               ] [QwRx60a] closed
[root@dmp-dn-001 /]#

我看到了错误的原因就是虚拟内存的权限太小，至少需要262144

[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

查看虚拟机可分配内存的大小：

[root@dmp-dn-001 /]# sysctl -a|grep vm.max_map_count
vm.max_map_count = 65530
[root@dmp-dn-001 /]#

接着就是修改虚拟机可分配内存的大小

[root@dmp-dn-001 /]# sysctl -w vm.max_map_count=262144
vm.max_map_count = 262144
[root@dmp-dn-001 /]# sysctl -a|grep vm.max_map_count
vm.max_map_count = 262144
[root@dmp-dn-001 /]#

启动es镜像：

[root@dmp-dn-001 /]# docker run 7cb69da7148d
[2018-12-11T12:37:08,213][INFO ][o.e.n.Node               ] [] initializing ...
[2018-12-11T12:37:08,260][INFO ][o.e.e.NodeEnvironment    ] [uTUEV7Q] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [82gb], net total_space [99.9gb], types [rootfs]
[2018-12-11T12:37:08,261][INFO ][o.e.e.NodeEnvironment    ] [uTUEV7Q] heap size [989.8mb], compressed ordinary object pointers [true]
[2018-12-11T12:37:08,263][INFO ][o.e.n.Node               ] node name [uTUEV7Q] derived from node ID [uTUEV7Q6Q8mgVXsdIkMd6Q]; set [node.name] to override
[2018-12-11T12:37:08,263][INFO ][o.e.n.Node               ] version[6.2.4], pid[1], build[ccec39f/2018-04-12T20:37:28.497551Z], OS[Linux/3.10.0-327.el7.x86_64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_161/25.161-b14]
[2018-12-11T12:37:08,263][INFO ][o.e.n.Node               ] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.QFAKB4sE, -XX:+HeapDumpOnOutOfMemoryError, -XX:+PrintGCDetails, -XX:+PrintGCDateStamps, -XX:+PrintTenuringDistribution, -XX:+PrintGCApplicationStoppedTime, -Xloggc:logs/gc.log, -XX:+UseGCLogFileRotation, -XX:NumberOfGCLogFiles=32, -XX:GCLogFileSize=64m, -Des.cgroups.hierarchy.override=/, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [aggs-matrix-stats]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [analysis-common]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [ingest-common]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [lang-expression]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [lang-mustache]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [lang-painless]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [mapper-extras]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [parent-join]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [percolator]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [rank-eval]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [reindex]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [repository-url]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [transport-netty4]
[2018-12-11T12:37:10,092][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded module [tribe]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [ingest-geoip]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [ingest-user-agent]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-core]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-deprecation]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-graph]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-logstash]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-ml]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-monitoring]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-security]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-upgrade]
[2018-12-11T12:37:10,093][INFO ][o.e.p.PluginsService     ] [uTUEV7Q] loaded plugin [x-pack-watcher]
[2018-12-11T12:37:12,144][INFO ][o.e.x.m.j.p.l.CppLogMessageHandler] [controller/281] [Main.cc@128] controller (64 bit): Version 6.2.4 (Build 524e7fe231abc1) Copyright (c) 2018 Elasticsearch BV
[2018-12-11T12:37:13,395][INFO ][o.e.d.DiscoveryModule    ] [uTUEV7Q] using discovery type [zen]
[2018-12-11T12:37:14,060][INFO ][o.e.n.Node               ] initialized
[2018-12-11T12:37:14,060][INFO ][o.e.n.Node               ] [uTUEV7Q] starting ...
[2018-12-11T12:37:14,171][INFO ][o.e.t.TransportService   ] [uTUEV7Q] publish_address {10.255.41.3:9300}, bound_addresses {[::]:9300}
[2018-12-11T12:37:14,182][INFO ][o.e.b.BootstrapChecks    ] [uTUEV7Q] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2018-12-11T12:37:17,240][INFO ][o.e.c.s.MasterService    ] [uTUEV7Q] zen-disco-elected-as-master ([0] nodes joined), reason: new_master {uTUEV7Q}{uTUEV7Q6Q8mgVXsdIkMd6Q}{uelRGzEaRaSWbOAaQUwBpw}{10.255.41.3}{10.255.41.3:9300}{ml.machine_memory=134906904576, ml.max_open_jobs=20, ml.enabled=true}
[2018-12-11T12:37:17,247][INFO ][o.e.c.s.ClusterApplierService] [uTUEV7Q] new_master {uTUEV7Q}{uTUEV7Q6Q8mgVXsdIkMd6Q}{uelRGzEaRaSWbOAaQUwBpw}{10.255.41.3}{10.255.41.3:9300}{ml.machine_memory=134906904576, ml.max_open_jobs=20, ml.enabled=true}, reason: apply cluster state (from master [master {uTUEV7Q}{uTUEV7Q6Q8mgVXsdIkMd6Q}{uelRGzEaRaSWbOAaQUwBpw}{10.255.41.3}{10.255.41.3:9300}{ml.machine_memory=134906904576, ml.max_open_jobs=20, ml.enabled=true} committed version [1] source [zen-disco-elected-as-master ([0] nodes joined)]])
[2018-12-11T12:37:17,270][INFO ][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [uTUEV7Q] publish_address {10.255.41.3:9200}, bound_addresses {[::]:9200}
[2018-12-11T12:37:17,271][INFO ][o.e.n.Node               ] [uTUEV7Q] started
[2018-12-11T12:37:17,354][INFO ][o.e.g.GatewayService     ] [uTUEV7Q] recovered [0] indices into cluster_state
[2018-12-11T12:37:17,688][INFO ][o.e.l.LicenseService     ] [uTUEV7Q] license [674c88a0-48f4-43b0-a71a-cda5cc1637cc] mode [basic] - valid

可以看到启动成功了，这是再看看pod的状态，

[root@master elasticsearchyaml]# kubectl get pods
NAME                  READY     STATUS    RESTARTS   AGE
elasticsearch-dmrkr   1/1       Running   6          9m
mysql-flf48           1/1       Running   2          1d
[root@master elasticsearchyaml]#

可以看到es的pod在正常运行了，那么问题就解决掉了。为了是虚拟机内存的限制设置始终有效，我们将他写入配置文件，否则重启后刚才的设置将失效，

vim  /etc/sysctl.conf


# System default settings live in /usr/lib/sysctl.d/00-system.conf.
# To override those settings, enter new settings here, or in an /etc/sysctl.d/<name>.conf file
#
# For more information, see sysctl.conf(5) and sysctl.d(5).

vm.max_map_count=262144

好了，问题已经解决，有问题或者想结交技术类朋友，请加QQ群：526855734

 

Tilyp
关注
  • 0
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 4
    评论
专栏目录
Kubernetes进阶学习之集群维护与升级实践
WeiyiGeek 唯一极客IT知识分享
07-24 915
0x00 Kubernetes Etcd 数据备份与恢复1) 备份 ETCD 数据实践2) 恢复 ETCD 数据实践0x01 Kubernetes 单 Master 节点(次版本)升级实践0x02 Kubernetes 单 Master 节点(跨版本)升级实践0x03 Kubernetes 集群从 Dockershim 迁移到 Containerd.io 运行时(1) 检...
kubernetes-elasticsearch-cluster：在Kubernetes之上的Elasticsearch集群变得容易
02-04
kubernetes-elasticsearch-cluster：在Kubernetes之上的Elasticsearch集群变得容易
kubelet报错，etcd重启失败
liangkaiping0525的博客
03-17 1886
报错如下： journalctl -fu kubelet 3月 17 14:54:32 75-k8s-master kubelet[21477]: W0317 14:54:32.861709 21477 conversion.go:111] Could not get instantcpu stats: cumulative stats decrease 3月 17 14:54:45 75-k8s-master kubelet[21477]: I0317 14:54:45.723260 214
k8s常见问题：如何处理CrashLoopBackOff问题？
最新发布
分享云原生大数据技术和个人成长、职业发展相关内容
05-07 2384
首先关于CrashLoopBackOff并不是代表一种错误， "CrashLoopBackOff 是 Kubernetes 中的一个状态，表示在一个 Pod 中发生的重启循环：Pod 中的一个容器启动之后发生了问题，然后反复重启。Kubernetes 会在重启之间等待逐渐增加的退避时间，我们在发现CrashLoopBackOff之后可以对集群进行及时的修复。因此，CrashLoopBackOff 本身并不是一个问题，而是表明有一个错误在发生，阻止了 Pod 正确启动。
kubernetes flannel pod CrashLoopBackoff解决
Focus on k8s and python
05-21 2868
# 背景 某环境客户部署了一个kubernetes集群，发现flannel的pod一直重启，始终处于CrashLoopBackOff状态。 ![image-20200521194511898](https://360linux.oss-cn-hangzhou.aliyuncs.com/img/image-20200521194511898.png) # 排查 1. 对于始终CrashLoopBackOff的pod，一般是应用本身的问题，需要查看具体pod的日志，通过```kubectl logs -
kubernetes启动Pod遇到CrashLoopBackOff的解决思路
热门推荐
纵横四海的博客
01-29 14万+
1.问题现状 通过命令行工具kubectl 获取异常容器 [root@master ~]# kubectl get pods -n kube-system | grep -v Running NAME READY STATUS RESTARTS AGE prometheus-tim
kubeadmin kube-apiserver Exited 始终起不来查因记录
l434的博客
02-16 2136
kubeadmin
K8s问题【flannel一直重启问题，CrashLoopBackOff】
Happywzy~的博客
12-16 1万+
kubectl describe 命令查看 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 13m ...
Kubernetes持久化部署elasticsearch7.15.0分布式集群
02-21
原文链接：https://blog.csdn.net/m0_37814112/article/details/122965720 说明：包含elasticsearch7.15.0集群3节点、5节点、7节点等三种方式的K8S部署yaml文件、镜像文件，里面有详细的README.txt部署参考
es-operator：用于Elasticsearch的Kubernetes运算符
02-04
这是一个在Kubernetes中运行Elasticsearch的运营商，专注于运营方面，例如安全消耗以及为Elasticsearch数据节点提供自动缩放功能，而不仅仅是抽象清单定义。 兼容性 ES-Operator已通过Elasticsearch 6.x和7.0测试。...
安装部署 elasticsearch kibana 资源
11-05
安装部署 elasticsearch kibana 资源 如果有不会的伙伴 可以参考安装部署专栏《安装部署 elasticsearch kibana IK分词器》文章 其中会有较为详细的部署步奏 如果有不足之处,朢大神评论区指点 感谢您的支持, ღ( ´･...
Kubernetes-Elasticsearch
03-27
【正文】 Kubernetes（简称K8s）是Google开源的一款容器编排系统，它使得在大规模集群中管理...同时，通过Kubernetes的丰富工具链，可以对Elasticsearch的运行状态进行全方位的监控和管理，确保系统的稳定性和安全性。
docker踩坑系列
qq_41604283的博客
11-02 354
Windows下最近推出了ubuntu子系统，出于好奇下载并安装了一下，刚好最近在学习docker的使用，不如就在window自带的子系统上进行测试能否使用。理论存在，实践开始。贴出找到比较详细的docker教程： http://c.biancheng.net/view/3118.html 第一步：安装docker Desktop,具体怎么安装参照官网的步骤，这里就不一一解释了。（注意需要在windows——程序与功能——启用或关闭Windows功能——开启Hyper-V，然后进行重启） 第二步
深入了解：Kubernetes pod状态出现CrashLoopBackOff 的原因
牛肉胡辣汤
10-08 9218
在这个示例中，我们假设您的后端服务是使用Python编写的，并且使用了一个名为"app.py"的主应用程序文件。这只是一个简单的示例，您可以根据您的实际需求进行调整和扩展。在这个示例中，我们定义了一个名为"my-app"的Deployment，它包含一个容器名为"my-app-container"的镜像。在实际应用中，您可能还需要定义其他资源，如服务（Service）、持久卷（PersistentVolume）、配置映射（ConfigMap）等，以满足您的应用需求。
k8s的LInux单节点部署(含containerCreating、ImagePullBackOff、CrashLoopBackOff问题的解决方案)
思南的博客
12-27 1286
1、安装etcd和kubernetes 该步骤会默认安装docker。所以建议在原机器上没有安装Docker，否则可能会有冲突导致安装失败。 yum install -y etcd kubernetes 2、配置 （1）、修改配置文件：/etc/sysconfig/docker 添加下面一行，使用内网仓库： ADD_REGISTRY='--add-registry reg.docker.lc' （2）修改配置文件：/etc/kubernetes/apiserver KUBE_API_ADDRESS="-
k8s错误CrashLoopBackOff
运维Linux和python
02-28 1万+
序言2020年1月1日就收到一个故障，注定不是平凡的一年。所以呢，决定年后戒烟。。。至于是哪一年的年后，我没说。。。哈哈哈CrashLoopBackoff在创...
kubesphere安装service-mesh后，elasticsearch-logging-data、elasticasearch-logging-discovery一直启动不起来
weixin_49025357的博客
06-19 268
处理kubesphere安装微服务治理模块出现的问题
7 张图解 CrashLoopBackOff，如何发现问题并解决它？
因上努力，果上随缘。但行好事，莫问前程。
08-31 2万+
是一种 Kubernetes 状态，表示 Pod 中发生的重启循环：Pod 中的容器已启动，但一遍又一遍的崩溃然后又重新启动。Kubernetes 将在重新启动之间等待越来越长的BackOff时间，以便您有机会修复错误。因此，CrashLoopBackOff 本身并不是一个错误，而是表明发生了一个错误，导致 Pod 无法正常启动。Pod 在 Running、Failed 和 Waiting 之间循环请注意，它重新启动的原因是因为它设置为Always（默认情况下）或OnFailure。...
KubeSphere 日志备份与恢复实践
KubeSphere
12-12 2221
为什么需要日志备份 KubeSphere 日志系统使用 Fluent Bit ElasticSearch 的日志采集存储方案，并通过 Curator 实现对 Index 的生命周期管理，定期清理久远日志。对于有日志审计和灾备需求的场景来说，KubeSphere 默认的 7 天日志保留策略远远不够，仅备份 ElasticSearch 数据盘并不能保证数据可恢复性和完整性。 ElasticSear...
ElasticSearch6.7.0安装文档20201127.docx
04-22
ElasticSearch6.7.0安装过程记录

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 4
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值