# Elastic-operator-0 CrashLoopBackOff

**URL:** <https://discuss.elastic.co/t/elastic-operator-0-crashloopbackoff/267736>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [March 19, 2021, 1:47am UTC](https://discuss.elastic.co/t/elastic-operator-0-crashloopbackoff/267736 "2021-03-19T01:47:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SnakeByte](https://avatars.discourse-cdn.com/v4/letter/s/9fc348/32.png) [@SnakeByte](https://discuss.elastic.co/u/SnakeByte)\
**Post date:** [March 19, 2021, 1:47am UTC](https://discuss.elastic.co/t/elastic-operator-0-crashloopbackoff/267736/1 "2021-03-19T01:47:09Z")

</div>

Following the instructions here, I only got as far as step 2 before running into trouble 🙂 :  
[Deploy ECK in your Kubernetes cluster](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-eck.html)

elastic-operator-0 is left in a CrashLoogBackOff state, with these three log entries:

`{"log.level":"error","@timestamp":"2021-03-19T01:16:23.369Z","log.logger":"manager","message":"Error setting GOMAXPROCS","service.version":"1.4.1+512d5431","service.type":"eck","ecs.version":"1.4.0","error":"invalid format for CGroupSubsys: \"12:freezer:/kubepods-burstable-podb913058b_6a87_453c_b589_bc8e84d29adb.slice:cri-containerd:6e4fa8c12a6d16cf94a3acb4b9edd5cc8314d85537a11115c8c9f40c55ca0796\"","error.stack_trace":"github.com/elastic/cloud-on-k8s/cmd/manager.startOperator\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:362\ngithub.com/elastic/cloud-on-k8s/cmd/manager.doRun.func2\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:321"}`

`{"log.level":"error","@timestamp":"2021-03-19T01:16:23.369Z","log.logger":"manager","message":"Shutting down due to error","service.version":"1.4.1+512d5431","service.type":"eck","ecs.version":"1.4.0","error":"invalid format for CGroupSubsys: \"12:freezer:/kubepods-burstable-podb913058b_6a87_453c_b589_bc8e84d29adb.slice:cri-containerd:6e4fa8c12a6d16cf94a3acb4b9edd5cc8314d85537a11115c8c9f40c55ca0796\"","error.stack_trace":"github.com/elastic/cloud-on-k8s/cmd/manager.doRun\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:329\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895\nmain.main\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/main.go:30\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:204"}`

`Error: invalid format for CGroupSubsys: "12:freezer:/kubepods-burstable-podb913058b_6a87_453c_b589_bc8e84d29adb.slice:cri-containerd:6e4fa8c12a6d16cf94a3acb4b9edd5cc8314d85537a11115c8c9f40c55ca0796"`

From what I could find searching the internet, this is a golang thing, but I'm uncertain why there is trouble. The node is running Ubuntu 18.04 LTS as a guest vm within Vmware Workstation 12 Pro that's running on top of Windows 10 Pro (Intel CPU). The runtime is Docker 19.03.8, with the cgroupdriver set to systemd.

---

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [March 22, 2021, 8:09am UTC](https://discuss.elastic.co/t/elastic-operator-0-crashloopbackoff/267736/2 "2021-03-22T08:09:48Z")

</div>

> [@SnakeByte](#):
>
> invalid format for CGroupSubsys

This seems related: [Invalid format for CGroupSubsys · Issue #4083 · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/issues/4083#issuecomment-754592876).

---

<div class="post-metadata">

**Author:** ![SnakeByte](https://avatars.discourse-cdn.com/v4/letter/s/9fc348/32.png) [@SnakeByte](https://discuss.elastic.co/u/SnakeByte)\
**Post date:** [March 23, 2021, 1:30am UTC](https://discuss.elastic.co/t/elastic-operator-0-crashloopbackoff/267736/3 "2021-03-23T01:30:42Z")

</div>

Thanks sebgl -- apparently I was using containerd for the runtime after-all -- I thought I blew that node away. Your link eventually got me to the solution:

```auto
version = 2
[plugins]
  [plugins."io.containerd.grpc.v1.cri"]
   [plugins."io.containerd.grpc.v1.cri".containerd]
      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
          runtime_type = "io.containerd.runc.v1"
          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
            SystemdCgroup = true

```

for /etc/containerd/config.toml

Oddly, the instructions for creating the containerd configuration file here ([Container runtimes | Kubernetes](https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd-systemd)) made a configuration file that I couldn't just edit and inline the change above -- I had to completely replace the file with just the contents above for this to start working.

---

<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:** [April 20, 2021, 1:31am UTC](https://discuss.elastic.co/t/elastic-operator-0-crashloopbackoff/267736/4 "2021-04-20T01:31:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
