[bug] Migrating from Pleroma with Prometheus metrics on caused Akkoma to crash #382

Closed
opened 2022-12-19 21:55:14 +00:00 by kinetix · 1 comment

Your setup

From source

Extra details

No response

Version

3.5.0-48-g3d546409-develop

PostgreSQL version

13

What were you trying to do?

When trying to run 'pleroma.frontend install' or 'phx.server' for the first time during a switchover/migration from Pleroma, it appears Akkoma choked on the prometheus config in the DB - from what was pasted to IRC last night:

16:57 < Kinetix> MIX_ENV=prod mix pleroma.frontend install pleroma-fe --ref stable
16:57 < Kinetix> ** (EXIT from #PID<0.94.0>) shutdown: failed to start child: Pleroma.Config.TransferTask
16:57 < Kinetix>     ** (EXIT) an exception was raised:
16:57 < Kinetix>         ** (ArgumentError) errors were found at the given arguments:
16:57 < Kinetix>   * 1st argument: not an already existing atom
16:57 < Kinetix>             :erlang.binary_to_existing_atom("Elixir.Pleroma.Web.Endpoint.MetricsExporter", :utf8)

Removing the config entry from the DB allowed Akkoma to start.

What did you expect to happen?

No response

What actually happened?

No response

Logs

No response

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

  • I have double-checked and have not found this issue mentioned anywhere.
### Your setup From source ### Extra details _No response_ ### Version 3.5.0-48-g3d546409-develop ### PostgreSQL version 13 ### What were you trying to do? When trying to run 'pleroma.frontend install' or 'phx.server' for the first time during a switchover/migration from Pleroma, it appears Akkoma choked on the prometheus config in the DB - from what was pasted to IRC last night: ``` 16:57 < Kinetix> MIX_ENV=prod mix pleroma.frontend install pleroma-fe --ref stable 16:57 < Kinetix> ** (EXIT from #PID<0.94.0>) shutdown: failed to start child: Pleroma.Config.TransferTask 16:57 < Kinetix> ** (EXIT) an exception was raised: 16:57 < Kinetix> ** (ArgumentError) errors were found at the given arguments: 16:57 < Kinetix> * 1st argument: not an already existing atom 16:57 < Kinetix> :erlang.binary_to_existing_atom("Elixir.Pleroma.Web.Endpoint.MetricsExporter", :utf8) ``` Removing the config entry from the DB allowed Akkoma to start. ### What did you expect to happen? _No response_ ### What actually happened? _No response_ ### Logs _No response_ ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [ ] I have double-checked and have not found this issue mentioned anywhere.
kinetix added the
bug
label 2022-12-19 21:55:14 +00:00

fixed via af7c3fab98

fixed via af7c3fab98f4f5d1fa541035fd8b2821e0abb77b
Sign in to join this conversation.
No milestone
No project
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#382
No description provided.