Crash on launch post-update

Support
1

Hello,
I will try to be as detailed as possible. I would appreciate any help
This is regarding a Docker install of a server that worked at some point, but which no longer starts properly.
I’ve had a bit of trouble recently trying to configure my instance to match with the past two updates. My first issue seemed to be a missing media Upload subdomain, which I solved thanks to some previous threads, and the caddy config guide in response to the exploit being patched.
I had previously noticed the high-water-mark message in the akkoma logs when diagnosing issues earlier, but it’s no longer showing up, so I’m not sure if it is a memory issue, but I thought it might be good to know.
I am attempting to start my server using the latest build, after following the docker update instructions in the docs.

When I run using

docker compose down
docker compose up

everything seems to start fine, other than a semi-worrying db-1 | chmod: /var/run/postgresql: Operation not permitted as the first line.

Further down the line, the database seems to disconnect, but I can’t tell for what reason. Running top while starting the services does not show a drastic increase in resource usage, imo.

Here are the logs from when I start using docker compose up

Attaching to akkoma-1, db-1
db-1      | chmod: /var/run/postgresql: Operation not permitted
db-1      |
db-1      | PostgreSQL Database directory appears to contain a database; Skipping initialization
db-1      |
db-1      | 2024-06-03 07:12:24.531 UTC [1] LOG:  starting PostgreSQL 14.12 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
db-1      | 2024-06-03 07:12:24.531 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
db-1      | 2024-06-03 07:12:24.531 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db-1      | 2024-06-03 07:12:24.699 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db-1      | 2024-06-03 07:12:24.913 UTC [14] LOG:  database system was shut down at 2024-06-03 07:12:07 UTC
db-1      | 2024-06-03 07:12:25.174 UTC [1] LOG:  database system is ready to accept connections
akkoma-1  | -- Waiting for database...
akkoma-1  | db:5432 - accepting connections
akkoma-1  | -- Running migrations...
akkoma-1  |
akkoma-1  | 07:12:28.391 [info] Migrations already up
akkoma-1  | -- Starting!
akkoma-1  |
akkoma-1  | 07:12:33.846 [notice] Application web_push_encryption exited: :stopped
akkoma-1  |
akkoma-1  | 07:12:33.861 [notice] Application joken exited: :stopped
akkoma-1  |
akkoma-1  | 07:12:33.878 [info] Found emoji packs: angel-sanctuary
akkoma-1  |
akkoma-1  | 07:12:33.878 [info] No emoji.txt found for pack "angel-sanctuary", assuming all .png, .gif files are emoji
akkoma-1  |
akkoma-1  | 07:12:34.158 [info] Running Pleroma.Web.Endpoint with cowboy 2.12.0 at 0.0.0.0:4000 (http)
akkoma-1  |
akkoma-1  | 07:12:34.166 [info] Access Pleroma.Web.Endpoint at https://{in.stance.url}
akkoma-1  |
akkoma-1  | 07:12:34.231 [info] Postgrex.Protocol (#PID<0.656.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.1042.0> exited
db-1      | 2024-06-03 07:12:34.244 UTC [39] ERROR:  canceling statement due to user request
db-1      | 2024-06-03 07:12:34.244 UTC [39] STATEMENT:  SELECT d0."id", d0."name", d0."state", d0."feature_lock", d0."params", d0."data", d0."inserted_at", d0."updated_at" FROM "data_migrations" AS d0 WHERE (d0."name" = $1)
db-1      | 2024-06-03 07:12:34.244 UTC [39] LOG:  could not send data to client: Broken pipe
db-1      | 2024-06-03 07:12:34.244 UTC [39] FATAL:  connection to client lost
akkoma-1  |
akkoma-1  | 07:12:34.294 [info] Postgrex.Protocol (#PID<0.657.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.826.0> exited
akkoma-1  |
akkoma-1  | 07:12:34.301 [notice] Application pleroma exited: :stopped
db-1      | 2024-06-03 07:12:34.308 UTC [38] ERROR:  canceling statement due to user request
db-1      | 2024-06-03 07:12:34.308 UTC [38] STATEMENT:  SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1)
db-1      | 2024-06-03 07:12:34.311 UTC [38] LOG:  could not send data to client: Broken pipe
db-1      | 2024-06-03 07:12:34.311 UTC [38] FATAL:  connection to client lost
akkoma-1  |
akkoma-1  | 07:12:34.814 [notice] Application web_push_encryption exited: :stopped
akkoma-1  |
akkoma-1  | 07:12:34.815 [notice] Application joken exited: :stopped
akkoma-1  |
akkoma-1  | 07:12:34.816 [info] Found emoji packs: angel-sanctuary
akkoma-1  |
akkoma-1  | 07:12:34.816 [info] No emoji.txt found for pack "angel-sanctuary", assuming all .png, .gif files are emoji
akkoma-1  |
akkoma-1  | 07:12:34.841 [info] Running Pleroma.Web.Endpoint with cowboy 2.12.0 at 0.0.0.0:4000 (http)
akkoma-1  |
akkoma-1  | 07:12:34.841 [info] Access Pleroma.Web.Endpoint at https://{in.stance.url}

I’d be happy to share any parts of my config that may help to shed light on the problem, if necessary

Thank you for your time!

2

your logs show a successful startup, but you say it crashes?

i dont see a crash, nor have you described how it crashes

3

You’re right, there was never a crash. I mistook the database disconnecting for the reason why the frontend would 502.
Turns out it was as simple as that my reverse proxy couldn’t route to the server, because I didn’t realize that upgrading would erase the changes I made to docker-compose.yml. I’ve learnt my lesson now and put those changes in docker-compose.override.yml. Front-end works as expected.

Thanks for your time

1 Like