Trying to set up a new instance using the instructions here:

https://www.openproject.org/docs/installation-and-operations/installation/docker/#one-container-per-process-recommended

But the compose_web_1 container remains in a persistent starting state.

Its log:

-----> Setting PGVERSION=13 PGBIN=/usr/lib/postgresql/13/bin PGCONF_FILE=/etc/postgresql/13/main/postgresql.conf
=> Booting Puma
=> Rails 6.1.4.6 application starting in production 
=> Run `bin/rails server --help` for more startup options
Exiting

Any idea what's the issue here and how to resolve it?

Hello, this looks like a memory issue maybe? Can you check the free memory on your system while you're starting the processes?

Hi Cyril.

Thanks! That was indeed the case.

Hi, could you please share what was your memory before and after the fix?

We like to improve quality of our  documentation in the threads

These cases will be useful for people who find them in the future, it could be yourself in 5 years :)

Hello, i have the exact same problem.

Log:

-----> Setting PGVERSION=13 PGBIN=/usr/lib/postgresql/13/bin PGCONF_FILE=/etc/postgresql/13/main/postgresql.conf

I noticed no memory issues.

Is there a official solution out there? :D

I am also facing the same issue on RPI4. Doesnt seem like mem issue? is it processor issue? Am on Rpi4 8Gb

crash loop

HI Sunny,

sorry but with RPI4 you are working maybe on a "tuned" and unsupported version. ARM is unsupported by now.

OpenProject COULD run on ARM processors, but this is all kind of community hacks at the moment, you will need to help yourself here, try searching the forum for ARM and PI and MacOS threads, maybe that helps.

I have discoverd OpenProject today and started the docker containers on a Ubuntu  22.04.02 (LTS) using https://www.openproject.org/docs/installation-and-operations/installation/docker/#one-container-per-process-recommended without modifying anything.

After about a minute Puma is shutting down and restarting:

[1] === puma shutdown: 2023-06-21 10:11:56 +0000 ===
[1] - Goodbye!
[1] - Gracefully shutting down workers...
Exiting
-----> Setting PGVERSION=13 PGBIN=/usr/lib/postgresql/13/bin PGCONF_FILE=/etc/postgresql/13/main/postgresql.conf
=> Booting Puma
=> Rails 7.0.4.2 application starting in production 
=> Run `bin/rails server --help` for more startup options
I, [2023-06-21T10:12:20.270315 #1]  INFO -- : Using schema cache file /app/db/schema_cache.yml
[1] Puma starting in cluster mode...
[1] * Puma version: 6.1.1 (ruby 3.2.2-p53) ("The Way Up")
[1] *  Min threads: 4
[1] *  Max threads: 16
[1] *  Environment: production
[1] *   Master PID: 1
[1] *      Workers: 2
[1] *     Restarts: (✔) hot (✖) phased
[1] * Preloading application
[1] * Listening on http://0.0.0.0:8080
[1] Use Ctrl-C to stop
[1] - Worker 0 (PID: 57) booted in 0.01s, phase: 0
[1] - Worker 1 (PID: 61) booted in 0.03s, phase: 0
[1] === puma shutdown: 2023-06-21 10:12:58 +0000 ===
[1] - Goodbye!
[1] - Gracefully shutting down workers...
Exiting
-----> Setting PGVERSION=13 PGBIN=/usr/lib/postgresql/13/bin PGCONF_FILE=/etc/postgresql/13/main/postgresql.conf
=> Booting Puma
=> Rails 7.0.4.2 application starting in production 
=> Run `bin/rails server --help` for more startup options
I, [2023-06-21T10:13:17.681118 #1]  INFO -- : Using schema cache file /app/db/schema_cache.yml
[1] Puma starting in cluster mode...

I got exactly the same problem. ¿Any solution?

Edit:

Upgrading from 12 to 13 on Ubuntu 20 LTS Docker following https://github.com/opf/openproject-deploy/tree/stable/13/compose/control

This looks like it might be due to the auto heal killing the process because it may not appear healthy.

To confirm this we would need all the logs from the auto heal container as well and perhaps also confirm wheather the web container's health check endpoint (/health_checks/default) returns HTTP OK (200).