AkkomaGang/akkoma
AkkomaGang/akkoma
15
66
Fork 94
Code Issues 180 Pull requests 27 Projects 2 Releases 14 Packages Wiki Activity

[bug] Akkoma throws errors and loses connection to Postgres #663

New issue
Closed
opened 2023-11-16 20:27:37 +00:00 by askiiart · 4 comments
askiiart commented 2023-11-16 20:27:37 +00:00
Copy link

Your setup

Docker

Extra details

Docker on Debian 12

Version

ebfb617

PostgreSQL version

14

What were you trying to do?

I was trying to start and access Akkoma.

What did you expect to happen?

It should have worked as normal.

What actually happened?

Akkoma threw several errors in the log, and returns this when I try to access it

{"errors":{"detail":"Internal server error"}}

This usually happens when first starting Akkoma, but sometimes it works fine for several hours then only crashes later.

Note: the logs go further back, but it's just waiting for postgres to start up.

Logs

akkoma-db  | 2023-11-16 20:07:08.350 UTC [210] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:09.354 UTC [211] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:10.357 UTC [212] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:10.620 UTC [14] LOG:  database system was not properly shut down; automatic recovery in progress
akkoma-db  | 2023-11-16 20:07:11.248 UTC [14] LOG:  redo starts at 1D/C0B93F38
akkoma-db  | 2023-11-16 20:07:11.359 UTC [213] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:12.361 UTC [214] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:13.363 UTC [215] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:14.372 UTC [216] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:15.383 UTC [217] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:16.386 UTC [218] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:17.392 UTC [219] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:18.247 UTC [14] LOG:  invalid record length at 1D/C1F6D898: wanted 24, got 0
akkoma-db  | 2023-11-16 20:07:18.247 UTC [14] LOG:  redo done at 1D/C1F6D860 system usage: CPU: user: 0.05 s, system: 0.05 s, elapsed: 6.99 s
akkoma-db  | 2023-11-16 20:07:18.399 UTC [220] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:19.403 UTC [221] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:20.411 UTC [222] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:21.415 UTC [223] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:22.420 UTC [224] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:23.428 UTC [225] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:24.433 UTC [226] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:25.436 UTC [227] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:26.438 UTC [228] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:27.441 UTC [229] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:28.444 UTC [230] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:29.447 UTC [231] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:30.456 UTC [232] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:31.466 UTC [233] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:32.478 UTC [234] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:33.510 UTC [235] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:34.513 UTC [236] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:35.529 UTC [237] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:36.571 UTC [238] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:37.598 UTC [239] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:38.600 UTC [240] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:39.602 UTC [241] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:40.604 UTC [242] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:41.606 UTC [243] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:42.608 UTC [244] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:43.610 UTC [245] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:44.615 UTC [246] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:45.620 UTC [247] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:46.622 UTC [248] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:47.626 UTC [249] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:48.647 UTC [250] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:49.653 UTC [251] FATAL:  the database system is starting up
akkoma-db  | 2023-11-16 20:07:49.750 UTC [1] LOG:  database system is ready to accept connections
akkoma     | 
akkoma     | 20:11:27.263 [info] Found emoji packs: Blobhajes, Misc, Tom Scott, neocat, neofox, blobfox_flip
akkoma     | 
akkoma     | 20:11:27.264 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/Blobhajes/pack.json
akkoma     | 
akkoma     | 20:11:27.449 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/Misc/pack.json
akkoma     | 
akkoma     | 20:11:27.462 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/Tom Scott/pack.json
akkoma     | 
akkoma     | 20:11:27.470 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/neocat/pack.json
akkoma     | 
akkoma     | 20:11:27.520 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/neofox/pack.json
akkoma     | 
akkoma     | 20:11:27.540 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/blobfox_flip/pack.json
akkoma     | 
akkoma     | 20:11:28.517 [info] The function passed as a handler with ID "oban-monitor-failure" is a local function.
akkoma     | This means that it is either an anonymous function or a capture of a function without a module specified. That may cause a performance penalty when calling that handler. For more details see the note in `telemetry:attach/4` documentation.
akkoma     | 
akkoma     | https://hexdocs.pm/telemetry/telemetry.html#attach/4
akkoma     | 
akkoma     | 20:11:28.518 [info] The function passed as a handler with ID "oban-monitor-success" is a local function.
akkoma     | This means that it is either an anonymous function or a capture of a function without a module specified. That may cause a performance penalty when calling that handler. For more details see the note in `telemetry:attach/4` documentation.
akkoma     | 
akkoma     | https://hexdocs.pm/telemetry/telemetry.html#attach/4
akkoma     | 
akkoma     | 20:11:34.750 [info] Running Pleroma.Web.Endpoint with cowboy 2.10.0 at 0.0.0.0:4000 (http)
akkoma     | 
akkoma     | 20:11:34.759 [info] Access Pleroma.Web.Endpoint at https://fedi.askiiart.net
akkoma     | 
akkoma     | 20:11:39.761 [error] Error when calling MFA defined by measurement: Pleroma.Web.Telemetry :instance_stats []
akkoma     | Class=:exit
akkoma     | Reason={:timeout, {GenServer, :call, [Pleroma.Stats, :get_state, 5000]}}
akkoma     | Stacktrace=[
akkoma     |   {GenServer, :call, 3, [file: ~c"lib/gen_server.ex", line: 1074]},
akkoma     |   {Pleroma.Stats, :get_stats, 0, [file: ~c"lib/pleroma/stats.ex", line: 45]},
akkoma     |   {Pleroma.Web.Telemetry, :instance_stats, 0,
akkoma     |    [file: ~c"lib/pleroma/web/telemetry.ex", line: 142]},
akkoma     |   {:telemetry_poller, :make_measurement, 1,
akkoma     |    [
akkoma     |      file: ~c"/opt/akkoma/deps/telemetry_poller/src/telemetry_poller.erl",
akkoma     |      line: 322
akkoma     |    ]},
akkoma     |   {:telemetry_poller, :"-make_measurements_and_filter_misbehaving/1-lc$^0/1-0-",
akkoma     |    1,
akkoma     |    [
akkoma     |      file: ~c"/opt/akkoma/deps/telemetry_poller/src/telemetry_poller.erl",
akkoma     |      line: 318
akkoma     |    ]},
akkoma     |   {:telemetry_poller, :handle_info, 2,
akkoma     |    [
akkoma     |      file: ~c"/opt/akkoma/deps/telemetry_poller/src/telemetry_poller.erl",
akkoma     |      line: 340
akkoma     |    ]},
akkoma     |   {:gen_server, :try_dispatch, 4, [file: ~c"gen_server.erl", line: 1123]},
akkoma     |   {:gen_server, :handle_msg, 6, [file: ~c"gen_server.erl", line: 1200]}
akkoma     | ]
akkoma     | 
akkoma     | 
akkoma     | 20:11:43.779 [error] Postgrex.Protocol (#PID<0.657.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.800.0> timed out because it queued and checked out the connection for longer than 15000ms
akkoma     | 
akkoma     | #PID<0.800.0> was at location:
akkoma     | 
akkoma     |     :prim_inet.recv0/3
akkoma     |     (postgrex 0.17.2) lib/postgrex/protocol.ex:3188: Postgrex.Protocol.msg_recv/4
akkoma     |     (postgrex 0.17.2) lib/postgrex/protocol.ex:2213: Postgrex.Protocol.recv_bind/3
akkoma     |     (postgrex 0.17.2) lib/postgrex/protocol.ex:2068: Postgrex.Protocol.bind_execute_close/4
akkoma     |     (db_connection 2.5.0) lib/db_connection/holder.ex:354: DBConnection.Holder.holder_apply/4
akkoma     |     (db_connection 2.5.0) lib/db_connection.ex:1432: DBConnection.run_execute/5
akkoma     |     (db_connection 2.5.0) lib/db_connection.ex:1527: DBConnection.run/6
akkoma     |     (db_connection 2.5.0) lib/db_connection.ex:656: DBConnection.parsed_prepare_execute/5
akkoma     | 
akkoma     | 
akkoma     | 20:11:43.785 [error] GenServer Pleroma.Stats terminating
akkoma     | ** (DBConnection.ConnectionError) tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
akkoma     |     (ecto_sql 3.10.1) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
akkoma     |     (ecto_sql 3.10.1) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
akkoma     |     (ecto 3.10.3) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
akkoma     |     (ecto 3.10.3) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
akkoma     |     (pleroma 3.10.4-0-gebfb617) lib/pleroma/stats.ex:73: Pleroma.Stats.calculate_stat_data/0
akkoma     |     (pleroma 3.10.4-0-gebfb617) lib/pleroma/stats.ex:121: Pleroma.Stats.handle_continue/2
akkoma     |     (stdlib 4.3.1.2) gen_server.erl:1123: :gen_server.try_dispatch/4
akkoma     |     (stdlib 4.3.1.2) gen_server.erl:865: :gen_server.loop/7
akkoma     | Last message: {:continue, :calculate_stats}
akkoma     | State: nil
akkoma-db  | 2023-11-16 20:11:43.859 UTC [267] ERROR:  canceling statement due to user request
akkoma-db  | 2023-11-16 20:11:43.859 UTC [267] STATEMENT:  SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1)
akkoma-db  | 2023-11-16 20:11:43.861 UTC [267] LOG:  could not send data to client: Broken pipe
akkoma-db  | 2023-11-16 20:11:43.861 UTC [267] FATAL:  connection to client lost

Severity

I cannot use the software

Have you searched for this issue?

  • I have double-checked and have not found this issue mentioned anywhere.
### Your setup Docker ### Extra details Docker on Debian 12 ### Version ebfb617 ### PostgreSQL version 14 ### What were you trying to do? I was trying to start and access Akkoma. ### What did you expect to happen? It should have worked as normal. ### What actually happened? Akkoma threw several errors in the log, and returns this when I try to access it ```json {"errors":{"detail":"Internal server error"}} ``` This usually happens when first starting Akkoma, but sometimes it works fine for several hours then only crashes later. Note: the logs go further back, but it's just waiting for postgres to start up. ### Logs ```shell akkoma-db | 2023-11-16 20:07:08.350 UTC [210] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:09.354 UTC [211] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:10.357 UTC [212] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:10.620 UTC [14] LOG: database system was not properly shut down; automatic recovery in progress akkoma-db | 2023-11-16 20:07:11.248 UTC [14] LOG: redo starts at 1D/C0B93F38 akkoma-db | 2023-11-16 20:07:11.359 UTC [213] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:12.361 UTC [214] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:13.363 UTC [215] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:14.372 UTC [216] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:15.383 UTC [217] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:16.386 UTC [218] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:17.392 UTC [219] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:18.247 UTC [14] LOG: invalid record length at 1D/C1F6D898: wanted 24, got 0 akkoma-db | 2023-11-16 20:07:18.247 UTC [14] LOG: redo done at 1D/C1F6D860 system usage: CPU: user: 0.05 s, system: 0.05 s, elapsed: 6.99 s akkoma-db | 2023-11-16 20:07:18.399 UTC [220] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:19.403 UTC [221] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:20.411 UTC [222] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:21.415 UTC [223] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:22.420 UTC [224] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:23.428 UTC [225] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:24.433 UTC [226] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:25.436 UTC [227] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:26.438 UTC [228] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:27.441 UTC [229] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:28.444 UTC [230] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:29.447 UTC [231] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:30.456 UTC [232] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:31.466 UTC [233] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:32.478 UTC [234] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:33.510 UTC [235] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:34.513 UTC [236] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:35.529 UTC [237] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:36.571 UTC [238] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:37.598 UTC [239] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:38.600 UTC [240] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:39.602 UTC [241] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:40.604 UTC [242] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:41.606 UTC [243] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:42.608 UTC [244] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:43.610 UTC [245] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:44.615 UTC [246] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:45.620 UTC [247] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:46.622 UTC [248] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:47.626 UTC [249] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:48.647 UTC [250] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:49.653 UTC [251] FATAL: the database system is starting up akkoma-db | 2023-11-16 20:07:49.750 UTC [1] LOG: database system is ready to accept connections akkoma | akkoma | 20:11:27.263 [info] Found emoji packs: Blobhajes, Misc, Tom Scott, neocat, neofox, blobfox_flip akkoma | akkoma | 20:11:27.264 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/Blobhajes/pack.json akkoma | akkoma | 20:11:27.449 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/Misc/pack.json akkoma | akkoma | 20:11:27.462 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/Tom Scott/pack.json akkoma | akkoma | 20:11:27.470 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/neocat/pack.json akkoma | akkoma | 20:11:27.520 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/neofox/pack.json akkoma | akkoma | 20:11:27.540 [info] Loading emoji pack from JSON: /opt/akkoma/instance/static/emoji/blobfox_flip/pack.json akkoma | akkoma | 20:11:28.517 [info] The function passed as a handler with ID "oban-monitor-failure" is a local function. akkoma | This means that it is either an anonymous function or a capture of a function without a module specified. That may cause a performance penalty when calling that handler. For more details see the note in `telemetry:attach/4` documentation. akkoma | akkoma | https://hexdocs.pm/telemetry/telemetry.html#attach/4 akkoma | akkoma | 20:11:28.518 [info] The function passed as a handler with ID "oban-monitor-success" is a local function. akkoma | This means that it is either an anonymous function or a capture of a function without a module specified. That may cause a performance penalty when calling that handler. For more details see the note in `telemetry:attach/4` documentation. akkoma | akkoma | https://hexdocs.pm/telemetry/telemetry.html#attach/4 akkoma | akkoma | 20:11:34.750 [info] Running Pleroma.Web.Endpoint with cowboy 2.10.0 at 0.0.0.0:4000 (http) akkoma | akkoma | 20:11:34.759 [info] Access Pleroma.Web.Endpoint at https://fedi.askiiart.net akkoma | akkoma | 20:11:39.761 [error] Error when calling MFA defined by measurement: Pleroma.Web.Telemetry :instance_stats [] akkoma | Class=:exit akkoma | Reason={:timeout, {GenServer, :call, [Pleroma.Stats, :get_state, 5000]}} akkoma | Stacktrace=[ akkoma | {GenServer, :call, 3, [file: ~c"lib/gen_server.ex", line: 1074]}, akkoma | {Pleroma.Stats, :get_stats, 0, [file: ~c"lib/pleroma/stats.ex", line: 45]}, akkoma | {Pleroma.Web.Telemetry, :instance_stats, 0, akkoma | [file: ~c"lib/pleroma/web/telemetry.ex", line: 142]}, akkoma | {:telemetry_poller, :make_measurement, 1, akkoma | [ akkoma | file: ~c"/opt/akkoma/deps/telemetry_poller/src/telemetry_poller.erl", akkoma | line: 322 akkoma | ]}, akkoma | {:telemetry_poller, :"-make_measurements_and_filter_misbehaving/1-lc$^0/1-0-", akkoma | 1, akkoma | [ akkoma | file: ~c"/opt/akkoma/deps/telemetry_poller/src/telemetry_poller.erl", akkoma | line: 318 akkoma | ]}, akkoma | {:telemetry_poller, :handle_info, 2, akkoma | [ akkoma | file: ~c"/opt/akkoma/deps/telemetry_poller/src/telemetry_poller.erl", akkoma | line: 340 akkoma | ]}, akkoma | {:gen_server, :try_dispatch, 4, [file: ~c"gen_server.erl", line: 1123]}, akkoma | {:gen_server, :handle_msg, 6, [file: ~c"gen_server.erl", line: 1200]} akkoma | ] akkoma | akkoma | akkoma | 20:11:43.779 [error] Postgrex.Protocol (#PID<0.657.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.800.0> timed out because it queued and checked out the connection for longer than 15000ms akkoma | akkoma | #PID<0.800.0> was at location: akkoma | akkoma | :prim_inet.recv0/3 akkoma | (postgrex 0.17.2) lib/postgrex/protocol.ex:3188: Postgrex.Protocol.msg_recv/4 akkoma | (postgrex 0.17.2) lib/postgrex/protocol.ex:2213: Postgrex.Protocol.recv_bind/3 akkoma | (postgrex 0.17.2) lib/postgrex/protocol.ex:2068: Postgrex.Protocol.bind_execute_close/4 akkoma | (db_connection 2.5.0) lib/db_connection/holder.ex:354: DBConnection.Holder.holder_apply/4 akkoma | (db_connection 2.5.0) lib/db_connection.ex:1432: DBConnection.run_execute/5 akkoma | (db_connection 2.5.0) lib/db_connection.ex:1527: DBConnection.run/6 akkoma | (db_connection 2.5.0) lib/db_connection.ex:656: DBConnection.parsed_prepare_execute/5 akkoma | akkoma | akkoma | 20:11:43.785 [error] GenServer Pleroma.Stats terminating akkoma | ** (DBConnection.ConnectionError) tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated) akkoma | (ecto_sql 3.10.1) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1 akkoma | (ecto_sql 3.10.1) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6 akkoma | (ecto 3.10.3) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4 akkoma | (ecto 3.10.3) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3 akkoma | (pleroma 3.10.4-0-gebfb617) lib/pleroma/stats.ex:73: Pleroma.Stats.calculate_stat_data/0 akkoma | (pleroma 3.10.4-0-gebfb617) lib/pleroma/stats.ex:121: Pleroma.Stats.handle_continue/2 akkoma | (stdlib 4.3.1.2) gen_server.erl:1123: :gen_server.try_dispatch/4 akkoma | (stdlib 4.3.1.2) gen_server.erl:865: :gen_server.loop/7 akkoma | Last message: {:continue, :calculate_stats} akkoma | State: nil akkoma-db | 2023-11-16 20:11:43.859 UTC [267] ERROR: canceling statement due to user request akkoma-db | 2023-11-16 20:11:43.859 UTC [267] STATEMENT: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) akkoma-db | 2023-11-16 20:11:43.861 UTC [267] LOG: could not send data to client: Broken pipe akkoma-db | 2023-11-16 20:11:43.861 UTC [267] FATAL: connection to client lost ``` ### Severity I cannot use the software ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.
askiiart added the
bug
 label 2023-11-16 20:27:37 +00:00
floatingghost commented 2023-11-16 20:30:08 +00:00
Owner
Copy link

this sounds like you have a very overloaded server - the postgres container typically starts up in <5seconds

what are you running on?

this sounds like you have a very overloaded server - the postgres container typically starts up in <5seconds what are you running on?
askiiart commented 2023-11-16 20:49:23 +00:00
Author
Copy link

what are you running on?

I'm on an Intel i5-12400 with 24GB RAM. I've got Akkoma on the hard drives, which often get pretty loaded, so I'll try moving Akkoma to the SSD and see if that improves it.

> what are you running on? I'm on an Intel i5-12400 with 24GB RAM. I've got Akkoma on the hard drives, which often get pretty loaded, so I'll try moving Akkoma to the SSD and see if that improves it.
askiiart commented 2023-11-16 20:58:22 +00:00
Author
Copy link

Ok ok huge issue on my part: SnapRAID is syncing, which is absolutely pinning the hard drives. My bad!

Once snapraid's done I'll give this a try again, I'll let you know how it goes then, and if that goes well, I'll close this issue then.

Ok ok huge issue on my part: SnapRAID is syncing, which is absolutely pinning the hard drives. My bad! Once snapraid's done I'll give this a try again, I'll let you know how it goes then, and if that goes well, I'll close this issue then.
askiiart commented 2023-11-16 21:48:26 +00:00
Author
Copy link

Yep, that was the issue. Closing this now, sorry about that.

Yep, that was the issue. Closing this now, sorry about that.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
better-stats
stable
translations
customizable-docker-db
static-adminfe
bad-uploader-config-warning
docker
user-expiry-backfill
config-db-keys
ensure-scrubbers-loaded
otp26
code-shaking-does-not-go-brr
elixir1.15
circleci
backup-fixes
mod-task
policy
mrf-coolness
frontend-switcher-9000
contentMap
language-on-posts
rabbit
credo-on-pr
unify-http
normalise-markup-by-default
buildx
v3.13.3
v3.13.2
v2.6.3
v3.13.1
v3.13.0
snac-3.12.1.2
v3.12.2
snac-3.12.1.1
v3.12.1
v3.12.0
v3.11.0
v2.6.2
v2.6.1
2.6.1
v2.6.0
v2.5.5
v3.10.4
v3.10.3
v3.10.2
v3.10.1
v3.10.0
v2.5.4
v2.5.3
v3.9.3
v3.9.2
v3.9.1
V3.9.0
2023.05
v3.8.0
v3.7.1
v3.7.0
v3.6.0
v3.5.0
v2.4.5
v3.4.0
v3.3.1
v2.4.4
v3.3.0
v3.2.3
v3.2.2
v3.2.1
stable-202209
v3.2.0
v3.1.0
stable-2022.07
v3.0.0
v0.0.1
v2.5.2-6
v2.5.2-5
v2.5.2-4
v2.5.2-3
v2.5.2-2
v2.5.2-1
v2.5.2
v2.5.1
v2.5.0-8
v2.5.0-7
v2.5.0-6
v2.5.0-5
v2.5.0-4
v2.5.0-3
v2.5.0-2
v2.5.0-1
v2.5.0
v2.4.3
pre-rebase
v2.4.2
v2.4.1
v2.4.0
soapbox-v1.1.1
soapbox-v1.1.0
soapbox-v1.0.0
v2.3.0
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.7
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.1.9
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.91
v1.0.90
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
v0.9.0
Labels
Clear labels   
approved, awaiting change

   
bug

Something is not working

  
configuration

This requires config changes

  
documentation

This is about human-readable docs

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
extremely low priority

   
feature request

Something new?

  
Fix it yourself

Support has been attempted

  
help wanted

Need some help

  
invalid

Something is wrong

  
mastodon_api

   
needs docs

   
needs tests

   
not a bug

   
planned

   
pleroma_api

   
privacy

   
question

More information is needed

  
static_fe

   
triage

   
wontfix

This won't be fixed

No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#663
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?