2022-11-12 02:49:17
2022-11-11 22:03:04
2022-11-11 20:34:11
888009
@alex hi Alex, i am trying to create admin profile, but having some issue and have no idea how to resolve it. please take a look at:
** (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 2949ms. 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-1901-gaa926ce3.develop+soapbox) lib/pleroma/config/transfer_task.ex:47: Pleroma.Config.TransferTask.load_and_update_env/2
(pleroma 2.4.53-1901-gaa926ce3.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
** (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 2949ms. 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-1901-gaa926ce3.develop+soapbox) lib/pleroma/config/transfer_task.ex:47: Pleroma.Config.TransferTask.load_and_update_env/2
(pleroma 2.4.53-1901-gaa926ce3.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
Alex Gleason
•Tony
•sudo -Hu glitch bash -i -c MIX_ENV=prod mix pleroma.user new tony tony@example.com
--admin
Alex Gleason
•(I wonder if there's a problem with your user not being named `pleroma`)
Tony
•Alex Gleason likes this.
Alex Gleason
•Allow to specify post language, add content translations and language auto-detection (!196) · Merge requests · Soapbox / Rebased · GitLab
GitLabTony
•but nothing
Alex Gleason
•journalctl -u pleroma --since "5 minutes ago"
andtail /var/log/nginx/error.log
Tony
•Alex Gleason
•pleroma
and chown everything topleroma:pleroma
. You overcomplicated it by changing the username.