# When execute fix-coordinator-ips got "Could not find process for coordinator IP.." error

**URL:** <https://forums.foundationdb.org/t/when-execute-fix-coordinator-ips-got-could-not-find-process-for-coordinator-ip-error/3469>\
**Category:** Kubernetes Operator\
**Created:** [July 27, 2022, 7:04am UTC](https://forums.foundationdb.org/t/when-execute-fix-coordinator-ips-got-could-not-find-process-for-coordinator-ip-error/3469 "2022-07-27T07:04:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![liuyan](https://avatars.discourse-cdn.com/v4/letter/l/839c29/32.png) [@liuyan](https://forums.foundationdb.org/u/liuyan)\
**Post date:** [July 27, 2022, 7:04am UTC](https://forums.foundationdb.org/t/when-execute-fix-coordinator-ips-got-could-not-find-process-for-coordinator-ip-error/3469/1 "2022-07-27T07:04:39Z")

</div>

If there is coordinator ip changes, like I delete more than half pods, it will trigger this recover step, and when trying to execute the fix-coordinator-ips command, got error

```auto
sh-4.4$ kubectl fdb fix-coordinator-ips -c mdm-foundationdb-ibm -n testoperator1
2022/07/27 06:46:23 Could not find process for coordinator IP 10.254.14.174:4500:tls
2022/07/27 06:46:23 Could not find process for coordinator IP 10.254.23.103:4500:tls
2022/07/27 06:46:23 Could not find process for coordinator IP 10.254.17.99:4500:tls
2022/07/27 06:46:23 New connection string: mdm_foundationdb_ibm:hXU4v6hVgaKKYRgrrrH7JIdfX2Trbp4a@10.254.14.174:4500:tls,10.254.23.103:4500:tls,10.254.17.99:4500:tls

```

could you share some insights what might be wrong?

---

<div class="post-metadata">

**Author:** ![johscheuer](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@johscheuer](https://forums.foundationdb.org/u/johscheuer)\
**Post date:** [August 3, 2022, 8:39am UTC](https://forums.foundationdb.org/t/when-execute-fix-coordinator-ips-got-could-not-find-process-for-coordinator-ip-error/3469/2 "2022-08-03T08:39:38Z")

</div>

I assume by delete you mean you run `kubectl delete po ..` or the equivalent in you favourite programming language? Have you ensured that the new Pods are created and running? This is the place where the error is thrown: [fdb-kubernetes-operator/fix\_coordinator\_ips.go at main · FoundationDB/fdb-kubernetes-operator · GitHub](https://github.com/FoundationDB/fdb-kubernetes-operator/blob/main/kubectl-fdb/cmd/fix_coordinator_ips.go#L185-L188). If you are able to reproduce this issue, could you open a GitHub issue with a minimal reproducible setup? It would also be helpful if you could share the cluster status from the cluster definition in Kubernetes.

---

<div class="post-metadata">

**Author:** ![liuyan](https://avatars.discourse-cdn.com/v4/letter/l/839c29/32.png) [@liuyan](https://forums.foundationdb.org/u/liuyan)\
**Post date:** [August 4, 2022, 2:57pm UTC](https://forums.foundationdb.org/t/when-execute-fix-coordinator-ips-got-could-not-find-process-for-coordinator-ip-error/3469/3 "2022-08-04T14:57:23Z")

</div>

@johscheuer I opened [Execute fix-coordinator-ips command got “Could not find process for coordinator IP..” error · Issue #1314 · FoundationDB/fdb-kubernetes-operator · GitHub](https://github.com/FoundationDB/fdb-kubernetes-operator/issues/1314) let me know if you need more info. thank you.