Joulinar
commented
1 year ago pls reboot your system and share following afterwards
journalctl -u readarr.serviceClosed Gabba35 closed 1 year ago
Joulinar
commented
1 year ago pls reboot your system and share following afterwards
journalctl -u readarr.service
Gabba35
commented
1 year ago Thanks for reaching our Joulinar!
root@DietPi:~# journalctl -u readarr.service
Journal file /var/log/journal/365bf3506715487e91db1ed3418110c5/system.journal is truncated, ignoring file.
-- Journal begins at Mon 2023-03-20 18:35:40 AEDT, ends at Mon 2023-03-20 18:38:22 AEDT. --
Mar 20 18:35:52 DietPi systemd[1]: Started Readarr (DietPi).
Mar 20 18:35:52 DietPi systemd[713]: readarr.service: Failed to execute /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:52 DietPi systemd[713]: readarr.service: Failed at step EXEC spawning /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:52 DietPi systemd[1]: readarr.service: Main process exited, code=exited, status=203/EXEC
Mar 20 18:35:52 DietPi systemd[1]: readarr.service: Failed with result 'exit-code'.
Mar 20 18:35:52 DietPi systemd[1]: readarr.service: Scheduled restart job, restart counter is at 1.
Mar 20 18:35:52 DietPi systemd[1]: Stopped Readarr (DietPi).
Mar 20 18:35:52 DietPi systemd[1]: Started Readarr (DietPi).
Mar 20 18:35:53 DietPi systemd[724]: readarr.service: Failed to execute /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:53 DietPi systemd[724]: readarr.service: Failed at step EXEC spawning /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Main process exited, code=exited, status=203/EXEC
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Failed with result 'exit-code'.
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Scheduled restart job, restart counter is at 2.
Mar 20 18:35:53 DietPi systemd[1]: Stopped Readarr (DietPi).
Mar 20 18:35:53 DietPi systemd[1]: Started Readarr (DietPi).
Mar 20 18:35:53 DietPi systemd[730]: readarr.service: Failed to execute /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:53 DietPi systemd[730]: readarr.service: Failed at step EXEC spawning /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Main process exited, code=exited, status=203/EXEC
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Failed with result 'exit-code'.
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Scheduled restart job, restart counter is at 3.
Mar 20 18:35:53 DietPi systemd[1]: Stopped Readarr (DietPi).
Mar 20 18:35:53 DietPi systemd[1]: Started Readarr (DietPi).
Mar 20 18:35:53 DietPi systemd[731]: readarr.service: Failed to execute /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:53 DietPi systemd[731]: readarr.service: Failed at step EXEC spawning /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Main process exited, code=exited, status=203/EXEC
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Failed with result 'exit-code'.
Mar 20 18:35:53 DietPi systemd[1]: readarr.service: Scheduled restart job, restart counter is at 4.
Mar 20 18:35:53 DietPi systemd[1]: Stopped Readarr (DietPi).
Mar 20 18:35:53 DietPi systemd[1]: Started Readarr (DietPi).
Mar 20 18:35:54 DietPi systemd[733]: readarr.service: Failed to execute /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:54 DietPi systemd[733]: readarr.service: Failed at step EXEC spawning /opt/readarr/Readarr: No such file or directory
Mar 20 18:35:54 DietPi systemd[1]: readarr.service: Main process exited, code=exited, status=203/EXEC
Mar 20 18:35:54 DietPi systemd[1]: readarr.service: Failed with result 'exit-code'.
Mar 20 18:35:54 DietPi systemd[1]: readarr.service: Scheduled restart job, restart counter is at 5.
Mar 20 18:35:54 DietPi systemd[1]: Stopped Readarr (DietPi).
Mar 20 18:35:54 DietPi systemd[1]: readarr.service: Start request repeated too quickly.
Mar 20 18:35:54 DietPi systemd[1]: readarr.service: Failed with result 'exit-code'.
Mar 20 18:35:54 DietPi systemd[1]: Failed to start Readarr (DietPi).can you share following as well
systemctl cat readarr.service# /etc/systemd/system/readarr.service
[Unit]
Description=Readarr (DietPi)
Wants=network-online.target
After=network-online.target
[Service]
SyslogIdentifier=Readarr
User=readarr
UMask=002
LogsDirectory=readarr
ExecStart=/opt/readarr/Readarr -nobrowser -data=/mnt/dietpi_userdata/readarr
TimeoutStopSec=20
KillMode=process
Restart=on-failure
# Hardening
ProtectSystem=strict
ProtectHome=true
PrivateDevices=true
ProtectKernelTunables=true
ProtectControlGroups=true
ReadWritePaths=-/opt/readarr -/mnt -/media -/var/log/readarr -/tmp
[Install]
WantedBy=multi-user.targetok let's check if following folder are existing
ls -la /opt/readarr/
ls -la /var/log/readarrroot@DietPi:~# ls -la /opt/readarr/
ls -la /var/log/readarrfor me this all looks good. I guess trying to start it manually will work?
systemctl stop readarr.service
sudo -u readarr /opt/readarr/Readarr -nobrowser -data=/mnt/dietpi_userdata/readarrHmm, didn't seem to do the trick. This is the output:
systemctl stop readarr.service
sudo -u readarr /opt/readarr/Readarr -nobrowser -data=/mnt/dietpi_userdata/readarr
sudo: unable to execute /opt/readarr/Readarr: No such file or directorydid you already tried to reinstall? If not, you can do following:
systemctl stop readarr.service
rm -Rf /opt/readarr
dietpi-software reinstall 203Yeah, tried that before posting but no luck on it.
The repos:
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 https://download.mono-project.com/repo/debian raspbianbuster InRelease
Hit:3 https://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 https://apt.sonarr.tv/debian buster InReleaseReadarr.develop.0.1.4.1596.linux-core-arm64.tar.gz
No luck, still 'failed' as a service.
Joulinar
commented
1 year ago Repositories doesn't matter as Readarr is downlaod directly from GitHub. One last attend would be to remove Readarr, reboot and do a fresh install.
Gabba35
commented
1 year ago I now have no video signal after dieting shows one line of text on reboot (audio still works..). Something unhappy. It's a lot do a fresh install with everything configured at the moment, might have to give up on Readarr. Thanks for all of your help, it's much appreciated.
Joulinar
commented
1 year ago can you try to access the system using SSH?
On my test RPi4B Readarr is working without issues. I guess it's something on your dedicated system.
MichaIng
commented
1 year ago You have 64-bit kernel mode enabled on a Raspbian (ARMv6) userland. Please remove the arm_64bit setting from your /boot/config.txt, reboot and reinstall Readarr.
There is zero benefit to enable the 64-bit kernel mode if the whole OS is 32-bit. It just causes confusion among any installer which selects binaries based on uname -m output, expecting this to match the installed OS.
Gabba35
commented
1 year ago Had a look, no arm_64bit setting in my config.txt. I'm not sure how I'd changed it. I'm thinking I'll go a new install with a new SD card since it's been a while.
Joulinar
commented
1 year ago can you share your configuration file pls:
cat /boot/config.txtStrange, please also show again:
uname -m
dpkg --print-architecture
cat /etc/os-releaseI've done a fresh install. Readarr works. So the current errors are a different problem.
I don't get HDMI output if I have the GPU split at 512mb(384mb works) - it cuts out during the console boot text otherwise. This was happening before fresh install too - was there anything in the last update? It didn't happen before it. It boots into 4k for some reason, I've got the below in dietpi-config display resolution.
Hardware: RPi 4 Model B (aarch64)
Current resolution: vc4-fkms-v3d
Fresh install config.txt has arm_64bit 1 in it. Is it Kodi or another software causing this? Kodi still runs if I make it '#arm_64bit 1'. Running 'kodi --standalone' or 'startkodi' via console. It did give me an error about 64 vs arm7 or something though with '#arm_64bit 1'.
I get these errors when running Kodi.
error: XDG_RUNTIME_DIR not set in the environment.
context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second timeroot@DietPi:~# uname -m
dpkg --print-architecture
cat /etc/os-release
aarch64
arm64
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"Fresh install config.txt has arm_64bit 1 in it.
This if fully correct because you used the ARMv8 64bit image for the new installation. Therefore the flag has been set correctly 😉
MichaIng
commented
1 year ago I don't get HDMI output if I have the GPU split at 512mb(384mb works)
What for do you assign so much GPU memory? Note that modern RPi kernel, especially on RPi 4, does make use of the GPU memory very rarely. Most things have been moved to CMA and hence common system memory. You will not need more than the default in very most cases, up to 128 MiB if you have specific applications which make dedicated use of the GPU memory for decoding or encoding. Everything above that, is just wasted an weakens performance as less system RAM is available.
Uff I just see with Kodi we still suggest 256 MiB, but that should be actually lowered to 128 MiB or no raise at all. At least someone should verify that there are cases where raising the GPU memory above default has any positive effect on Kodi video playback performance.
Current resolution: vc4-fkms-v3d
Use full KMS driver vc4-kms-v3d unless you have a specific legacy video or camera application which requires legacy GPU driver parts.
MichaIng
commented
1 year ago Marking this as closed as the original issue has been solved. Feel free to reopen if required.
Readarr service fails to start. Sonarr running fine but was installed before upgrading to bullseye.
Appreciate any support on this, is Readarr not supported or has an issue with mono?
5.1.4(1)-release (arm-unknown-linux-gnueabihf)Linux DietPi 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/LinuxAdditional Information
Steps to reproduce
Expected behaviour
Should start when rebooting or loading using dietpi-services
Actual behaviour
Extra details