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'.