Akkoma fails to start

Support
1

I installed Akkoma, set up a few accounts, and changed some settings in admin-fe. It said I needed to restart Akkoma to apply some of them, and now it won’t start :D

$ sudo systemctl status akkoma
● akkoma.service - Akkoma social network
     Loaded: loaded (/etc/systemd/system/akkoma.service; enabled; preset: enabled)
     Active: active (running) since Sat 2023-09-23 16:53:10 MDT; 35s ago
   Main PID: 560103 (beam.smp)
      Tasks: 34 (limit: 779)
        CPU: 56.570s
     CGroup: /system.slice/akkoma.service
             ├─560103 /opt/akkoma/erts-13.2.2.2/bin/beam.smp -- -root /opt/akkoma -bindir /opt/akkoma/erts-13.2.2.2/bin -progname erl -- -home /opt/akkoma -- -noshell -s elixir start_cli -mode embedded -setcookie FJO4CPLAH6N5W5RWMNKPZ3QQROT644E4XZMPHAWKHXDV6AZCF57Q==== -name pleroma@127.0.0.1 -config /opt/akkoma/releases/3.10.4-0-gebfb617/sys -boot /opt/akkoma/releases/3.10.4-0-gebfb617/start -boot_var RELEASE_LIB /opt/akkoma/lib -- -extra --no-halt
             ├─560139 erl_child_setup 1024
             ├─560236 /opt/akkoma/lib/fast_html-2.2.0/priv/fasthtml_worker
             ├─560237 /opt/akkoma/lib/fast_html-2.2.0/priv/fasthtml_worker
             ├─560238 /opt/akkoma/lib/fast_html-2.2.0/priv/fasthtml_worker
             ├─560239 /opt/akkoma/lib/fast_html-2.2.0/priv/fasthtml_worker
             ├─560240 sh -s disksup
             ├─560241 /opt/akkoma/lib/os_mon-2.8.2/priv/bin/memsup
             ├─560242 /opt/akkoma/lib/os_mon-2.8.2/priv/bin/cpu_sup
             ├─560244 /opt/akkoma/erts-13.2.2.2/bin/inet_gethost 4
             └─560245 /opt/akkoma/erts-13.2.2.2/bin/inet_gethost 4

Sep 23 16:53:42 ruby pleroma[560103]:             (kernel 8.5.4.1) application_master.erl:293: :application_master.start_it_old/4
Sep 23 16:53:42 ruby pleroma[560103]: 16:53:42.799 [error] GenServer Restarter.Pleroma terminating
Sep 23 16:53:42 ruby pleroma[560103]: ** (MatchError) no match of right hand side value: {:error, {:bad_return, {{Pleroma.Application, :start, [:normal, []]}, {:EXIT, {%Pleroma.ApplicationRequirements.VerifyError{message: "System commands missing. Check logs and see `docs/installation` for more details."}, [{Pleroma.ApplicationRequirements, :handle_result, 1, [file: ~c"lib/pleroma/application_requirements.ex", line: 32]}, {Pleroma.Application, :start, 2, [file: ~c"lib/pleroma/application.ex", line: 55]}, {:application_master, :start_it_old, 4, [file: ~c"application_master.erl", line: 293]}]}}}}}
Sep 23 16:53:42 ruby pleroma[560103]:     (restarter 0.1.0) lib/pleroma.ex:104: Restarter.Pleroma.do_restart/1
Sep 23 16:53:42 ruby pleroma[560103]:     (restarter 0.1.0) lib/pleroma.ex:96: Restarter.Pleroma.handle_cast/2
Sep 23 16:53:42 ruby pleroma[560103]:     (stdlib 4.3.1.2) gen_server.erl:1123: :gen_server.try_dispatch/4
Sep 23 16:53:42 ruby pleroma[560103]:     (stdlib 4.3.1.2) gen_server.erl:1200: :gen_server.handle_msg/6
Sep 23 16:53:42 ruby pleroma[560103]:     (stdlib 4.3.1.2) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Sep 23 16:53:42 ruby pleroma[560103]: Last message: {:"$gen_cast", {:after_boot, :prod}}
Sep 23 16:53:42 ruby pleroma[560103]: State: %{after_boot: false, need_reboot: false, rebooted: false}
2

Needed to install ffmpeg and imagemagick, maybe the message should be updated to include the missing commands?

3

The logs should already have the missing dependencies, and also what filter they are required for akkoma/application_requirements.ex at develop - akkoma - Akkoma Development

My guess is that those log lines were cut off by systemctl status. A way to check the logs is journalctl -u akkoma. Or if you only want the last e.g. 100 lines, you can do journalctl -u akkoma -n 100