Medusa installed but wont run

Troubleshooting
1

No idea how to deal with such issues but this is the status:

sudo systemctl status medusa
● medusa.service - Medusa Daemon
   Loaded: loaded (/etc/systemd/system/medusa.service; disabled; vendor preset:
enabled)
   Active: failed (Result: exit-code) since Mon 2020-10-19 22:03:43 B
ST; 4min 34s ago
  Process: 762 ExecStart=/usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py -
q --nolaunch --datadir=/mnt/dietpi_userdata/medusa (code=exited, status=
216/GROUP)
 Main PID: 762 (code=exited, status=216/GROUP)
      CPU: 0

Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, s
cheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Start request repeate
d too quickly.
Oct 19 22:03:43 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed s
tate.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.

If I am reading that correctly the error is “Exit-code” not too helpful
A bit of searching and i tried booting it manually same error when i check the status
uninstalled and re-installed…same error

tried to sudo apt-get python3… it says the latest is already installed same for python
updated dietpi earlier so its all up to date

Completly at a loss as to how to fix

2

Hi,

many thanks for your report. Indeed there seems to be an issue with Medusa. Pls can you post journalctl -u medusa.service

3 
journalctl -u medusa.service
-- Logs begin at Mon 2020-10-19 22:03:15 BST, end at Mon 2020-10-19 22:18:52 BST
. --
Oct 19 22:03:42 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Main process exited,
code=exited, status=216/GROUP
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Unit entered failed s
tate.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Service hold-off time over, s
cheduling restart.
Oct 19 22:03:42 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Main process exited,
code=exited, status=216/GROUP
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Unit entered failed s
tate.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Service hold-off time over, s
cheduling restart.
Oct 19 22:03:42 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Main process exited,
code=exited, status=216/GROUP
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Unit entered failed s
tate.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, s
cheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Main process exited,
code=exited, status=216/GROUP
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed s
tate.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, s
cheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Start request repeated too quickly.
Oct 19 22:03:43 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:48 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:48 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:48 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Start request repeated too quickly.
Oct 19 22:09:49 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.

All double dutch to me.

4

Posted above ^

Is there anything I can do my end to make it work or is it a case of sit back and wait (np if it is, these things happen after all)

5

hmm ok can you try reinstall Medusa. At least you have a different error message I would expect.

dietpi-software reinstall 116
6 



 sudo dietpi-software reinstall 116
[  OK  ] DietPi-Software | Initialised database
[  OK  ] DietPi-Software | Reading database
[ SUB1 ] DietPi-Software > Automated reinstall
[  OK  ] DietPi-Software | Reinstalling Medusa: Automatic Video Library Manager for TV Shows
[  OK  ] DietPi-Software | Free space check: path=/ | available=7697 MiB | required=500 MiB
[  OK  ] DietPi-Software | DietPi-Userdata validation: /mnt/dietpi_userdata
[  OK  ] DietPi-Software | Checking network connectivity
[  OK  ] DietPi-Software | Checking DNS resolver
[  OK  ] Network time sync | Completed
[ SUB2 ] DietPi-Services > unmask
[  OK  ] DietPi-Services | unmask : nzbget
[  OK  ] DietPi-Services | unmask : emby-server
[  OK  ] DietPi-Services | unmask : medusa
[  OK  ] DietPi-Services | unmask : radarr
[  OK  ] DietPi-Services | unmask : syncthing
[  OK  ] DietPi-Services | unmask : docker
[  OK  ] DietPi-Services | unmask : cron
[ SUB2 ] DietPi-Services > stop
[  OK  ] DietPi-Services | stop : cron
[  OK  ] DietPi-Services | stop : docker
[  OK  ] DietPi-Services | stop : syncthing
[  OK  ] DietPi-Services | stop : radarr
[  OK  ] DietPi-Services | stop : medusa
[  OK  ] DietPi-Services | stop : emby-server
[  OK  ] DietPi-Services | stop : nzbget
[  OK  ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads /var/www /opt
[  OK  ] DietPi-Software | chown dietpi:dietpi /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
[  OK  ] DietPi-Software | chmod 775 /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
[ SUB1 ] DietPi-Software > Update & upgrade APT
[ INFO ] DietPi-Software | APT update, please wait...
Hit:2 https://download.docker.com/linux/debian stretch InRelease
Ign:3 https://deb.debian.org/debian stretch InRelease
Hit:4 https://deb.debian.org/debian stretch-updates InRelease
Get:5 https://deb.debian.org/debian-security stretch/updates InRelease [53.0 kB]
Hit:6 https://deb.debian.org/debian stretch-backports InRelease
Hit:7 https://deb.debian.org/debian stretch Release
Hit:8 https://download.mono-project.com/repo/debian stretch InRelease
Hit:1 https://minio.k-space.ee/armbian/apt stretch InRelease
Get:9 https://deb.debian.org/debian-security stretch/updates/main arm64 Packages [584 kB]
Fetched 637 kB in 3s (190 kB/s)
Reading package lists...
[  OK  ] DietPi-Software | APT update
[ INFO ] DietPi-Software | APT upgrade, please wait...
[  OK  ] DietPi-Software | APT upgrade
[ SUB1 ] DietPi-Software > Checking for prerequisite software
[ INFO ] DietPi-Software | UnRAR will be installed
[ SUB1 ] DietPi-Software > Installing UnRAR: unarchiver for .rar files
[ INFO ] DietPi-Software | APT install for: unrar, please wait...
[  OK  ] DietPi-Software | APT install for: unrar
[ SUB2 ] DietPi-Services > stop
[  OK  ] DietPi-Services | stop : cron
[  OK  ] DietPi-Services | stop : docker
[  OK  ] DietPi-Services | stop : syncthing
[  OK  ] DietPi-Services | stop : radarr
[  OK  ] DietPi-Services | stop : medusa
[  OK  ] DietPi-Services | stop : emby-server
[  OK  ] DietPi-Services | stop : nzbget
[ SUB1 ] DietPi-Software > Installing Medusa: Automatic Video Library Manager for TV Shows
[ INFO ] DietPi-Software | APT install for: mediainfo python3, please wait...
[  OK  ] DietPi-Software | APT install for: mediainfo python3
[ INFO ] DietPi-Software | Medusa install dir "/mnt/dietpi_userdata/medusa" already exists. Download and install steps will be skipped.
 - If you want to update Medusa, please use the internal updater from WebUI.
 - If you need to reinstall (e.g. broken instance), please manually backup your config files+data, remove the install dir and rerun "dietpi-software (re)install 116".
[ SUB2 ] DietPi-Services > stop
[  OK  ] DietPi-Services | stop : cron
[  OK  ] DietPi-Services | stop : docker
[  OK  ] DietPi-Services | stop : syncthing
[  OK  ] DietPi-Services | stop : radarr
[  OK  ] DietPi-Services | stop : medusa
[  OK  ] DietPi-Services | stop : emby-server
[  OK  ] DietPi-Services | stop : nzbget
[ SUB1 ] DietPi-Software > Optimise and configure software
[ INFO ] DietPi-Software | Applying DietPi optimisations and configurations for PINE A64 (aarch64), please wait...

[ SUB1 ] DietPi-Software > Configuring Medusa: Automatic Video Library Manager for TV Shows
[  OK  ] DietPi-Software | Verifying user "medusa" to run Medusa
[  OK  ] DietPi-Software | usermod -g dietpi -d /mnt/dietpi_userdata/medusa -s /usr/sbin/nologin medusa
[  OK  ] DietPi-Software | cp /mnt/dietpi_userdata/medusa/runscripts/init.systemd /etc/systemd/system/medusa.service
[  OK  ] DietPi-Software | sed -i s/^[[:blank:]]Group=/#Group=/ /etc/systemd/system/medusa.service
[  OK  ] DietPi-Software | Setting in /etc/systemd/system/medusa.service adjusted: ExecStart=/usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py -q --nolaunch --datadir=/mnt/dietpi_userdata/medusa
[  OK  ] DietPi-Software | chown -R medusa:dietpi /mnt/dietpi_userdata/medusa
Removed /etc/systemd/system/multi-user.target.wants/dietpi-autostart_custom.service.
[  OK  ] DietPi-Autostart | systemctl enable dietpi-autostart_custom
[  OK  ] DietPi-Autostart | systemctl daemon-reload
[ SUB2 ] DietPi-Services > dietpi_controlled
[  OK  ] DietPi-Services | dietpi_controlled : nzbget
[  OK  ] DietPi-Services | dietpi_controlled : emby-server
[  OK  ] DietPi-Services | dietpi_controlled : medusa
[  OK  ] DietPi-Services | dietpi_controlled : radarr
[  OK  ] DietPi-Services | dietpi_controlled : syncthing
[  OK  ] DietPi-Services | dietpi_controlled : docker
[  OK  ] DietPi-Services | dietpi_controlled : cron
[  OK  ] DietPi-Survey | Purging survey data
[ SUB1 ] DietPi-Software > Installation completed
[ SUB2 ] DietPi-Services > restart
[  OK  ] DietPi-Services | restart : nzbget
[  OK  ] DietPi-Services | restart : emby-server
[  OK  ] DietPi-Services | restart : medusa
[  OK  ] DietPi-Services | restart : radarr
[  OK  ] DietPi-Services | restart : syncthing
[  OK  ] DietPi-Services | restart : docker
[  OK  ] DietPi-Services | restart : cron




dietpi@DietPi:~$ sudo systemctl status medusa
● medusa.service - Medusa Daemon
   Loaded: loaded (/etc/systemd/system/medusa.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-10-19 22:53:29 BST; 6s ago
  Process: 3142 ExecStart=/usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py -q --nolaunch --datadir=/mnt/dietpi_userdata/medusa (code=exited, status=216/GROUP)
 Main PID: 3142 (code=exited, status=216/GROUP)
      CPU: 0

Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:53:29 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Start request repeated too quickly.
Oct 19 22:53:29 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.

the journal thingy looks the same, but just incase here it is:

 journalctl -u medusa.service
-- Logs begin at Mon 2020-10-19 22:03:15 BST, end at Mon 2020-10-19 22:54:03 BST. --
Oct 19 22:03:42 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:03:42 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:03:42 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:42 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:03:43 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Start request repeated too quickly.
Oct 19 22:03:43 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:03:43 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:48 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:48 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:48 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:48 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:09:49 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Start request repeated too quickly.
Oct 19 22:09:49 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:09:49 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:28 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:53:28 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:53:28 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:53:28 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:53:28 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: Started Medusa Daemon.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Main process exited, code=exited, status=216/GROUP
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:28 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Service hold-off time over, scheduling restart.
Oct 19 22:53:29 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Start request repeated too quickly.
Oct 19 22:53:29 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Unit entered failed state.
Oct 19 22:53:29 DietPi systemd[1]: medusa.service: Failed with result 'exit-code'.
7

pls try

G_CONFIG_INJECT 'Group=' 'Group=dietpi' /etc/systemd/system/medusa.service
systemctl daemon-reload
systemctl restart medusa.service
systemctl status medusa.service
8

without sudo

with sudo:

dietpi@DietPi:~$ sudo G_CONFIG_INJECT 'Group=' 'Group=dietpi' /etc/systemd/system/medusa.service
sudo: G_CONFIG_INJECT: command not found
dietpi@DietPi:~$ G_CONFIG_INJECT 'Group=' 'Group=dietpi' /etc/systemd/system/medusa.service




dietpi@DietPi:~$ sudo systemctl daemon-reload
dietpi@DietPi:~$ systemctl restart medusa.service
Failed to connect to bus: No such file or directory
dietpi@DietPi:~$ sudo systemctl restart medusa.service
dietpi@DietPi:~$ sudo systemctl status medusa.service
● medusa.service - Medusa Daemon
   Loaded: loaded (/etc/systemd/system/medusa.service; disabled; vendor preset:
enabled)
   Active: failed (Result: exit-code) since Mon 2020-10-19 23:08:13 B
ST; 14s ago
  Process: 3569 ExecStart=/usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py
-q --nolaunch --datadir=/mnt/dietpi_userdata/medusa (code=exited, status
=216/GROUP)
 Main PID: 3569 (code=exited, status=216/GROUP)
      CPU: 0

Oct 19 23:08:13 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.
Oct 19 23:08:13 DietPi systemd[1]: medusa.service: Service hold-off time over, s
cheduling restart.
Oct 19 23:08:13 DietPi systemd[1]: Stopped Medusa Daemon.
Oct 19 23:08:13 DietPi systemd[1]: medusa.service: Start request repeate
d too quickly.
Oct 19 23:08:13 DietPi systemd[1]: Failed to start Medusa Daemon.
Oct 19 23:08:13 DietPi systemd[1]: medusa.service: Unit entered failed s
tate.
Oct 19 23:08:13 DietPi systemd[1]: medusa.service: Failed with result 'e
xit-code'.

the LS of the folder mentioned in the error:

dietpi@DietPi:/etc/systemd$ ls
journald.conf  network        system       timesyncd.conf  user.conf
logind.conf    resolved.conf  system.conf  user

I dont know enough about linux to find the correct link to the file though


EDIT:
so the file is there, from what i can see

dietpi@DietPi:/etc/systemd/system$ ls
apt-daily.service                   getty-static.service
apt-daily.timer                     getty.target.wants
apt-daily-upgrade.service           halt.target.wants
apt-daily-upgrade.timer             local-fs.target.wants
armbian-firstrun-config.service     medusa.service
armbian-firstrun.service            multi-user.target.wants
armbian-hardware-monitor.service    network-online.target.wants
armbian-hardware-optimize.service   nzbget.service
armbian-ramlog.service              nzbget.service.d
armbian-resize-filesystem.service   poweroff.target.wants
armbian-zram-config.service         radarr.service
default.target.wants                reboot.target.wants
dietpi-autostart_custom.service     serial-getty@ttyS0.service
dietpi-boot.service                 serial-getty@ttyS1.service
dietpi-firstboot.service            serial-getty@ttyS2.service
dietpi-fs_partition_resize.service  serial-getty@tty.service
dietpi-kill_ssh.service             sockets.target.wants
dietpi-postboot.service             syncthing.service
dietpi-preboot.service              sysinit.target.wants
dietpi-ramlog.service               systemd-logind.service
dietpi-wifi-monitor.service
dietpi@DietPi:/etc/systemd/system$
9

ok I missed sudo as I’m doing all this as user root :wink:

pls can you post following

systemctl cat medusa.service
groups medusa
10

if i sudo nano into the file:

# Medusa systemd service unit file
#
# Configuration Notes
#
#    - Option names (e.g. ExecStart=, Type=) are case-sensitive)
#
#    - Adjust User= and Group= to the user/group you want Medusa to run as.
#
#    - Optional adjust EnvironmentFile= path to configuration file
#        Can ONLY be used for configuring extra options used in ExecStart.
#        Putting a minus (-) in front of file means no error warning if the file doesn't exist
#
#    - Adjust ExecStart= to point to your python and Medusa executables.
#       The FIRST token of the command line must be an ABSOLUTE FILE NAME,
#       then followed by arguments for the process.
#       If no --datadir is given, data is stored in same dir as start.py
#       Arguments can also be set in EnvironmentFile (except python)
#
#    - WantedBy= specifies which target (i.e. runlevel) to start Medusa for.
#        multi-user.target equates to runlevel 3 (multi-user text mode)
#        graphical.target  equates to runlevel 5 (multi-user X11 graphical mode)
#

### Example Using Medusa as daemon with pid file
# Type=forking
# PIDFile=/var/run/PyMedusa/Medusa.pid
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --daemon --nolaunch --pidfile=/var/run/PyMedusa/Medusa.pid --datadir=/opt/medusa

## Example Using Medusa as daemon without pid file
# Type=forking
# GuessMainPID=no
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --daemon --nolaunch --datadir=/opt/medusa

### Example Using simple
# Type=simple
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --nolaunch

### Example Using simple with EnvironmentFile where APP_DATA=/home/medusa/.medusa in /etc/medusa.conf
# Type=simple
# EnvironmentFile=/etc/medusa.conf
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --nolaunch --datadir=${APP_DATA}

### Configuration

[Unit]
Description=Medusa Daemon
After=network.target

[Service]
User=medusa
Group=medusa

Type=simple
ExecStart=/usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py -q --nolaunch --datadir=/mnt/dietpi_userdata/medusa
TimeoutStopSec=25
KillMode=process
Restart=on-failure


[Install]
WantedBy=multi-user.target

not sure if that helps?

11

the first command seems to do the same as loading it into nano:

dietpi@DietPi:/etc/systemd/system$ sudo systemctl cat medusa.service
# /etc/systemd/system/medusa.service
# Medusa systemd service unit file
#
# Configuration Notes
#
#    - Option names (e.g. ExecStart=, Type=) are case-sensitive)
#
#    - Adjust User= and Group= to the user/group you want Medusa to run as.
#
#    - Optional adjust EnvironmentFile= path to configuration file
#        Can ONLY be used for configuring extra options used in ExecStart.
#        Putting a minus (-) in front of file means no error warning if the file doesn't exist
#
#    - Adjust ExecStart= to point to your python and Medusa executables.
#       The FIRST token of the command line must be an ABSOLUTE FILE NAME,
#       then followed by arguments for the process.
#       If no --datadir is given, data is stored in same dir as start.py
#       Arguments can also be set in EnvironmentFile (except python)
#
#    - WantedBy= specifies which target (i.e. runlevel) to start Medusa for.
#        multi-user.target equates to runlevel 3 (multi-user text mode)
#        graphical.target  equates to runlevel 5 (multi-user X11 graphical mode)
#

### Example Using Medusa as daemon with pid file
# Type=forking
# PIDFile=/var/run/PyMedusa/Medusa.pid
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --daemon --nolaunch --pidfile=/var/run/PyMedusa/Medusa.pid --datadir=/opt/medusa

## Example Using Medusa as daemon without pid file
# Type=forking
# GuessMainPID=no
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --daemon --nolaunch --datadir=/opt/medusa

### Example Using simple
# Type=simple
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --nolaunch

### Example Using simple with EnvironmentFile where APP_DATA=/home/medusa/.medusa in /etc/medusa.conf
# Type=simple
# EnvironmentFile=/etc/medusa.conf
# ExecStart=/usr/bin/python3 /opt/medusa/start.py -q --nolaunch --datadir=${APP_DATA}

### Configuration

[Unit]
Description=Medusa Daemon
After=network.target

[Service]
User=medusa
Group=medusa

Type=simple
ExecStart=/usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py -q --nolaunch --datadir=/mnt/dietpi_userdata/medusa
TimeoutStopSec=25
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target
dietpi@DietPi:/etc/systemd/system$

second command:

dietpi@DietPi:/etc/systemd/system$ sudo groups medusa
medusa : dietpi

Side note: The help getting this sorted is appreciated

12

ok somehow the user group did not changed

[Service]
User=medusa
Group=medusa

it should be

[Service]
User=medusa
Group=dietpi

pls try again to do this as user root

G_CONFIG_INJECT 'Group=' 'Group=dietpi' /etc/systemd/system/medusa.service

output should looks like this

root@DietPi3:~# G_CONFIG_INJECT 'Group=' 'Group=dietpi' /etc/systemd/system/medusa.service
[  OK  ] G_CONFIG_INJECT | Setting in /etc/systemd/system/medusa.service adjusted: Group=dietpi
root@DietPi3:~#
13

I always thought sudo was to do a command as the root user, after reading your reply I found out thats not really the case…
A quick bit of googling and i learnt how to log in as root user.

now the config_inject thing worked and i can load medusa! yay…thank you!

root@DietPi:/etc/systemd/system# G_CONFIG_INJECT 'Group=' 'Group=dietpi' /etc/systemd/system/medusa.service
[  OK  ] G_CONFIG_INJECT | Setting in /etc/systemd/system/medusa.service adjusted: Group=dietpi
root@DietPi:/etc/systemd/system# systemctl daemon-reload
root@DietPi:/etc/systemd/system# systemctl restart medusa.service
root@DietPi:/etc/systemd/system# systemctl status medusa.service
● medusa.service - Medusa Daemon
   Loaded: loaded (/etc/systemd/system/medusa.service; disabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-10-19 23:40:17 BST; 15s ago
 Main PID: 4167 (python3)
    Tasks: 2 (limit: 4915)
   Memory: 103.0M
      CPU: 11.537s
   CGroup: /system.slice/medusa.service
           ├─4167 /usr/bin/python3 /mnt/dietpi_userdata/medusa/start.py -q --nolaunch --datadir=/mnt/dietpi_userdata/medusa
           └─4176 ffprobe -version

Oct 19 23:40:17 DietPi systemd[1]: Started Medusa Daemon.
14

on DietPi, login as user root is quite simple as it is not locked and usually it’s using same password a user dietpi (if not changed) :wink:

15

typed su and it asked for my password and all things worked lol Not exactly linux adapt (comfortable enough to know nano but thats about as far as i get, will use su from now on)

16

you could simply login as user root via SSH directly.