# Automatically elastic operator pod went down and up

**URL:** <https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [December 16, 2020, 10:37am UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840 "2020-12-16T10:37:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![knagasri](https://avatars.discourse-cdn.com/v4/letter/k/47e85d/32.png) [@knagasri](https://discuss.elastic.co/u/knagasri)\
**Post date:** [December 16, 2020, 10:37am UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840/1 "2020-12-16T10:37:56Z")

</div>

Deployed Elasticsearch cluster in GCP. Without making any changes, operator pod goes down and after sometime pods get restarted. Elastic operator version is 1.1.0 . Below is logs of elastic operator pod .

```auto
{"log.level":"error","@timestamp":"2020-12-16T04:18:29.237Z","log.logger":"driver","message":"Could not update remote clusters in Elasticsearch settings","service.version":"1.1.0-29e7447f","service.type":"eck","ecs.version":"1.4.0","namespace":"ns","es_name":"es","error":"Operation cannot be fulfilled on elasticsearches.elasticsearch.k8s.elastic.co \"es\": the object has been modified; please apply your changes to the latest version and try again","error.stack_trace":"github.com/go-logr/zapr.(*zapLogger). 

```

Can anyone know why it is happening ?

---

<div class="post-metadata">

**Author:** ![dkow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkow/32/47340_2.png) [@dkow](https://discuss.elastic.co/u/dkow)\
**Post date:** [December 16, 2020, 11:29am UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840/2 "2020-12-16T11:29:17Z")

</div>

Hey @knagasri, thanks for your question.

How are you checking that the operator Pod restarted? Can you provide logs from before the crash? You can use `kubectl logs -n elastic-system elastic-operator-0 --previous` to do that.

The log you've pasted indicates that there was a conflict updating a resource - when the operator tried to update, the resource was already at a higher version. It's expected to see this log appear sporadically.

---

<div class="post-metadata">

**Author:** ![knagasri](https://avatars.discourse-cdn.com/v4/letter/k/47e85d/32.png) [@knagasri](https://discuss.elastic.co/u/knagasri)\
**Post date:** [December 16, 2020, 1:16pm UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840/3 "2020-12-16T13:16:29Z")

</div>

kubectl --kubeconfig=e -n logs elastic-operator-0 --previous

```auto
Error from server (BadRequest): previous terminated container "manager" in pod "elastic-operator-0" not found

```

---

<div class="post-metadata">

**Author:** ![dkow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkow/32/47340_2.png) [@dkow](https://discuss.elastic.co/u/dkow)\
**Post date:** [December 16, 2020, 3:39pm UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840/4 "2020-12-16T15:39:49Z")

</div>

It seems there was no previous instance of the operator and `Operation cannot be fulfilled on...` log line isn't an indication of a restart. Is it possible that it didn't restart at all?

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [December 16, 2020, 3:53pm UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840/5 "2020-12-16T15:53:36Z")

</div>

`kubectl describe pod/elastic-operator-0 -n elastic-system` would help to see if the OOMKiller is the culprit.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:19am UTC](https://discuss.elastic.co/t/automatically-elastic-operator-pod-went-down-and-up/258840/6 "2022-11-04T08:19:52Z")

</div>