Mono 5.18 SSL store problems on aarch64 platforms #3666
Comments
|
@m4tt075 Hello. As you can see, I have just successfully uploaded and published Mono and related application package updates. |
|
I might not be looking in the correct place, but the latest I see is Mono 5.18.0.240-12. I have that version installed. |
|
@bjorn1981 Yes, that is the latest version we ship. I've just searched the net for reports of the same error. There is not a lot. I found some issues for ARM64 platforms with this, but no clear direction where it comes from. Some people blamed |
|
Sorry, accidentally closed and reopened... |
|
same issue here since mono update to 5.18.0.240-12 |
|
@silv3r23 You are on aarch64 as well, right? |
|
@kaso17 May I please ask you to look at the above? Can you make sense out of this or do you know where this is coming from? Any advice appreciated... |
|
I never had time or any aarch64 device to track this down further. I've never seen this on any other platform than aarch64. mono/mono#8648 indicates some problems with older acc versions. If you used a new toolchain for the mono 5.18 release you might want to try the previous one first. might be a gcc regression. if that doesn't make the source of the problem clear, I would build boringssl (used by mono for TLS) and use the included command line tools to try to reproduce this without mono to find out if it's a mono or boringssl bug. |
|
Many thanks, @kaso17. Good to know (though not good) that the issue is apparently known. I've just cross-checked,the toolchains: The one we've used to build 5.18 is the same that we used for 5.8 at the time. No change in that regard. Looking through the thread you have referenced and references therein, the problem really appears to be a bit random, i.e. occurring with some mono version but not with others. I'm considering to build a couple of aarch64 builds of different mono versions to see whether we can at least "bisect" to some extent. @bjorn1981 @silv3r23 What happens if you manually downgrade your mono installation to our previous 5.8 version? You can get it from here: |
|
I have the same issue. As stated in the stack trace above. I'm using a Synology DS418J. It looks like the only way to get things working again, would be a downgrade. I'll try the link above - but it's happening on the Synology DS418J. Unfortunately, it looks like you need to uninstall Radarr and Sonarr (The two apps that use Mono) before you can downgrade. Actually, downgrade is forbidden. You need to uninstall Mono, and then do the manual install. Edit: I'm unable to do this now, as when I try reinstalled Radarr (Had to uninstall to remove mono), it forces me to update to the latest mono version (after downgrading). |
|
@CraigInBrisbane Right. Unfortunately, some of the newer For My debugging capabilities are limited, but I'll see whether I can build other, newer |
m4tt075
changed the title
|
Thanks for looking into it. Downgrading was my first idea as well, but I did not have time to backup and downgrade Sonarr and Radarr. I can test new releases when available. |
|
The CPU architecture of my synology is rtd1296. Unfortunately I cannot downgrade, because I had to uninstall Sonarr and Radarr at first and dont have time to back it up too. |
|
Thanks @m4tt075 - I downgraded Sonarr and Radarr and Mono as suggested. Setting it up took 20mins so not an issue. All working fine again. Happy to test new versions once they come up. Thanks for the help and efforts. |
|
I have this issue too CPU is Realtek RTD1293 (DS-418j). :( Going to attempt manual downgrade. |
|
In addition, I have the same problem on DS413j (so armv5) with Jackett (see log below). |
|
I see the same issue on a DS118 as @bjorn1981 with Lights-Out:
while trying to get data via HttpClient. Version 5.8 was working without issues. |
|
I can also offer to test new releases when available. |
|
+1 to the list DS418. Only seems to be affecting Radarr for me. Haven't tried uninstalling and downgrading everything as yet, major pain.... |
|
OK, guys, first attempt to fix the issue: |
|
Still the same issue on my DS118,. |
|
+1 same |
|
What worked for me:
After some restarts and updating Radarr and Sonarr to the newest Version, everything works again without backup and restore. |
|
@Kilay your mono version seems to be be simply incomplete As far as jackett is concerned you might want to try the new ARM32/ARM64/AMD64 releases. They use .NETcore making mono obsolete. Many users also reported reduced memory usage compared to the mono version. But someone probably has to package it for Syno first. |
|
OK, thanks for testing and reporting. Second attempt, enforcing |
|
Version number is causing a problem, last fix was 5.18.1.0-12, so cant over right. Sorry to noobish to attempt to change version numbers. |
|
@CraigInBrisbane I don't know but wouldn't count on it. I'd either downgrade again or patch the |
Just bought a used DS212+ with '88f6282' arch. Same issues. I will try to see if downgrading helps. Was the solution (reduced mono dependency) already applied and republished? |
|
hi. i also have the DS212+, and Mono stopped working. I want to downgrade Mono and Jackett, but i really don't see any download link under https://synocommunity.com/package/mono what am i doing wrong? |
|
Hi, so before I jump in and downgrade everything on my NAS, Can someone specify which version are compatible? For Mono, Radarr, Sonarr and maybe Jackett. |
|
Hi all, I have a DS420j which is aarch64. I cannot find mono 5.8 anywhere and the Syno community only has 5.18 and newer and none of then work. Does anyone know where I can get my hands on 5.8? |
5.8.0 is available in the Syno Community here |
|
Reporting this is broken for DS1515+ and the avoton-x64 architecture. Downgrading to mono v5.8.0.108-11 and sonarr v20200409-16 has worked for me. |
Thanks @Dirkle, I have already looked there and unfortunately I cannot find a download link of 5.8 for my architecture aarch64 (although there are ones for mine in other versions). Are you aware if any of the others are compatible? |
|
@hmelville I have built mono 5.8 for aarch64. Please give feedback whether this is running so I can upload it to the SynoCommunity package respository. |
@hgy59. That has worked perfectly with Sonarr version 20200921-18. Thank you. |
|
As I have published version 5.8.0.108-11 for aarch64, I have removed the release in https://github.com/hgy59/spksrc/releases/tag/Mono_5.8 PS |
|
Looking for some more background here - we have a DS216j (88F6820) and a DS218 (RTD1296), both with Sonarr 3.0.6.1196 & Jackett v0.17.828, however the DS218 (RDT1296) throws POINT_IS_NOT_ON_CURVE errors with any version of Mono greater than 5.8.0.108 whereas the DS216j (88F6820) has no issues with 5.20.1.34. This is likely a naive question, but I'm keen to understand why compiling the Mono 5.20.1.34 source for the aarch64 architecture doesn't solve this issue ? Is it as simple as the aarch64 compiler being broken ? Thanks in advance for your replies. |
|
The aarch64 failure is caused by the too old gcc of the synology toolchains. And yes, it is that any available aarch64 compiler seems to be broken. |
|
I think this issue can be closed. If possible install the .net version of the package or downgrade mono to 5.8 (Sonarr does not provide a .net version yet.) https://github.com/SynoCommunity/spksrc/wiki/Radarr-Sonarr-Lidarr-Jackett |
* Fix DSM 7 compatibility * Exclude aarch64 on DSM 6.x (issue #3666)
- update mono - fix BTLS library for aarch64 built with gcc 4 (SynoCommunity#3666) - remove some features to keep the package as small as possible - remove aot, profiling and debugging - remove boehm gc - remove ikvm library - disable packages for ARMv5 by removing ARMv5 from UNSUPPORTED_ARCHS it is still possible to create such a package, but without a TLS library most use cases will not work - add a script to update mono ca certificates after installation
- update mono - fix BTLS library for aarch64 built with gcc 4 (SynoCommunity#3666) - remove some features to keep the package as small as possible - remove aot, profiling and debugging - remove boehm gc - remove ikvm library - disable packages for ARMv5 by removing ARMv5 from UNSUPPORTED_ARCHS it is still possible to create such a package, but without a TLS library most use cases will not work - add a script to update mono ca certificates after installation
* mono: update to v6.12.0.182 - update mono - fix BTLS library for aarch64 built with gcc 4 (#3666) - remove some features to keep the package as small as possible - remove boehm gc - remove ikvm library - add a script to update mono ca certificates after installation * fix build for ARMv5 - enforce build of BTLS library for ARMv5 archs - fixes mono/mono#11422 * fix ffmpeg dependency evaluation in prepare build
and others
For new Package Requests, see the guidelines
Setup
Package Name: Mono
Package Version: 5.18
NAS Model: DS118
NAS Architecture: ARM rtd1296
DSM version: 6.1
Expected behavior
https connection excepted
Actual behavior
any https connection is refused since updating Mono 5.8 -> 5.18, for example torrentapi or telegram. Happens in sonarr and radarr. Mono, Sonarr and Radarr are all latest version by SynoCommunity.
log error:
System.Net.WebException: Error: SecureChannelFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:0f000078:elliptic curve routines:OPENSSL_internal:POINT_IS_NOT_ON_CURVE
Running /var/packages/mono/target/bin/cert-sync /etc/ssl/certs/ca-certificates.crt did not help. Also noticed there is no /usr/share/.mono/ folder
Connecting torrentapi over http instead of https works.
The text was updated successfully, but these errors were encountered: