# Pomerium-databroker pod CrashLoopBackOff

**URL:** <https://discuss.pomerium.com/t/pomerium-databroker-pod-crashloopbackoff/126>\
**Category:** Support\
**Tags:** k8s\
**Created:** [May 28, 2022, 12:45pm UTC](https://discuss.pomerium.com/t/pomerium-databroker-pod-crashloopbackoff/126 "2022-05-28T12:45:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SeanYuan](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@SeanYuan](https://discuss.pomerium.com/u/SeanYuan)\
**Post date:** [May 28, 2022, 12:45pm UTC](https://discuss.pomerium.com/t/pomerium-databroker-pod-crashloopbackoff/126/1 "2022-05-28T12:45:25Z")

</div>

Hi Expert: sorry to bother,

## What happened?

after helm installation, the pomerium-databroker pod and redis pod cannot be running

## What did you expect to happen?

## How’d it happen?

the pods status is shown below

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/9f90be7bed9b10bec9c5e0a9188b1ac8118de9be.png)

databroker:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/97510e06858360b427debf5c6afe825cd089a756.png)

redis pod:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/048fb7e9e4be163b7d8f8710c41b94a27f8afafa.png)

## What’s your environment like?

- Pomerium version (retrieve with `pomerium --version`):  
Pomerium v0.17.3 image

- Server Operating System/Architecture/Cloud:  
centOS7

## What’s your config.yaml?

my values.yaml is shown below

```auto
authenticate:
  ingress:
    tls:
      secretName: pomerium-tls
  existingTLSSecret: pomerium-tls
  idp:
    provider: "okta"
    clientID: "0oa1xxxxxxxxxxxxxx4Z697"
    clientSecret: "b6_QkzxxxxxxxxxxxxxxxxxxxxxxxxxxsV"
    serviceAccount: "ewogICJhcGlfxxxxxxxxxxxxxxxxxxxxxTWVHdnViWFNRxxxxxxxxxxxxxIKfQo="
  proxied: false

proxy:
  existingTLSSecret: pomerium-tls

databroker:
  existingTLSSecret: pomerium-tls
  storage:
    connectionString: redis://pomerium-redis-master.pomerium.svc.cluster.local
    type: redis
    clientTLS:
      existingSecretName: pomerium-tls
      existingCASecretKey: ca.crt

authorize:
  existingTLSSecret: pomerium-tls

redis:
  enabled: true
  auth:
    enabled: false
  usePassword: false
  generateTLS: false
  tls:
    certificateSecret: pomerium-redis-tls

ingressController:
  enabled: true

ingress:
  enabled: false

config:
  rootDomain: localhost.pomerium.io
  existingCASecret: pomerium-tls
  generateTLS: false # On by default, disabled when cert-manager or another solution is in place.
# The policy block isn't required when using the Pomerium Ingress Controller, as routes are defined
# by the addition of Ingress Resources.
# routes:
# # This will be our testing app, to confirm that Pomerium is authenticating and routing traffic.
# - from: https://authenticate.localhost.pomerium.io
# to: https://pomerium-authenticate.pomerium.svc.cluster.local
# preserve_host_header: true
# allow_public_unauthenticated_access: true
# policy:

```

appreciate!

---

<div class="post-metadata">

**Author:** ![denis](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@denis](https://discuss.pomerium.com/u/denis)\
**Post date:** [May 31, 2022, 12:51pm UTC](https://discuss.pomerium.com/t/pomerium-databroker-pod-crashloopbackoff/126/2 "2022-05-31T12:51:10Z")

</div>

Databroker depends on Redis.  
Redis doesn’t seem to be unable to start because a persistent volume claim cannot be fulfilled.  
Please check PVC documentation for your kubernetes distribution and environment and adjust accordingly.

---

<div class="post-metadata">

**Author:** ![SeanYuan](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@SeanYuan](https://discuss.pomerium.com/u/SeanYuan)\
**Post date:** [June 2, 2022, 6:45am UTC](https://discuss.pomerium.com/t/pomerium-databroker-pod-crashloopbackoff/126/3 "2022-06-02T06:45:02Z")

</div>

appreciate Denis!! I create 2 PV, the yaml as below:

```auto
apiVersion: v1
kind: PersistentVolume
metadata:
  name: task-pv-volume
  labels:
    type: local
spec:
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /ifs/share_folder
    server: 192.168.31.227

```

currently, the PVC was bound status, but 2 redis pods and databrokder pod are still the crashloopbackoff status

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/774b88b6f648dc304887654e7c805c38b831d2d9.png)

databroker issue:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/6b01f6b21c6cb5ffdece42df60e222421ecf3d03.png)

redis-master:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/b3c2669005f02d31d6ecdc0fa86b50a614181a33.png)

redis-replicas:

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/pomerium/original/1X/5a77e0d4b69ca5fa4a2afe68f97fdad80c0dd1df.png)

much appreciate