Conversation

Notices

1. Embed this notice
   チャノさん (japananon@mitra.anon-kenkai.com)'s status on Friday, 18-Apr-2025 22:45:00 JST チャノさん

   Test post. This is being posted via Mitra v4.0.0

   Server is behaving weirdly... systemctl shows the mitra process as having failed to start, but the server actually seems to be running and I don't know why.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 18-Apr-2025 22:44:56 JST silverpill

     in reply to

     @japananon Yeah, I hope it was not much trouble. Future major releases are going to be less disruptive

   • Embed this notice
     チャノさん (japananon@mitra.anon-kenkai.com)'s status on Friday, 18-Apr-2025 22:44:57 JST チャノさん

     in reply to

     Problem solved... had an old redundant service file in /etc/systemd/system that was overriding the newer one.

   • Embed this notice
     チャノさん (japananon@mitra.anon-kenkai.com)'s status on Friday, 18-Apr-2025 22:44:58 JST チャノさん

     in reply to

     • silverpill

     Paging @silverpill , since I'm not certain what to pin this on. the mitra.service file appears to be identical to example in the repo... the "mitra server" command works perfectly fine when manually executed via CLI, but systemctl stumbles over it:

     Apr 18 14:37:51 my-mitra systemd[1]: Started Mitra Server. Apr 18 14:37:51 my-mitra mitra[1636]: Mitra admin CLI Apr 18 14:37:51 my-mitra mitra[1636]: Usage: mitra [OPTIONS] <COMMAND> Apr 18 14:37:51 my-mitra mitra[1636]: Commands: Apr 18 14:37:51 my-mitra mitra[1636]: server Start HTTP server Apr 18 14:37:51 my-mitra mitra[1636]: update-config Change value of a dynamic configuration parameter Apr 18 14:37:51 my-mitra mitra[1636]: add-filter-rule Add federation filter rule ... ... Apr 18 14:14:04 my-mitra systemd[1]: mitra.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Apr 18 14:14:04 my-mitra systemd[1]: mitra.service: Failed with result 'exit-code'.
   • Embed this notice
     チャノさん (japananon@mitra.anon-kenkai.com)'s status on Friday, 18-Apr-2025 22:44:59 JST チャノさん

     in reply to

     I appear to need to manually run the "mitra server" command to start the HTTP server on every server restart. I don't know why this is necessary, but it appears to be systemctl that's fucking it up, because it otherwise works.

     AFAIK the mitra service file has been properly updated along with the rest of the installation, and it's clearly pointing at the correct executable, but it won't start on its own. Logs show "Main process exited. code=exited, status=2/INVALIDARGUMENT"

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 19-Apr-2025 00:05:01 JST silverpill

     in reply to

     • chris

     @chris @japananon contrib/docker/Dockerfile has been updated too

     https://codeberg.org/silverpill/mitra/src/branch/main/contrib/docker/Dockerfile

     (this is how bleakfuture image is built)

   • Embed this notice
     chris@mitra.northumbria.me's status on Saturday, 19-Apr-2025 00:05:03 JST chris

     in reply to

     • silverpill

     @silverpill @japananon Using the bleakfuture docker images it was completely painless.

     systemctl --user stop container-pod1mitra.service podman pull bleakfuture0/mitra:latest systemctl --user start container-pod1mitra.service

     I then had to modify my backup script where it called
     podman exec -it pod1mitra mitra list-local-files