Brewblox-ctl setup fails

jwiqvist · May 23, 2020, 11:05pm

I’m trying to do a fresh install, so I am following the documentation, using raspberry lite etc. Works fine until I run brewblox-ctl setup and get this log:
pi@raspberrypi:~/brewblox $ brewblox-ctl setup
INFO Stopping services…
Removing brewblox_ui_1 … done
Removing brewblox_eventbus_1 … done
Removing brewblox_mdns_1 … done
Removing brewblox_datastore_1 … done
Removing brewblox_emitter_1 … done
Removing brewblox_spark-one_1 … done
Removing brewblox_history_1 … done
Removing brewblox_influx_1 … done
Removing brewblox_traefik_1 … done
Removing network brewblox_default
INFO Checking ports…
This directory already contains a docker-compose.yml file. Do you want to keep i t? [Press ENTER for default value ‘Yes’]

This directory already contains Couchdb datastore files. Do you want to keep them? [Press ENTER for default value ‘Yes’]

This directory already contains Influx history files. Do you want to keep them? [Press ENTER for default value ‘Yes’]

This directory already contains Traefik gateway files. Do you want to keep them? [Press ENTER for default value ‘Yes’]

INFO Setting .env values…

INFO Stopping services…
Removing network brewblox_default
WARNING: Network brewblox_default not found.
INFO Pulling docker images…
Pulling eventbus … done
Pulling emitter … done
Pulling influx … done
Pulling datastore … done
Pulling spark-one … done
Pulling traefik … done
Pulling ui … done
Pulling history … done
Pulling mdns … done
INFO Starting configured services…
Creating network “brewblox_default” with the default driver
Creating brewblox_traefik_1 …
Creating brewblox_influx_1 …
Creating brewblox_history_1 … error

Creating brewblox_influx_1 … error
by/e02c1b8ed374a9b908eddf688e5840540ac72fe66f31a684499f166ea7ac5ffb/log.json: no such file or directory): runc did not terminate sucessfully: unknown
Creating brewblox_traefik_1 … error
ERROR: for brewblox_influx_1 Cannot start service influx: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/537f823f13d6e83a5170a348885a872e8c672c5c4fa3291b683dda91038ddb0c/log.json: no such file or directory): runc did not terminate sucessfully: unknown

ERROR: for brewblox_traefik_1 Cannot start service traefik: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/704e9c3f4dde0262a692fc625ee53b343d3233ea2e8cd876ab1d58319096c2db/log.json: no such file or directory): runc did not terminate sucessfully: unknown

ERROR: for history Cannot start service history: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/e02c1b8ed374a9b908eddf688e5840540ac72fe66f31a684499f166ea7ac5ffb/log.json: no such file or directory): runc did not terminate sucessfully: unknown

ERROR: for influx Cannot start service influx: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/537f823f13d6e83a5170a348885a872e8c672c5c4fa3291b683dda91038ddb0c/log.json: no such file or directory): runc did not terminate sucessfully: unknown

ERROR: for traefik Cannot start service traefik: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/704e9c3f4dde0262a692fc625ee53b343d3233ea2e8cd876ab1d58319096c2db/log.json: no such file or directory): runc did not terminate sucessfully: unknown
ERROR: Encountered errors while bringing up the project.
Command ‘docker-compose up -d --remove-orphans traefik influx history’ returned non-zero exit status 1.

Bob_Steers · May 24, 2020, 2:51am

The problem seems to be with the Docker daemon.

Try rebooting the Pi to reset the daemon. If this does not fix the problem, could you please run:

sudo systemctl status docker

jwiqvist · May 24, 2020, 8:30pm

Tried the command, results below. Btw i’m on a Raspberry 3 Model B, version 1.2.

pi@raspberrypi:~ $ sudo systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-05-24 21:22:30 BST; 27s ago
Docs: https://docs.docker.com
Main PID: 480 (dockerd)
Tasks: 14
Memory: 94.0M
CGroup: /system.slice/docker.service
└─480 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

May 24 09:17:27 raspberrypi dockerd[480]: time=“2020-05-24T09:17:27.895851031+01:00” level=warning msg=“Your kernel does not support cgroup rt period”
May 24 09:17:27 raspberrypi dockerd[480]: time=“2020-05-24T09:17:27.895938739+01:00” level=warning msg=“Your kernel does not support cgroup rt runtime”
May 24 09:17:27 raspberrypi dockerd[480]: time=“2020-05-24T09:17:27.897234885+01:00” level=info msg=“Loading containers: start.”
May 24 09:17:32 raspberrypi dockerd[480]: time=“2020-05-24T09:17:32.349957019+01:00” level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon o
May 24 09:17:32 raspberrypi dockerd[480]: time=“2020-05-24T09:17:32.842278789+01:00” level=info msg=“Loading containers: done.”
May 24 09:17:33 raspberrypi dockerd[480]: time=“2020-05-24T09:17:33.097254310+01:00” level=warning msg=“failed to retrieve runc version: signal: segmentation fault (core dumped)”
May 24 21:22:28 raspberrypi dockerd[480]: time=“2020-05-24T21:22:28.943280099+01:00” level=info msg=“Docker daemon” commit=9d98839 graphdriver(s)=overlay2 version=19.03.9
May 24 21:22:28 raspberrypi dockerd[480]: time=“2020-05-24T21:22:28.959893745+01:00” level=info msg=“Daemon has completed initialization”
May 24 21:22:30 raspberrypi systemd[1]: Started Docker Application Container Engine.
May 24 21:22:30 raspberrypi dockerd[480]: time=“2020-05-24T21:22:30.654202234+01:00” level=info msg=“API listen on /var/run/docker.sock”

Bob_Steers · May 24, 2020, 9:44pm

Googling your errors did not yield a clear-cut answer. You can try multiple approaches

Option 1: Retry the installation on a different SD card. SD cards are often the first component to fail, and errors tend to be cryptic. After the brewblox-ctl install and the reboot, run sudo systemctl status docker to check.

Option 2: Check whether anything is listening on port 80. I’m not sure why this would be an issue, but https://stackoverflow.com/questions/60664720/unable-to-start-docker-in-centos-job-for-docker-service-cancelled/60670749#60670749 reports it as being relevant.

Option 3: Downgrade installed docker version.

sudo apt install docker-ce=5:19.03.1~3-0~raspbian-buster
sudo systemctl restart docker
sudo systemctl status docker

Elco · May 24, 2020, 10:06pm

Segfault suggests a serious issue with docker, RAM or a corrupted SD card. I would also suggest a fresh install of latest raspbian on a new SD card.

jwiqvist · May 26, 2020, 8:23am

Yep, reinstalling everything from Raspberry Light onwards solved the problem. Should probably get a new SD-card but for now that worked. Thank you!