Small issue with dietpi-services

Hi, I’ve been migrating some services to give docker a go, so one of the services I migrated was radarr.
What I did was go into dietpi-services and deactivate the running radarr service, then deploy the docker instance and after checking everything was alright with the docker instance I proceeded to uninstall radarr through the dietpi-software.
It removed it just fine.

The service is removed alright:

dietpi@Pi:~$ sudo systemctl disable radarr
Failed to disable unit: Unit file radarr.service does not exist.

But the service is still listed on in dietpi-services, and of course shows as inactive.

Not a big deal, but just wanted to report it and ask if there is a way to fix that.

Maybe you could try to purge radarr before installing it in docker?

AFAIK the dietpi-software uninstall takes care of that, I mean it removes and purges radarr (or any other software that is being uninstalled). Or do you mean that I should try to manually purge it again?

Anyway it’s just a cosmetic issue, that it still shows in dietpi-services as available. radarr is in fact uninstalled and the newly installed docker instance is working fine.

It should purge it. What I am suggesting is to purge it without first disabling it or installing the docker version. After it is uninstalled and without any leftovers install the docker version.

Makes sense to uninstall the non-docker version first. But it’s strange that it’s listed by dietpi-services while systemctl says it does not exist. Can you show the result of the following commands:

systemctl cat radarr
ls -l /{{etc,usr/local/lib,lib,usr/lib}/systemd/system,run/systemd/generator.late}/radarr.service

Sure thing:

sudo systemctl cat radarr
No files found for radarr.service.

sudo ls -l /{{etc,usr/local/lib,lib,usr/lib}/systemd/system,run/systemd/generator.late}/radarr.service
ls: no se puede acceder a '/etc/systemd/system/radarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/usr/local/lib/systemd/system/radarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/lib/systemd/system/radarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/usr/lib/systemd/system/radarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/run/systemd/generator.late/radarr.service': No existe el fichero o el directorio

It is localized in spanish, but basically says can’t access … the file or directory doesn’t exist.

Strange, then there is no way that dietpi-services would list it. Can you check again:

dietpi-services status

Ah the only other idea, probably it’s present in the include/exclude filter file?

cat /boot/dietpi/.dietpi-services_include_exclude

Of course:

sudo dietpi-services status

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: status

[  OK  ] DietPi-Services | nfs-kernel-server    active (exited) since Fri 2021-04-02 14:12:22 CEST; 24h ago
[  OK  ] DietPi-Services | syncthing            active (running) since Fri 2021-04-02 23:52:57 CEST; 14h ago
[  OK  ] DietPi-Services | noip2                active (running) since Fri 2021-04-02 14:12:33 CEST; 24h ago
[  OK  ] DietPi-Services | docker               active (running) since Fri 2021-04-02 14:12:33 CEST; 24h ago
[  OK  ] DietPi-Services | cron                 active (running) since Fri 2021-04-02 14:12:33 CEST; 24h ago
[  OK  ] DietPi-Services | ssh                  active (running) since Fri 2021-04-02 14:12:20 CEST; 24h ago
[  OK  ] DietPi-Services | dietpi-ramlog        active (exited) since Fri 2021-04-02 14:11:45 CEST; 24h ago
[  OK  ] DietPi-Services | dietpi-preboot       active (exited) since Fri 2021-04-02 14:11:45 CEST; 24h ago
[  OK  ] DietPi-Services | dietpi-boot          active (exited) since Fri 2021-04-02 14:12:20 CEST; 24h ago
[  OK  ] DietPi-Services | dietpi-postboot      active (exited) since Fri 2021-04-02 14:12:20 CEST; 24h ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor  inactive (dead)
[  OK  ] DietPi-Services | dietpi-arr_to_RAM    active (exited) since Fri 2021-04-02 14:11:44 CEST; 24h ago

It’s not listed here, as you probably expected, but then this…

But that is Sonarr, not Radarr. I guess it’s present but excluded. Check the same way:

ls -l /{{etc,usr/local/lib,lib,usr/lib}/systemd/system,run/systemd/generator.late}/sonarr.service
grep sonarr /boot/dietpi/.dietpi-services_include_exclude

Excuse me… I’m idiot. :roll_eyes:

sudo ls -l /{{etc,usr/local/lib,lib,usr/lib}/systemd/system,run/systemd/generator.late}/sonarr.service
ls: no se puede acceder a '/etc/systemd/system/sonarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/usr/local/lib/systemd/system/sonarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/usr/lib/systemd/system/sonarr.service': No existe el fichero o el directorio
ls: no se puede acceder a '/run/systemd/generator.late/sonarr.service': No existe el fichero o el directorio
-rw-r--r-- 1 root root 527 mar 28 01:27 /lib/systemd/system/sonarr.service



sudo grep sonarr /boot/dietpi/.dietpi-services_include_exclude- sonarr

No result

So I guess that for some reason it wasn’t properly uninstalled/purged from /lib/systemd/system/sonarr.service. Removing the file solves the issue.

Thanks a lot!

Your grep sonarr /boot/dietpi/.dietpi-services_include_exclude shows the Sonarr exclusion. You can remove the now obsolete - sonarr line it contains.

/lib/systemd/system/sonarr.service is strange indeed, as dietpi-software creates /etc/systemd/system/sonarr.service.

But I see the Sonarr v3 package contains this service file natively, so I guess you installed Sonarr v3 manually once? And probably it’s still installed: apt purge sonarr

Hi, yes you were right and as i said removing the file removes the issue.

Yeah, something like that, sonarr updated itself to v3.0 from the previous dietpi version and that might have triggered the issue.

Thanks once again.

sonarr updated itself to v3.0 from the previous dietpi version

Oh, does it? Would be new to me. Were all settings migrated successfully? We’ll migrate to Sonarr v3 with next release as well, but I’m a bit concerned to force it when users need to re-configure vast parts of their Sonarr. If this is however done automatically anyway, no need to worry.

I guess it does, if you check the box to do automatic updates, and about how it went I should say it was flawless, besides this one little thing so good I didn’t even remembered about it happening.

Lol, if it has an internal updater, the package version looses it’s meaning, respectively a package reinstall/upgrade could even downgrade Sonarr. However, good to know about this, when doing tests and implementing the v2 => v3 migration.

For me radarr updated itself to v3. Sonarr on the contrary didn’t and I had to do it manually. I suppose it had to do with the lack of package for the architecture of rockpi.