I’ve been running Dietpi and Sickrage for some time on a Raspberry Pi Zero W, works well aside from increasing issues with Sickrage.
So today I thought I’d make a new system with the now-recommended Medusa, and try that out.
I downloaded Dietpi 6.21.1 and installed it, configured it to use wifi, have a different hostname and use a static ip (also gateway, dns servers etc). All worked ok.
I then chose Medusa software from the dietpi-software menu, and installed it.
It didn’t choose or install other software that is needed, eg the recommended Transmission client, nor did it choose any web server for me. I think (may be wrong here) that choosing Sickrage from the dietpi-software menu would automatically select other required software like Transmission and a web server.
Anyway, the install appears to compelete ok, but after a reboot, it tries to start Medusa and fails.
What should I be doing/what else is needed to make Medusa work?
Medusa does not require a webserver nor did/does SickRage. Both bring their internal webserver, which can be seen by the custom port that you need to add in browser .
I just tested install here on Stretch VM and service starts up well + web interface opens on port 8081 well.
Since it’s a raw python script download it should run OS/arch independently, as long as python itself runs fine.
But before guessing around, could you paste output of:
Thanks for the reply, I was unsure what external programs were required, and just vaguely remembered being asked if I wanted to install recommended extras.
There were no obvious errors during the install, but on reboot, when it starts the dietpi services, transmission starts ok but it hangs for some time “starting Medusa” then eventually says it failed.
Here’s the output from the commands :
root@ricketychair:~# journalctl -u medusa
-- Logs begin at Tue 2019-02-12 11:58:18 GMT, end at Tue 2019-02-12 11:59:18 GMT. --
Feb 12 11:58:50 ricketychair systemd: Starting Medusa Daemon...
root@ricketychair:~# tail -20 /mnt/dietpi_userdata/medusa/Logs/application.log
tail: cannot open '/mnt/dietpi_userdata/medusa/Logs/application.log' for reading: No such file or directory
I’ve just checked, and /mnt/dietpi_userdata/medusa exists, with various medusa files in there, but no Logs directory exists there.
Okay thanks for testing and reporting back. So indeed while Medusa starts up great manually, it fails on boot. Perhaps some other boot scripts or steps interfering or something is missing when it attempts to start. Also that it “simply” times out after 90 seconds is somehow helpful.
What I don’t like is that your manual start also took 90 seconds exactly although not timing out. I guess this is the usual systemd time allowed on scheduled starts. Although it should be DietPi-Services controlled . Will check back to assure that.
On my VM it took just 3 seconds or such, but you are on RPi Zero, that should be noted .
Also I guess it will be faster the next startups when first-run setup/configs and such have been done already.
Finally it is perhaps only RPi Zero being too slow to start it in allowed amount of seconds. We could workaround this by doing first service start right within the install run.