Post AtDdkpSJ5SYTgMbYkS by silverpill@mitra.social
 (DIR) More posts by silverpill@mitra.social
 (DIR) Post #AtDOOmp4hExNpkHljc by japananon@mitra.anon-kenkai.com
       2025-04-18T12:12:47.564831Z
       
       1 likes, 0 repeats
       
       Test post. This is being posted via Mitra v4.0.0Server 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.
       
 (DIR) Post #AtDPnsqtW4zvj8fTHM by japananon@mitra.anon-kenkai.com
       2025-04-18T12:28:38.419677Z
       
       0 likes, 0 repeats
       
       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"
       
 (DIR) Post #AtDSNMsu33sgulehCy by japananon@mitra.anon-kenkai.com
       2025-04-18T12:57:27.257445Z
       
       0 likes, 0 repeats
       
       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 CLIApr 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 serverApr 18 14:37:51 my-mitra mitra[1636]:   update-config              Change value of a dynamic configuration parameterApr 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/INVALIDARGUMENTApr 18 14:14:04 my-mitra systemd[1]: mitra.service: Failed with result 'exit-code'.
       
 (DIR) Post #AtDU6NyIx9bRGuDCIS by japananon@mitra.anon-kenkai.com
       2025-04-18T13:16:47.709830Z
       
       0 likes, 0 repeats
       
       Problem solved... had an old redundant service file in /etc/systemd/system that was overriding the newer one.
       
 (DIR) Post #AtDWbdm4RtPxAUWLeS by silverpill@mitra.social
       2025-04-18T13:44:28.137616Z
       
       0 likes, 0 repeats
       
       @japananon Yeah, I hope it was not much trouble. Future major releases are going to be less disruptive
       
 (DIR) Post #AtDXBiaO2MG2W3G6Vs by japananon@mitra.anon-kenkai.com
       2025-04-18T13:51:21.928577Z
       
       0 likes, 0 repeats
       
       @silverpill I think this one's largely on me. I didn't realize the priority order of unit files, and I frankly don't even remember how a redundant one got made there.
       
 (DIR) Post #AtDdkoP4zyNaQ45T4y by chris@mitra.northumbria.me
       2025-04-18T14:10:07.774469Z
       
       0 likes, 0 repeats
       
       @silverpill @japananon Using the bleakfuture docker images it was completely painless.systemctl --user stop container-pod1mitra.servicepodman pull bleakfuture0/mitra:latestsystemctl --user start container-pod1mitra.serviceI then had to modify my backup script where it calledpodman exec -it  pod1mitra mitra list-local-files
       
 (DIR) Post #AtDdkpSJ5SYTgMbYkS by silverpill@mitra.social
       2025-04-18T15:04:34.420264Z
       
       0 likes, 0 repeats
       
       @chris @japananon contrib/docker/Dockerfile has been updated toohttps://codeberg.org/silverpill/mitra/src/branch/main/contrib/docker/Dockerfile(this is how bleakfuture image is built)