I did a clean install today of the newest Dietpi image, and came to the conclusion that neither Sonarr nor Radarr (and according to some, Jacket is affected as well) seemed to work.
Tried three different SD cards before coming to the conclusion this was either an installation problem or something else, so i did some searching and came to the conclusion that i was far from alone, and that the issue was (supposedly) widespread across several distributions.
Since that seemed a bit odd, i searched again, and came to the conclusion that the problem seems to be with Mono/NLog, if posts on the Sonarr Github : click me! and a bugreport posted on Mono's Github : Click me harder!! are to be believed.
Apt-get update currenly yields the following result :
Code: Select all
root@*my system name here*:~# apt-get update
Get:1 http://download.mono-project.com/repo/debian stretch InRelease [5863 B]
Ign:1 http://download.mono-project.com/repo/debian stretch InRelease
Get:2 https://apt.sonarr.tv master InRelease [13.3 kB]
Hit:3 https://www.mirrorservice.org/sites/archive.raspbian.org/raspbian stretch InRelease
Hit:4 https://archive.raspberrypi.org/debian stretch InRelease
Ign:2 https://apt.sonarr.tv master InRelease
Fetched 19.2 kB in 4s (4593 B/s)
Reading package lists... Done
W: GPG error: http://download.mono-project.com/repo/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A6A19B38D3D831EF
W: The repository 'http://download.mono-project.com/repo/debian stretch InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: https://apt.sonarr.tv master InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EBFF6B99D9B78493
W: The repository 'https://apt.sonarr.tv master InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Suggestions thus far seem to come down to switching back to the previous version of Mono and pinning it until this is fixed, or to wait for a fix.
Personally i've just installed an older version of Mono, which (for me) fixed the issue for now, but YMMV.
(side note; apologies for not (also) using GitHub to report this, i'm rather busy and couldn't find my login info for my GitHub account :oops: )
