I am getting CrashLookBackOff error for Percona XtraDB Cluster 8.0.20 in Kubernetes

Laxminarayana · November 11, 2020, 3:33am

@matthewb Thanks for response. Please find below manifest file and generated logs.

apiVersion: v1

kind: Pod

metadata:

creationTimestamp: ‘2020-11-11T08:48:29Z’

generateName: percona-xtradb-cluster-pxc-

labels:

app: percona-xtradb-cluster-pxc

chart: percona-xtradb-cluster-1.0.3

controller-revision-hash: percona-xtradb-cluster-pxc-c4cb996c8

heritage: Tiller

release: percona-xtradb-cluster

statefulset.kubernetes.io/pod-name: percona-xtradb-cluster-pxc-0

namespace: default

ownerReferences:

apiVersion: apps/v1

blockOwnerDeletion: true

controller: true

kind: StatefulSet

uid: ab89b4bf-23fa-11eb-9a3d-0242376f5115

resourceVersion: ‘33575’

selfLink: /api/v1/namespaces/default/pods/percona-xtradb-cluster-pxc-0

uid: ab958682-23fa-11eb-9a3d-0242376f5115

spec:

containers:

command:
- /bin/bash
- /startup-scripts/entrypoint.sh

env:

- name: MYSQL_ROOT_PASSWORD

 valueFrom:

  secretKeyRef:

   key: mysql-root-password

   name: percona-xtradb-cluster-pxc

- name: MYSQL_PASSWORD

 valueFrom:

  secretKeyRef:

   key: mysql-password

   name: percona-xtradb-cluster-pxc

- name: XTRABACKUP_PASSWORD

 valueFrom:

  secretKeyRef:

   key: xtrabackup-password

   name: percona-xtradb-cluster-pxc

- name: MYSQL_USER

 valueFrom:

  secretKeyRef:

   key: mysql-user

   name: percona-xtradb-cluster-pxc

- name: MYSQL_DATABASE

 valueFrom:

  secretKeyRef:

   key: mysql-database

   name: percona-xtradb-cluster-pxc

- name: ALLOW_ROOT_FROM

 value: '%'

- name: CLUSTER_NAME

 value: percona-xtradb-cluster-pxc

- name: SHORT_CLUSTER_NAME

 value: percona-xtradb-cluster-pxc

- name: K8S_SERVICE_NAME

 value: percona-xtradb-cluster-pxc-repl

- name: PXC_STRICT_MODE

 value: MASTER

- name: DEBUG

 value: 'true'

image: ‘local/percona-xtradb-cluster-server:8.0.20-11.3’

imagePullPolicy: Never

livenessProbe:

exec:

 command:

  - /bin/bash

  - '-c'

  - mysqladmin ping || test -e /var/lib/mysql/sst_in_progress

failureThreshold: 3

initialDelaySeconds: 30

periodSeconds: 10

successThreshold: 1

timeoutSeconds: 2

ports:

- containerPort: 3306

 name: mysql

 protocol: TCP

- containerPort: 4567

 name: galera-repl

 protocol: TCP

- containerPort: 4568

 name: state-transfer

 protocol: TCP

- containerPort: 4444

 name: state-snapshot

 protocol: TCP

readinessProbe:

exec:

 command:

  - mysql

  - '-h'

  - 127.0.0.1

  - '-e'

  - SELECT 1

failureThreshold: 3

initialDelaySeconds: 30

periodSeconds: 10

successThreshold: 1

timeoutSeconds: 2

resources: {}

terminationMessagePath: /dev/termination-log

terminationMessagePolicy: File

volumeMounts:

- mountPath: /var/lib/mysql

 name: mysql-data

- mountPath: /startup-scripts

 name: mysql-startup-scripts

- mountPath: /etc/mysql/conf.d

 name: mysql-config-files

- mountPath: /root

 name: slash-root

- mountPath: /var/log

 name: var-log

- mountPath: /backup-data

 name: backup-data

- mountPath: /var/run/secrets/kubernetes.io/serviceaccount

 name: default-token-hl4xt

 readOnly: true

command:
- tail
- ‘-f’
- /var/log/audit.log

image: ‘local/debian:jessie’

imagePullPolicy: Never

resources: {}

terminationMessagePath: /dev/termination-log

terminationMessagePolicy: File

volumeMounts:

- mountPath: /var/log

 name: var-log

- mountPath: /var/run/secrets/kubernetes.io/serviceaccount

 name: default-token-hl4xt

 readOnly: true

dnsPolicy: ClusterFirst

enableServiceLinks: true

hostname: percona-xtradb-cluster-pxc-0

initContainers:

command:
- rm
- ‘-fr’
- /var/lib/mysql/lost+found

image: ‘local/debian:jessie’

imagePullPolicy: Never

resources: {}

terminationMessagePath: /dev/termination-log

terminationMessagePolicy: File

volumeMounts:

- mountPath: /var/lib/mysql

 name: mysql-data

- mountPath: /var/run/secrets/kubernetes.io/serviceaccount

 name: default-token-hl4xt

 readOnly: true

nodeName: minikube

priority: 0

restartPolicy: Always

schedulerName: default-scheduler

securityContext:

fsGroup: 1001

serviceAccount: default

serviceAccountName: default

subdomain: percona-xtradb-cluster-pxc

terminationGracePeriodSeconds: 30

tolerations:

effect: NoExecute

key: node.kubernetes.io/not-ready

operator: Exists

tolerationSeconds: 300

effect: NoExecute

key: node.kubernetes.io/unreachable

operator: Exists

tolerationSeconds: 300

volumes:

name: mysql-data

persistentVolumeClaim:

claimName: mysql-data-percona-xtradb-cluster-pxc-0

emptyDir: {}

emptyDir: {}

configMap:

defaultMode: 420

name: percona-xtradb-cluster-pxc-config-files

configMap:

defaultMode: 420

name: percona-xtradb-cluster-pxc-startup-scripts

emptyDir: {}

emptyDir: {}

name: default-token-hl4xt

secret:

defaultMode: 420

secretName: default-token-hl4xt

status:

conditions:

lastProbeTime: null

lastTransitionTime: ‘2020-11-11T08:48:31Z’

status: ‘True’

type: Initialized

lastProbeTime: null

lastTransitionTime: ‘2020-11-11T08:48:29Z’

message: ‘containers with unready status: [database]’

reason: ContainersNotReady

status: ‘False’

type: Ready

lastProbeTime: null

lastTransitionTime: ‘2020-11-11T08:48:29Z’

message: ‘containers with unready status: [database]’

reason: ContainersNotReady

status: ‘False’

type: ContainersReady

lastProbeTime: null

lastTransitionTime: ‘2020-11-11T08:48:29Z’

status: ‘True’

type: PodScheduled

containerStatuses:

containerID: >-

docker://c68c8aec500be16b399b8752b00bfd8c0fbe0fe25ec8ac2a2e21e4a8a112c50b

image: ‘debian:jessie’

imageID: >-

docker-pullable://debian@sha256:62459e0ef769f129957fed32a1a4512b1415f09b794454acf012c82412ddf834

lastState:

terminated:

 containerID: >-

  docker://60621f5d5c1d56ac759c36a2cb7c7c7b72e0989e443510ba62f02ab98023efa5

 exitCode: 1

 finishedAt: '2020-11-11T08:48:48Z'

 reason: Error

 startedAt: '2020-11-11T08:48:48Z'

ready: true

restartCount: 3

state:

running:

 startedAt: '2020-11-11T08:49:15Z'

containerID: >-

docker://eb49f2b69500dc3159bce2cc7bc32a94e65a35e560bf0191b0f44180918944b8

image: ‘local/percona-xtradb-cluster-server:8.0.20-11.3’

imageID: >-

docker-pullable://percona/percona-xtradb-cluster@sha256:08ef5b75e12dbbf7fba35c9b6598908e139d9d18227b05eaa06b55b18f574754

lastState:

terminated:

 containerID: >-

  docker://eb49f2b69500dc3159bce2cc7bc32a94e65a35e560bf0191b0f44180918944b8

 exitCode: 2

 finishedAt: '2020-11-11T08:55:05Z'

 reason: Error

 startedAt: '2020-11-11T08:55:01Z'

ready: false

restartCount: 6

state:

waiting:

 message: >-

  Back-off 5m0s restarting failed container=database

  pod=percona-xtradb-cluster-pxc-0_default(ab958682-23fa-11eb-9a3d-0242376f5115)

 reason: CrashLoopBackOff

hostIP: 192.168.49.2

initContainerStatuses:

containerID: >-

docker://97caad90ea2f251639d4eabc23a44a91a6a328ae2baa2d90e776bf1f142a1948

image: ‘debian:jessie’

imageID: >-

docker-pullable://debian@sha256:62459e0ef769f129957fed32a1a4512b1415f09b794454acf012c82412ddf834

lastState: {}

ready: true

restartCount: 0

state:

terminated:

 containerID: >-

  docker://97caad90ea2f251639d4eabc23a44a91a6a328ae2baa2d90e776bf1f142a1948

 exitCode: 0

 finishedAt: '2020-11-11T08:48:30Z'

 reason: Completed

 startedAt: '2020-11-11T08:48:30Z'

phase: Running

podIP: 172.17.0.10

qosClass: BestEffort

startTime: ‘2020-11-11T08:48:29Z’

Topic		Replies	Views
Deploying percona xtradb cluster on K8s leads to Init:Crashloopbackoff Community website	0	148	June 7, 2024
MySQL Cluster goes into full crash every 5-10mins Percona Everest mysql , percona	15	117	May 20, 2025
Kubernetes - [Galera] Handshake failed due to unknown CA Percona Server for MySQL 8.0 kubernetes	4	976	November 26, 2024
Pxc-db xtrabackup error Percona XtraDB Cluster 8.x mysql , percona	1	86	April 4, 2025
CrashLoopBackOff on deploy cluster Percona Operator for MongoDB	12	648	June 16, 2024

I am getting CrashLookBackOff error for Percona XtraDB Cluster 8.0.20 in Kubernetes

Related topics