-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Radarr] Won't start on DS715 after upgrade to version 20210311-15 #4546
Comments
Hi Thanks for the detailed logs and report. Your radarr.log is very short Can you run the radarr manually using following command and tell me what the output is? sudo su -s /bin/sh sc-radarr -c "env HOME=/volume1/@appstore/radarr/var LD_LIBRARY_PATH=/volume1/@appstore/radarr/lib /volume1/@appstore/radarr/share/Radarr/bin/Radarr" If you get Thanks |
Didn't had time yet, will test and provide information tomorrow |
I'm seeing the exact same behavior as the OP on a DS1817. Log entries look the same as well, specifically the Executing the command suggested above outputs a single word
|
Thanks @aderusha Can you run the command again and copy the last few lines from the Edit: You can also test if it is resource exhaustion by stopping all packages and restarting the NAS and only starting Radarr. |
Radarr should need max 200mb to start. Normally it idles around 150 or so for me. That CPU has neon so should be supported afaik. |
Did not had time to update (sorry) but here is at least the cpu info.
|
That CPU ought to be supported I think. The package might need fixing, but it should be fixable I think. |
I ran edit: Hitting "RUN" in the UI results in the following
|
@publicarray
Also for dmesg output
|
Thanks, So it's not your RAM. Honestly I was hoping to get more out of the logs. |
Sure. Can you swing by the radarr discord channel when you have some free time to dig into it? https://radarr.video/discord |
I have a DS918+. Since the last update of Radarr it wont start on boot. Though in my case if i manually start it then it works. |
Can't seem to join Discord, issue is still present. |
I seem to have the same issue and very similar logs. |
Hi and sorry for the silence, to learn more we would need a dump file. Can someone share theirs and share it in dotnet/runtime#56706? |
@publicarray i got no log there. |
How do we generate this dump? |
Thanks @farfromrefug Here is the process I used to get a dump from a running process: publicarray#28 (comment): I installed the .NET SDK https://github.com/publicarray/spksrc/releases/tag/dotnet-fix @mangod9 how do you get a memory dump from a process that crashes at launch though? |
@publicarray I don't understand what you mean with armadaxp being unsupported and/or marking it as unsupported. I'm running a recent Radarr dotnet core on my DS414 without any issues. Radarr Details:
|
* Add Prowlarr * Remove legacy config from service setup * Fix uninstall wizard (remove hidden files as well) * Fix rm: refusing to remove '.' or '..' directory: skipping * service_clean_tmpdir: use find for removing files and log rm files * armadaxp and alpine may or may not work #4546 (comment) * Add cross/libstdc++ to fix some ARM architectures Co-authored-by: Sebastian Schmidt <publicarray@users.noreply.github.com>
@schumi2004 @AnonTester @aderusha, I've been trying to solicit feedback to confirm compatibility with .NET builds of Radarr, Lidarr and Sonarr v4 running on ARMv7 architectures. If you have the time perhaps you can check out #5574 and add your feedback on the test packages I've shared. Appreciate the support. |
@schumi2004, a new version of Radarr (v20230215-19) has been published. This version includes Radarr 4.3.2.6857 and removes support for In your original note you mentioned your setup was:
Based on this setup Radarr will not be compatible unless you upgrade to DSM 7.1. If this is not an option you can consider running one of the Servarr builds from https://github.com/Servarr/spksrc/releases which include a special wrapper for running dotnet apps on older architectures. |
@schumi2004, I wanted to follow up on your issue. Have you had a chance to try my suggested solution? Please let me know if it resolves the issue. If I don't hear back from you in the next few days, I'll assume the issue has been resolved and will close it. |
@mreid-tt I completely missed your previous message. /Edit |
hey @schumi2004, thanks much for the update. This is indeed strange. If you can, I'd like you to SSH into your NAS and share with me the results of:
I noted above you already shared your cpu info (#4546 (comment)) so I won't need that again. I may have to update the results of my original testing based on the results. EDIT: I have another issue with a similar processor (#5302) and you may be experiencing the same issue. Looking forward to the SSH output above to confirm. |
It seems that AnnapurnaLabs Alpine CPUs are not compatible with dotnet 6.0. They have been excluded from future builds of Radarr and other packages which use dotnet 6.0. |
Setup
Package Name: Radarr
Package Version: 20210311-15
NAS Model: DS715
NAS Architecture: Alpine
DSM version: 6.2.4-25556
Package Name: Mono
Package Version: 5.20.1.34-17
Expected behavior
The package should start normally from Package Center
Actual behavior
After clicking 'Run' in Package Center a windows pops up with the message 'Failed to run package service'.
Steps to reproduce
1. Installed the given update, but also a clean installation causes this behavior. v20210311-15
2. Removing and manual installing version v20201214-13 makes it work again, upgrading then brakes it.
Package log
_find logfiles in
/var/packages/{package}/var/
, for DSM7:/var/log/packages/{package}.log
, for DSM < 6.0: protocol in Package Center._
Other logs
/var/log/messages`_
/var/log/synopkg.log`_
The text was updated successfully, but these errors were encountered: