Recently updated my Akkoma instance to the latest build earlier today but after the upgrade was done, I keep getting Internal Server Error. Troubleshooting the issue, it appears that the updated version of Akkoma no longer listens on port 4000.
I checked using netstat and port 4000 is no longer bound.
At first I thought there was an issue with my Erlang & Elixir install so I updated it to this version:
Thanks for the prompt response, much appreciated. When trying to start Akkoma manually, it seems to just completely crashed out whereas starting it from systemctl seems to run the software but without listening on port 4000.
Not sure why it’s crashing out when running it manually…
I find it strange to have a different problem between running manually and running with systemctl. Could it be that some actions (git or mix most probably) were done with another user than the akkoma user? If so, maybe some files have wrong ownership, and now maybe we’re seeing weird bugs due to that. (I think chown -R akkoma:akkoma /opt/akkoma/ should fix that then?)
Another very wild guess is that maybe the build got corrupted by switching between elixir/otp/erlang versions or smthng. If so, maybe recompiling can help. The way I do that is: stop Akkoma, then in the akkoma folder rm -rf ./_build && systemctl restart akkoma and wait for it to recompile. It’s just a wild guess, but I remember years ago I had to do that once because I also had all kind of unexplainable weirdness.
I went reading through the code a bit, and the default returned for Config.Holder.default_config(group, key) is :nil, but I would expect for can_be_merged/2 to return false in that case because nil fails the is_list guard clause, thus returning the value.
Is it possible this is getting executed before the Application env for logger is actually set?
Thanks for looking into this, much appreciated. Can you please let me know how I can apply these patches to my existing install?
I also tried doing the cleaning the deps but that didn’t seem to fix it, during the mix.compile, it seems to suggest that there were some warn messages when compiling the pleroma app: https://pastes.io/t0mka2q0xw
However, if I try starting it from systemctl, it doesn’t & I have no clue why. Is there something wrong with the akkoma.service file? Here’s a copy of my akkoma.service file: https://pastes.io/kxrrkwj3oi