# Errors with Sharded Server Cluster on GKE

**URL:** <https://forums.percona.com/t/errors-with-sharded-server-cluster-on-gke/22445>\
**Category:** Percona Server for MongoDB\
**Tags:** kubernetes\
**Created:** [May 31, 2023, 5:35pm UTC](https://forums.percona.com/t/errors-with-sharded-server-cluster-on-gke/22445 "2023-05-31T17:35:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ben\_Chiciudean](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ben_chiciudean/32/10759_2.png) [@Ben\_Chiciudean](https://forums.percona.com/u/Ben_Chiciudean)\
**Post date:** [May 31, 2023, 5:35pm UTC](https://forums.percona.com/t/errors-with-sharded-server-cluster-on-gke/22445/1 "2023-05-31T17:35:48Z")

</div>

We tried install mongodb server with sharding enabled but keep getting this error on cfg pods: `find: '/data/configdb': No such file or directory`

We used latest psmdb-operator and psmdb-db helm charts.

GKE version is 1.26.3-gke.1000

In the cfg pod events we also get:

```auto
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/data/db/ps-entry.sh": stat /data/db/ps-entry.sh: no such file or directory: unknown

```

In the logs also:

```auto
Exit: connect to PBM: create mongo connection: mongo ping: server selection error: server selection timeout, current topology: { Type: ReplicaSetNoPrimary, Servers: [{ Addr: localhost:27017, Type: RSGhost, Average RTT: 1196431 },] }"

```

---

<div class="post-metadata">

**Author:** ![Parag\_Bhayani](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/parag_bhayani/32/3710_2.png) [@Parag\_Bhayani](https://forums.percona.com/u/Parag_Bhayani)\
**Post date:** [June 1, 2023, 2:51pm UTC](https://forums.percona.com/t/errors-with-sharded-server-cluster-on-gke/22445/2 "2023-06-01T14:51:12Z")

</div>

Hi @Ben_Chiciudean ,

Kindly share the cr.yaml file and the describe pod output of the config server for further analysis.  
Also the yaml output of config pod.

> kubectl describe pod (pod name) -n (namespace)  
> kubectl get pod (pod name) -n (namespace) -o yaml

Regards,  
Parag

---

<div class="post-metadata">

**Author:** ![Ben\_Chiciudean](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ben_chiciudean/32/10759_2.png) [@Ben\_Chiciudean](https://forums.percona.com/u/Ben_Chiciudean)\
**Post date:** [June 2, 2023, 11:58am UTC](https://forums.percona.com/t/errors-with-sharded-server-cluster-on-gke/22445/3 "2023-06-02T11:58:29Z")

</div>

> [@Parag\_Bhayani](#):
>
> Kindly share the cr.yaml file and the describe pod output of the config server for further analysis.  
> Also the yaml output of config pod.

In the end we used the `cr.yaml` file which works, like I said previously we tried with **psmdb-db helm chart** and any values we passed to the release, it wouldn’t apply them. We have removed the helm release.