Mongo container keeps restarting

Kobo On Your Own Server
,
1

I am trying to do a fresh install of the latest release of kobo-install (2.23.04) on an Ubuntu 22.04.5 LTS server. Everything seems to start up correctly until it gets to “Waiting for environment to be ready. it can take a few minutes” but it never starts up.

When I check the containers (docker ps) it shows the mongo container keeps restarting every few seconds. the kpi container also restarts about every 30 seconds. When I check the logs, they show that mongo keeps timing out:

kobofe-kobocat-1         | KoBoCAT intializing...
kobofe-kobocat-1         | Waiting for container `mongo`.
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | KoBoCAT intializing...
kobofe-kobocat-1         | Waiting for container `mongo`.
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | KoBoCAT intializing...
kobofe-kobocat-1         | Waiting for container `mongo`.
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | KoBoCAT intializing...
kobofe-kobocat-1         | Waiting for container `mongo`.
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1 exited with code 0
kobofe-kobocat-1         | Waiting for container `mongo`.
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1             | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1 exited with code 0
kobofe-kpi-1             | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1             | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1 exited with code 0
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1 exited with code 0
kobofe-kpi-1             | Waiting for container `mongo`.
kobofe-kpi-1             | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1             | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1 exited with code 0
kobofe-kobocat-1         | Waiting for container `mongo`.
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1         | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1 exited with code 0
kobofe-kpi-1             | KoBoForm initializing...
kobofe-kpi-1             | Waiting for container `mongo`.
kobofe-kpi-1             | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kpi-1             | wait-for-it: timeout occurred after waiting 40 seconds for mongo.REDACTED.private:27017
kobofe-kobocat-1 exited with code 0
kobofe-kobocat-1         | wait-for-it: waiting 40 seconds for mongo.REDACTED.private:27017

Is there something I can do to stop Mongo from crashing? I’m using Docker version 23.0.1

1 Like
2

I’ve figured out that my CPU did not support AVX which is required for Mongo 5.0+. After changing to a CPU with AVX enabled, it seems to work.

1 Like
3

@dtrotman :clap: :heart: :partying_face: thank you for sharing the solution with the entire community!