@graf @alex @matty Seem to be getting somewhere.
** (EXIT from #PID<0.94.0>) shutdown: failed to start child: Pleroma.Config.TransferTask ** (EXIT) an exception was raised: ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2785ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by: 1. Ensuring your database is available and that you can connect to it 2. Tracking down slow queries and making sure they are running fast enough 3. Increasing the pool_size (although this increases resource consumption) 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval See DBConnection.start_link/2 for more information (ecto_sql 3.9.0) lib/ecto/adapters/sql.ex:905: Ecto.Adapters.SQL.raise_sql_call_error/1 (ecto_sql 3.9.0) lib/ecto/adapters/sql.ex:820: Ecto.Adapters.SQL.execute/6 (ecto 3.9.1) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4 (ecto 3.9.1) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3 (pleroma 2.4.53-2100-g64945b3b.develop+soapbox) lib/pleroma/config/transfer_task.ex:47: Pleroma.Config.TransferTask.load_and_update_env/2 (pleroma 2.4.53-2100-g64945b3b.develop+soapbox) lib/pleroma/config/transfer_task.ex:36: Pleroma.Config.TransferTask.start_link/1 (stdlib 3.17.2) supervisor.erl:414: :supervisor.do_start_child_i/3 (stdlib 3.17.2) supervisor.erl:400: :supervisor.do_start_child/2