Radarr web interface constantly crashing

Troubleshooting
21

After a reboot, no more red text in the journalctl logs, this is what I’m getting

Aug 02 15:12:03 DomDietPi systemd[1]: Started Radarr (DietPi).
Aug 02 15:12:04 DomDietPi Radarr[592]: Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1
Aug 02 15:12:04 DomDietPi systemd[1]: radarr.service: Main process exited, code=exited, status=135/n/a
Aug 02 15:12:04 DomDietPi systemd[1]: radarr.service: Failed with result 'exit-code'.
Aug 02 15:12:04 DomDietPi systemd[1]: radarr.service: Service RestartSec=100ms expired, scheduling restart.
Aug 02 15:12:04 DomDietPi systemd[1]: radarr.service: Scheduled restart job, restart counter is at 1.
Aug 02 15:12:04 DomDietPi systemd[1]: Stopped Radarr (DietPi).
Aug 02 15:12:04 DomDietPi systemd[1]: Started Radarr (DietPi).
Aug 02 15:12:04 DomDietPi Radarr[636]: Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1
22

hmm that seems something related to .NET

@MichaIng
any ideas?

23

As the permissions already changed, possibly other changes happened as well. Better do reinstall Radarr before trying to debug this:

dietpi-software reinstall 145
24

After a reinstall of radarr and reboot of dietpi, got the same error

Aug 04 09:20:49 DomDietPi systemd[1]: Started Radarr (DietPi).
Aug 04 09:20:49 DomDietPi Radarr[592]: Could not resolve CoreCLR path. For more
details, enable tracing by setting COREHOST_TRACE environment variable to 1
Aug 04 09:20:49 DomDietPi systemd[1]: radarr.service: Ma
in process exited, code=exited, status=135/n/a
Aug 04 09:20:49 DomDietPi systemd[1]: radarr.service: Fa
iled with result 'exit-code'.
Aug 04 09:20:50 DomDietPi systemd[1]: radarr.service: Service RestartSec=100ms e
xpired, scheduling restart.
Aug 04 09:20:50 DomDietPi systemd[1]: radarr.service: Scheduled restart job, res
tart counter is at 1.
Aug 04 09:20:50 DomDietPi systemd[1]: Stopped Radarr (DietPi).
Aug 04 09:20:50 DomDietPi systemd[1]: Started Radarr (DietPi).
Aug 04 09:20:50 DomDietPi Radarr[636]: Could not resolve CoreCLR path. For more
details, enable tracing by setting COREHOST_TRACE environment variable to 1
25

Just wondering if you had any thoughts on this, thanks again for all the help! @Joulinar @MichaIng

26

Ah sorry I missed that Radarr is not really replaced on a reinstall, since it has an internal updater. Please try the following to force a fresh install:

mv /opt/radarr{,_old}
dietpi-software reinstall 145

If this works well, you can remove the old dir afterwards:

rm -R /opt/radarr_old
27

That seems to have fixed it!!

All working for now, will update if I have any further issues

Love your work

1 Like