Sonarr version (exact version): 4, attempted upgrade to latest
Mono version (if Sonarr is not running on Windows): not known
OS: Raspberry Pi OS / Debian 12.11
Debug logs: temp-debug.txt · GitHub
Description of issue:
Attemted to update Sonarr via the web interface. This was the first time I did that on this installation. Sonarr is installed in /opt/Sonarr on a Raspberry PI 5. This is what systemctl has to say:
root@pi5:/opt/Sonarr# systemctl status sonarr
× sonarr.service - Sonarr Daemon
Loaded: loaded (/etc/systemd/system/sonarr.service; enabled; preset: enabled)
Active: failed (Result: signal) since Sat 2025-05-31 13:45:21 UTC; 18min ago
Duration: 85ms
Process: 3305 ExecStart=/opt/Sonarr/Sonarr -nobrowser -data=/var/lib/sonarr/ (code=killed, signal=ABRT)
Main PID: 3305 (code=killed, signal=ABRT)
CPU: 50ms
May 31 13:45:21 pi5 systemd[1]: sonarr.service: Scheduled restart job, restart counter is at 5.
May 31 13:45:21 pi5 systemd[1]: Stopped sonarr.service - Sonarr Daemon.
May 31 13:45:21 pi5 systemd[1]: sonarr.service: Start request repeated too quickly.
May 31 13:45:21 pi5 systemd[1]: sonarr.service: Failed with result 'signal'.
May 31 13:45:21 pi5 systemd[1]: Failed to start sonarr.service - Sonarr Daemon.
How can I recover from this without loosing data?