# Need help in understanding temporal-potsgres.yaml

**URL:** <https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179>\
**Category:** Server Deployment\
**Tags:** postgresql\
**Created:** [May 8, 2023, 10:53am UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179 "2023-05-08T10:53:21Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![shivan\_trivedi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shivan_trivedi/32/3736_2.png) [@shivan\_trivedi](https://community.temporal.io/u/shivan_trivedi)\
**Post date:** [May 8, 2023, 10:53am UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/1 "2023-05-08T10:53:21Z")

</div>

I am trying to run temporal-potsgres.yaml under k8s folder of docker-compose repo , but frontend and worker pods are going to CrashBackOff state and throwing Error :- Unable to create server. Error: could not build arguments for function “[go.uber.org/fx](http://go.uber.org/fx)”.(\*App).failed to build log.Logger: received non-nil error from function “[go.temporal.io/server/temporal](http://go.temporal.io/server/temporal)”.ServerOptionsProvider, cassandra schema version compatibility check failed: version mismatch for keyspace/da **strong text** tabase: “temporal”. Expected version: 1.7 cannot be greater than Actual version: 0.0

temporaltest-history, temporaltest-matching and temporaltest-frontend are crashing again and again  
Can anyone please help me understanding the actual issue here as I am using postgresql so why it’s asking for cassandra support ? Or what actual is happening here ?

Also if anyone can help me regarding postgresql specific installation for K8s , some steps are missing under example in documentation

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [May 8, 2023, 11:37am UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/2 "2023-05-08T11:37:10Z")

</div>

hello @shivan_trivedi

I am trying to reproduce your issue,

Are you following these instructions? [docker-compose/KUBERNETES.md at main · temporalio/docker-compose · GitHub](https://github.com/temporalio/docker-compose/blob/main/KUBERNETES.md)

---

<div class="post-metadata">

**Author:** ![shivan\_trivedi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shivan_trivedi/32/3736_2.png) [@shivan\_trivedi](https://community.temporal.io/u/shivan_trivedi)\
**Post date:** [May 8, 2023, 11:39am UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/3 "2023-05-08T11:39:50Z")

</div>

![Screenshot 2023-05-08 at 5.08.14 PM](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/3/3cec756922e98194dced9a090f698f115366db5f.png)  
I used helm chart approach also but got same response from pod logs under minikube  
helm install -f values/values.postgresql.yaml temporaltestv2   
–set elasticsearch.enabled=false   
–set server.config.persistence.default.sql.user=temporal   
–set server.config.persistence.default.sql.password=temporal   
–set server.config.persistence.visibility.sql.user=temporal   
–set server.config.persistence.visibility.sql.password=temporal   
–set server.config.persistence.default.sql.host=postgresql   
–set server.config.persistence.visibility.sql.host=postgresql . --timeout 900s

---

<div class="post-metadata">

**Author:** ![shivan\_trivedi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shivan_trivedi/32/3736_2.png) [@shivan\_trivedi](https://community.temporal.io/u/shivan_trivedi)\
**Post date:** [May 8, 2023, 12:43pm UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/4 "2023-05-08T12:43:13Z")

</div>

Hey @antonio.perez , yes following the same article – docker-compose/KUBERNETES.md at main · temporalio/docker-compose · GitHub]([docker-compose/KUBERNETES.md at main · temporalio/docker-compose · GitHub](https://github.com/temporalio/docker-compose/blob/main/KUBERNETES.md))

---

<div class="post-metadata">

**Author:** ![shivan\_trivedi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shivan_trivedi/32/3736_2.png) [@shivan\_trivedi](https://community.temporal.io/u/shivan_trivedi)\
**Post date:** [May 8, 2023, 4:50pm UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/5 "2023-05-08T16:50:01Z")

</div>

Above issue is resolved now but now my worker is not connecting to port 7233 , already being forwarded . It is throwing **unable to create Temporal client failed reaching server: last connection error: connection error: desc = “transport: Error while dialing: dial tcp [::1]:7233: connect: connection refused”**  
**exit status 1**  
Any Idea regarding that ?

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [May 8, 2023, 4:55pm UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/6 "2023-05-08T16:55:06Z")

</div>

@shivan_trivedi ,  
can you check if you can connect from the command line

```auto
grpcurl -plaintext -d '{"service": "temporal.api.workflowservice.v1.WorkflowService"}' <URL>:7233 grpc.health.v1.Health/Check

```

---

<div class="post-metadata">

**Author:** ![shivan\_trivedi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shivan_trivedi/32/3736_2.png) [@shivan\_trivedi](https://community.temporal.io/u/shivan_trivedi)\
**Post date:** [May 8, 2023, 4:59pm UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/7 "2023-05-08T16:59:14Z")

</div>

@antonio.perez  
Failed to dial target host “127.0.0.1:7233”: dial tcp 127.0.0.1:7233: connect: connection refused

Basically I am running worker on my local machine and temporal on minikube and trying to connect it via port forwarding , Is this the right way or there is any issue ?

---

<div class="post-metadata">

**Author:** ![shivan\_trivedi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/shivan_trivedi/32/3736_2.png) [@shivan\_trivedi](https://community.temporal.io/u/shivan_trivedi)\
**Post date:** [May 8, 2023, 5:12pm UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/8 "2023-05-08T17:12:39Z")

</div>

cleared all old images and now getting this error ~~ **unable to create Temporal client failed reaching server: last connection error: connection error: desc = “error reading server preface: EOF”**

---

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [May 9, 2023, 11:43am UTC](https://community.temporal.io/t/need-help-in-understanding-temporal-potsgres-yaml/8179/9 "2023-05-09T11:43:43Z")

</div>

Hello @shivan_trivedi

Can you share the yml files and configuration to reproduce the issue?
