_For new Package Requests, see the guidelines_
_Package Name: Mono
_Package Version: 5.18
_NAS Model: DS118
_NAS Architecture: ARM rtd1296
_DSM version: 6.1
https connection excepted
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.
```
@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 mono, some openssl.
EDIT: To complete my message: Please report this with the mono team as they might be able to debug this further. We'll have to see whether this is an issue that affects people more broadly or just ARM64 platforms. Sorry, but I'm afraid I'm not able to do more right now. As temporary workaround, I'd downgrade the mono package again, but please report the error first, to ensure you provide all information the mono people need.
Sorry, accidentally closed and reopened...
same issue here since mono update to 5.18.0.240-12
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
at /spksrc/spk/mono/work-aarch64-6.1/mono-5.18.0.240/external/boringssl/crypto/ec/ec.c:835
at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00038] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000a1] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000ff] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.StartOperation (System.Threading.CancellationToken cancellationToken) [0x0008b] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00252] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x00126] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x0021a] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00141] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebOperation.Run () [0x0009a] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.HttpWebRequest.GetResponse () [0x00016] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0012f] in <a1d4cd371e3f48118cccea718b1ace8d>:0
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0009d] in <a1d4cd371e3f48118cccea718b1ace8d>:0
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookieContainer) [0x0007e] in <a1d4cd371e3f48118cccea718b1ace8d>:0
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00008] in <a1d4cd371e3f48118cccea718b1ace8d>:0
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in <a1d4cd371e3f48118cccea718b1ace8d>:0
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00052] in <b938542dd9a14cfc824f9cd70d8df65b>:0
@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.
https://github.com/mono/mono/issues/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:
https://synocommunity.com/package/mono
Does it work then?
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 *arr packages require newer mono versions, so just reverting the mono update is no option either.
Anyways, I think we have sufficient evidence that the aarch64 version of mono is broken for now. @ymartin59 For that reason, I've deactiveted it (just aarch64) on our repository.
For aarch64 users (@CraigInBrisbane et. al.), who updated already, downgrading mono is the only workaround for now. That requires to downgrade Radarr, too. On https://synocommunity.com/packages you can click on each package and get access to older package versions, which you can manually download and install. Sorry for the hassle.
My debugging capabilities are limited, but I'll see whether I can build other, newer mono versions for aarch64 that do not exhibit this problem. I'll post them here so that you can try. I don't have an aarch64 test platform myself.
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.
Can someone tell me how to identify the correct build please?
The only "aarch64" build I see is the latest one at the tip of the page.
In addition, I have the same problem on DS413j (so armv5) with Jackett (see log below).
Just for information, I previously had another error that affect armv5 but was able to fix it by adding MONO_ENV_OPTIONS='-O=-aot,-float32' in service-setup.sh script (see issue and fix reported in mono repo : https://github.com/mono/mono/issues/12537#issuecomment-459362182)
03-27 13:23:29 Error Jackett.Common.IndexerException: Exception (yggtorrent): /volume1/@appstore/mono/lib/../lib/libmono-btls-shared.so ---> System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: SecureChannelFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> System.DllNotFoundException: /volume1/@appstore/mono/lib/../lib/libmono-btls-shared.so
at (wrapper managed-to-native) Mono.Btls.MonoBtlsSslCtx.mono_btls_ssl_ctx_new()
at Mono.Btls.MonoBtlsSslCtx..ctor () [0x00000] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Btls.MonoBtlsContext.InitializeConnection () [0x00000] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Btls.MonoBtlsContext.StartHandshake () [0x00000] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x0007e] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000ff] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.StartOperation (System.Threading.CancellationToken cancellationToken) [0x0008b] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00252] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x00126] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x0021a] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00141] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebOperation.Run () [0x0009a] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <30c1a991558c4064acefa7cee0fc6779>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Net.Http.HttpClientHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x0041d] in <d79bb9faee264b669b8825270136bfaa>:0
--- End of inner exception stack trace ---
at System.Net.Http.HttpClientHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00478] in <d79bb9faee264b669b8825270136bfaa>:0
at CloudFlareUtilities.ClearanceHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x0010c] in <532686a2771c4b3eb8f0bcce022e4e0b>:0
at System.Net.Http.HttpClient.SendAsyncWorker (System.Net.Http.HttpRequestMessage request, System.Net.Http.HttpCompletionOption completionOption, System.Threading.CancellationToken cancellationToken) [0x000ca] in <d79bb9faee264b669b8825270136bfaa>:0
at Jackett.Common.Utils.Clients.HttpWebClient.Run (Jackett.Common.Utils.Clients.WebRequest webRequest) [0x00456] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Utils.Clients.WebClient.GetString (Jackett.Common.Utils.Clients.WebRequest request) [0x0010b] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.BaseWebIndexer.RequestStringWithCookies (System.String url, System.String cookieOverride, System.String referer, System.Collections.Generic.Dictionary`2[TKey,TValue] headers) [0x000cb] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.CardigannIndexer.PerformQuery (Jackett.Common.Models.TorznabQuery query) [0x0085e] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery (Jackett.Common.Models.TorznabQuery query) [0x00091] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
--- End of inner exception stack trace ---
at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery (Jackett.Common.Models.TorznabQuery query) [0x000ee] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.BaseWebIndexer.ResultsForQuery (Jackett.Common.Models.TorznabQuery query) [0x0006b] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Services.IndexerManagerService.TestIndexer (System.String name) [0x000a3] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Server.Controllers.IndexerApiController.Test () [0x000e1] in <d9cb217c33fa4cc9a9b8489469fe5189>:0
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor+TaskOfIActionResultExecutor.Execute (Microsoft.AspNetCore.Mvc.Infrastructure.IActionResultTypeMapper mapper, Microsoft.Extensions.Internal.ObjectMethodExecutor executor, System.Object controller, System.Object[] arguments) [0x00071] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync () [0x00131] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync () [0x0009e] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ActionExecutedContext context) [0x0001b] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00382] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync () [0x0002f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter () [0x0009f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ResourceExecutedContext context) [0x0001b] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00840] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync () [0x0002f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync () [0x0012e] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke (Microsoft.AspNetCore.Http.HttpContext httpContext) [0x001cb] in <6092a16d93814eba828b517a2b132f80>:0
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke (Microsoft.AspNetCore.Http.HttpContext context) [0x00384] in <427697fe42b7459ba5302fb76d339d3b>:0
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke (Microsoft.AspNetCore.Http.HttpContext context) [0x0043e] in <f352e566abf6421e87eafbcf57a0b237>:0
at Jackett.Server.Middleware.CustomExceptionHandler.Invoke (Microsoft.AspNetCore.Http.HttpContext httpContext) [0x0008a] in <d9cb217c33fa4cc9a9b8489469fe5189>:0 Jackett.Common.IndexerException: Exception (yggtorrent): /volume1/@appstore/mono/lib/../lib/libmono-btls-shared.so ---> System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: SecureChannelFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> System.DllNotFoundException: /volume1/@appstore/mono/lib/../lib/libmono-btls-shared.so
at (wrapper managed-to-native) Mono.Btls.MonoBtlsSslCtx.mono_btls_ssl_ctx_new()
at Mono.Btls.MonoBtlsSslCtx..ctor () [0x00000] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Btls.MonoBtlsContext.InitializeConnection () [0x00000] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Btls.MonoBtlsContext.StartHandshake () [0x00000] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x0007e] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000ff] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.StartOperation (System.Threading.CancellationToken cancellationToken) [0x0008b] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Boolean runSynchronously, Mono.Net.Security.MonoSslAuthenticationOptions options, System.Threading.CancellationToken cancellationToken) [0x00252] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MonoTlsStream.CreateStream (System.Net.WebConnectionTunnel tunnel, System.Threading.CancellationToken cancellationToken) [0x00126] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ba] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x0021a] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00141] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebOperation.Run () [0x0009a] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <30c1a991558c4064acefa7cee0fc6779>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Net.Http.HttpClientHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x0041d] in <d79bb9faee264b669b8825270136bfaa>:0
--- End of inner exception stack trace ---
at System.Net.Http.HttpClientHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00478] in <d79bb9faee264b669b8825270136bfaa>:0
at CloudFlareUtilities.ClearanceHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x0010c] in <532686a2771c4b3eb8f0bcce022e4e0b>:0
at System.Net.Http.HttpClient.SendAsyncWorker (System.Net.Http.HttpRequestMessage request, System.Net.Http.HttpCompletionOption completionOption, System.Threading.CancellationToken cancellationToken) [0x000ca] in <d79bb9faee264b669b8825270136bfaa>:0
at Jackett.Common.Utils.Clients.HttpWebClient.Run (Jackett.Common.Utils.Clients.WebRequest webRequest) [0x00456] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Utils.Clients.WebClient.GetString (Jackett.Common.Utils.Clients.WebRequest request) [0x0010b] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.BaseWebIndexer.RequestStringWithCookies (System.String url, System.String cookieOverride, System.String referer, System.Collections.Generic.Dictionary`2[TKey,TValue] headers) [0x000cb] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.CardigannIndexer.PerformQuery (Jackett.Common.Models.TorznabQuery query) [0x0085e] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery (Jackett.Common.Models.TorznabQuery query) [0x00091] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
--- End of inner exception stack trace ---
at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery (Jackett.Common.Models.TorznabQuery query) [0x000ee] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Indexers.BaseWebIndexer.ResultsForQuery (Jackett.Common.Models.TorznabQuery query) [0x0006b] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Common.Services.IndexerManagerService.TestIndexer (System.String name) [0x000a3] in <3f4864bea7054cd2b7e83a28c06c8c3f>:0
at Jackett.Server.Controllers.IndexerApiController.Test () [0x000e1] in <d9cb217c33fa4cc9a9b8489469fe5189>:0
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor+TaskOfIActionResultExecutor.Execute (Microsoft.AspNetCore.Mvc.Infrastructure.IActionResultTypeMapper mapper, Microsoft.Extensions.Internal.ObjectMethodExecutor executor, System.Object controller, System.Object[] arguments) [0x00071] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync () [0x00131] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync () [0x0009e] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ActionExecutedContext context) [0x0001b] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00382] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync () [0x0002f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter () [0x0009f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Filters.ResourceExecutedContext context) [0x0001b] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next (Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+State& next, Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+Scope& scope, System.Object& state, System.Boolean& isCompleted) [0x00840] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync () [0x0002f] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync () [0x0012e] in <b4ef600f4a594fe2865a8f97f915fb9d>:0
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke (Microsoft.AspNetCore.Http.HttpContext httpContext) [0x001cb] in <6092a16d93814eba828b517a2b132f80>:0
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke (Microsoft.AspNetCore.Http.HttpContext context) [0x00384] in <427697fe42b7459ba5302fb76d339d3b>:0
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke (Microsoft.AspNetCore.Http.HttpContext context) [0x0043e] in <f352e566abf6421e87eafbcf57a0b237>:0
at Jackett.Server.Middleware.CustomExceptionHandler.Invoke (Microsoft.AspNetCore.Http.HttpContext httpContext) [0x0008a] in <d9cb217c33fa4cc9a9b8489469fe5189>:0
I see the same issue on a DS118 as @bjorn1981 with Lights-Out:
Error: SecureChannelFailure (Authentication failed, see inner exception.)
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:
(1) Upgrading mono to latest stable (5.18.1.0):
[Edit: Link removed, as it did not work]
Any change?
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
System.DllNotFoundException: /volume1/@appstore/mono/lib/../lib/libmono-btls-shared.so
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 msc C# compiler instead of Roslyn. Inspired by some links @kaso17 kindly provided, here another aarch64 test build:
https://github.com/m4tt075/spksrc/releases/tag/mono-vars-2b
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.
Hi m4tt075, I tried your latest test build at https://github.com/m4tt075/spksrc/releases/tag/mono-vars-2b, but I still get the same error message: Error: SecureChannelFailure (Authentication failed, see inner exception.)
If you need more data/logging, please let me know if I can support you with information.
--
System.Net.WebException: Error: SecureChannelFailure (Authentication failed, see inner exception.): 'https://api.nzbgeek.info/api?t=caps&apikey=(Removed:-))' ---> 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
at /spksrc/spk/mono/work-aarch64-6.1/mono-5.18.0.240/external/boringssl/crypto/ec/ec.c:835
at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00038] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000a1] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool)
at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00006] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000ff] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
at Mono.Net.Security.AsyncProtocolRequest.StartOperation (System.Threading.CancellationToken cancellationToken) [0x0008b] in <63552ca6ec3f4cb28de3f8c0aa59b164>:0
--- End of inner exception stack trace ---
@Kilay your mono version seems to be be simply incomplete
System.DllNotFoundException: /volume1/@appstore/mono/lib/../lib/libmono-btls-shared.soAs 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.
Thank you @kaso17, I will try to uninstall/install Mono v5.18.0.240-12 again and see if I still have the issue. If yes, I will revert to previous version.
Hope someone will work on a .NETcore Jackett package for Syno as I am not able to do it myself.
Same problem here, ds 211+88f628x
@Kilay @Komagain OK. I've pulled the ARM5 mono version from the repository as well. Right now, the only option is to downgrade mono again (see further above).
I'm actually not sure whether the aarch64 and the ARM5problems are related. Is there anybody here with either ARM platform (ARM5, ARM7 or ARM8), for whom the upgrades actually work?
For information, I'm currently setting up a new build system. I turned increasingly insane trying to debug mono on my old laptop. Hope to be more productive soon...
Thanks for the efforts. Very much appreciated.
I have installed the latest versions of Mono en Sonarr on my test Nas (DS116 with an ARM7 cpu) and it is running without any problems.
@CraigInBrisbane Thanks. I just hope it will eventually pay off...
@BenjV Thanks. So not all ARMs are broken. Good, so maybe the problems are fixable.
A new test build for aarch64 is available here:
https://github.com/m4tt075/spksrc/releases/tag/mono-vars-2c
And another one (disabling the boehm garbage collector in the cross build):
https://github.com/m4tt075/spksrc/releases/tag/mono-vars-2d
@m4tt075
I suggest you stop putting effort in this issue.
The Mono developers "resolved" this by stopping the support for ARM64 platform.
Mono is in my opinion "dead in the water" because Microsoft released ".net core" to the public domain and has bought Xamarin ( the Mono developers) so my money is on ".net core"
@BenjV Wow. I wasn't aware Mono was sold. Hmh, in light of that, you might be right. From what @kaso17 wrote, an alternative for Jackett already exists. I just don't know about Radarr, Sonarr and Lidarr. Do you (or anybody) know about non-mono-dependent versions? Having said that, from some reports above, it seems they can be "tricked" into working with our old mono 5.8 version. I have not yet had the time to look into the ARM5 issues, but those could well be related to the outdated toolchain.
@ymartin59 Not sure how familiar you are with mono and/or the issues here, but any perspectives / advice on this from your side?
I think the problem is in the ARM64 architecture and not in the ArmV7 architecture.
The armv7 is the 32 bits version and they should be compatible with eachother.
So I should suggest to just use the ArmV7 package for both.
@BenjV
I see it the other way around. Since Microsoft bought Xamarin, Mono development got a big push and the developers can now access and use Microsoft .Net code in Mono.
Your link above does only explain that gcc is broken.
Just my 2 cent
Martin
There is of course no .net code in mono.
.net is part of Windows and not multiplatform and Microsoft will for sure not put .net core in mono.
And nobody can see in the future, but Microsoft is heavealy pushing .net core and they have a track record on buying things and let it bleed out.
No luck with the 2d build
Op di 2 apr. 2019 16:26 schreef m4tt075 notifications@github.com:
And another one (disabling the boehm garbage collector in the cross build):
https://github.com/m4tt075/spksrc/releases/tag/mono-vars-2d
@BenjV wrote:
So I should suggest to just use the ArmV7 package for both.
Do you mean to tweak the spk file of the ARM7 package so that it runs on ARM64 platforms, too?
Correct, but it is possible that then also Sonarr (and Radarr) for the ArmV7 must be used, but that has to be tested by someone with this architecture.
There is no need for need for creating new packages.
One can download the armada38x .spk, unpack it and add the architecture by changing the INFO file and packing it back into a .spk
In the INFO file change the line:
arch="armada38x "
into
arch="armada38x rtd1296 armada37xx "
Has anybody tried @BenjV 's advice above? If you haven't, please do...
I haven’t.
So. Download the latest version of mono from somewhere. Right version?
(Need to find right version to download)
Unzip
Edit an INFO file as above.
Rezip and then rename .zip to .spk
Install update using the spk file.
Does that sound right?
yeah nah, turns out I have NFI how to repack a spk. If you can provide the spk I will give it a whirl
Download the package from:
https://synocommunity.com/package/mono
(Choose 6.1 armada38x)
An .spk is not a zipfile but a tar so you need a program that can handle that .
Best to us 7zip.
Edit the INFO file as I already explained.
Best to do this with Notepad++ because the file has Unix style line-endings (LF) and not windows style line-endings(CRLF)
Pack the changed files into a new .spk and do a manual install on your Nas.
I followed instructions.
During manual install, I get “The package file is corrupt. .... Are you sure you want to continue”.
Note that I used Notepad++.
Is that expected? Maybe some checksum is wrong now due to the edit?
Same, except 'invalid file format'
Yes checksum is wrong.
Remove the checksum from the INFO file (last line) to get around this.
Removed checksum. Same issue. NAS manual install reports corrupt file.
In that case you did not create a tar file with 7zip.
If you add the files to a filename with extension .spk then you have to select tar as archive format in 7zip.
I opened the file with 7zip. Extracted the INfO file my desktop. Edited the INFO file with Notepad++. Copied the INFO back into the spk file (open in 7zip).
So I never created a spk file. I simply edited a file within the existing one.
I unpacked it all, edited the INFO and repacked as a tar, still no go
If you save it then it will be save as a zip (the default)
Better to open 7zip.
Select all the files including the changed INFO.
Click ADD in 7zip
Choose a new filename with extension .spk (for example: mono test.spk)
Select on that page tar as the archive format.
Click OK
Do a manual install of "mono test.spk" on your Nas
Just did that exactly as you said.
Same issue.
What NAS model do you have?
I have a Synology DS418j
The Synology DS418j arrives with an ARM CPU, but this time a much more proficient Realtek RTD1293. This chip is a 64-bit architecture, dual core CPU that has a higher frequency of 1.4GHz and with it you have a host of new application options open to you compared with the DS416J.
DS418 here
Ok I made a package for you guys
Downloadlink is here.
https://drive.google.com/file/d/1JFOV11HWikcfJjJyZ9fs4SB3FElEK2TO/view?usp=sharing
I installed it on my DS116 and it works fine.
So if it does not install on a DS418 the packages are not comapitble
Ok. Downloading.
Darn. Same issue with your file. Something is irritating the file. It still reports corrupt.
I have something different, mono is up and running but radar and sonar won’t start. Just restarting the NAS
Ok Mono is running but still can’t start radarr or sonarr, might be something my end though
Nope, no go. Mono says it’s running, but sonar and radar won’t start. Don’t think it’s a permission issue
Thanks for your help BenjV, unfortunately same issue as carnigg...
As I said before, you most likely have to do the same thing for Radarr and Sonarr and use the packages build voor the ARMV7.
I don't have time to change those package at this moment, but later on I will post them for you to test with.
I have made test packages for Sonarr and Radarr that may work in conjunction with the mono test package.
Here are the links to download them:
Sonarr:
https://drive.google.com/file/d/1GXWaAbHydKJ2Pipr3tXs5TkucKgYV2sQ/view?usp=sharing
Radarr
https://drive.google.com/file/d/1qtUkuGgSR_15I0AKYvoLszuOuUOwi2z1/view?usp=sharing
Thanks unfortunately same problem still, not starting Radarr and Sonarr...
Sorry to hear that, but it was always a bit of a longshot.
Thanks in any case for helping.
Yes. Thanks from me too. I guess we need to wait and hope that someone changes Radarr and Sonarr to .Net Core?
Yes, thanks for helping, @BenjV! It was worth a try.
On possible solutions: From the mono discussions, this is an issue with gcc 4.x versions really. Their "workaround" was to upgrade to newer gcc versions. Our problem is that all the Synology toolchains that we use to cross-compile still come with gcc 4.x (see subdirectories of https://sourceforge.net/projects/dsgpl/files/DSM%206.2%20Tool%20Chains/). If they upgrade, that could solve the issue, too.
In any case, I hope the "downgrade" workaround will still keep aarch64 platform users running for a while...
Maybe you could update the toolchain with a newer gcc version.
You can download the binaries for the arch64 cpu here.
https://rpmfind.net/linux/rpm2html/search.php?query=gcc-aarch64-linux-gnu
What worked for me:
- Download mono Version 5.8.0.108-11 from https://synocommunity.com/package/mono
- Unpack Package
- Change Version to higher version than 5.18.0.240-12
- Repack Package
- Install Package manually
- Restart Diskstation
After some restarts and updating Radarr and Sonarr to the newest Version, everything works again without backup and restore.
I also followed this method. In the INFO file I changed the version to 5.18.0.240-13 and deleted the checksum (with notepad++. Packed the files as a tar archive wth 7-zip. No need te reboot the diskstation, Sonarr and Radarr were already updated to the latest.
So now you are running the latest version of Sonarr and Radar with the old (5.8.0.108-11) mono version (disguised as version 5.18.0..240).
Don't you think that there is a reason why the Sonarr/Radarr developers want you to use the newer version?
Probably. I'll just see where it goes. Today everything was fully
operational. No errors in log files. If anything breaks I'll know I'm to
blame.
Op do 11 apr. 2019 14:10 schreef BenjV notifications@github.com:
So now you are running the latest version of Sonarr and Radar with the old
(5.8.0.108-11) mono version (disguised as version 5.18.0..240).Don't you think that there is a reason why the Sonarr/Radarr developers
want you to use the newer version?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SynoCommunity/spksrc/issues/3666#issuecomment-482088317,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIDlWll7X9OBDtTGLjwDGccegkR_6dWnks5vfyYmgaJpZM4cG5YZ
.
If you save it then it will be save as a zip (the default)
Better to open 7zip.
Select all the files including the changed INFO.
Click ADD in 7zip
Choose a new filename with extension .spk (for example: mono test.spk)
Select on that page tar as the archive format.
Click OK
Do a manual install of "mono test.spk" on your Nas
Just to clarify, the files have to be tar and not the directory (I have faced errors since last week because of that)
Is this the only "work around" at the moment? I might need to give it a go. From what I see, Sonarr/Radarr to .Net Core port is a long long way off.
PS: Still getting "Package is corrupt" issue though. :(
I was searching on the web which mono version is required by Sonarr/Radarr but that information is nowhere to be found.
@bjorn1981 and @Komagain could maybe report back if your solution is working without problems.
If so then the packages for Sonarr and Radarr could be changed so they accept to be installed when the older mono version is installed.
@BenjV
I confirm it works like a charm, I had to reboot 3 times:
@m4tt075 and @ymartin59
Is it a good idea to change the packages that use mono so that they also would accept a lower version of mono?
Or did you had a clear reason to demand the latest version of Mono for those packages?
@BenjV Foraarch64 certainly, because "anything" is better than "nothing". For all other users, probably not. Memory leak issues with the old mono version were the actual starting point of all the updates (see #3470). From there, the challenge was to find any combination of mono and *arr packages that would work together. Took loads of iterations to find anything that seemed stable, until I "dared" to push anything into our repo. The aarch64 problem did not show up until after we merged all changes.
To that extent: Is the bumped mono version a "hard" dependency? No, it isn't. Would I advise non-aarch64 users to go back? No, I wouldn't, especially since we've learned that this is a problem with the gcc compiler for mono on aarch64 platforms really. As you've rightly pointed out - and I sincerely thank you for the hint not to waste more of my time - we cannot fix problems, upstream gave up on already...
I'll see whether we can republish the *arr packages with reduced mono dependency requirements for aarch64 (and only that) in the next couple of days, but am afraid I cannot do more. More than happy to learn about better ideas, if there are any...
@m4tt075 - Do you know if this will be fixed ever? Reason I ask - my Nas box did a system update, which included a Mono update. So now Sonarr and Radarr no longer work.
@CraigInBrisbane I don't know but wouldn't count on it. I'd either downgrade again or patch the Sonarr and Radarr packages as others have described earlier in this threat.
I'll see whether we can republish the
*arrpackages with reducedmonodependency requirements foraarch64(and only that) in the next couple of days, but am afraid I cannot do more. More than happy to learn about better ideas, if there are any...
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?
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.
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
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.
https://github.com/hgy59/spksrc/releases/tag/Mono_5.8
Please give feedback whether this is running so I can upload it to the SynoCommunity package respository.
@hmelville I have built mono 5.8 for aarch64.
https://github.com/hgy59/spksrc/releases/tag/Mono_5.8Please 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
The version 5.8 for DS420j (rtd1296) was available already before - but it was missing for armada37xx (DS120j, etc.).
Anyway I have deleted 5.8.0.108-11 for rtd1296-6.1 and uploaded aarch64-6.1 (for rtd1296 and armada37xx).
Most helpful comment
What worked for me:
After some restarts and updating Radarr and Sonarr to the newest Version, everything works again without backup and restore.