Permission issues after Mono 6 upgrade

[Xtropy74]

Sonarr version (exact version): 3.0.2.537
Mono version (if Sonarr is not running on Windows): 6.0.0.313
OS: ubuntu-18.04.2
Debug logs:

https://pastebin.com/VLtM1Me1

Description of issue:

Ubuntu pushed out an update a few days ago to Mono 6.0.0.313 and since this update, Sonarr will not complete post-processing of completed downloads. The download is passed to Sabnzbd+ fine, the download completes and copies/renames the file to the proper folder but then hangs in Activity and turns orange stating “Failed to Import Episode” with log errors stating:

|Warn|ImportApprovedEpisodes|Couldn’t import episode
[v3.0.2.537] System.UnauthorizedAccessException: Access to the path is denied. —> System.IO.IOException: Operation not permitted

The file itself is copies fine (it even renames the file as it always does) but has a .partial~ file extension to it.

Current work around is to manually remove the .partial~ file extension and then re-scan the show/remove it from Activity and it works perfectly. There are no permission issues (all my files folders are 777) and I’ve had this exact working Sonarr setup for years. The only thing that has changed is regular upgrades to Sonarr v3 (when released) and this upgrade to Mono 6.

Hope this helps find a resolution.

Thanks

[markus101]

mono 6 changed a lot around disk access, we haven’t investigated anything, but it looks like it’s breaking enough that it’s going to be some time before we can hammer out the issues.

[Xtropy74]

Thanks for the details. I can confirm that a rollback to Mono 5 fixed this issue.

For anyone affected by the upgrade, here is what I did to roll back to 5.20.1.34 (current Mono 5 snapshot) on Ubuntu 18.04:

Edit your /etc/apt/sources.list.d/mono-official-stable.list and change:

deb https://download.mono-project.com/repo/ubuntu stable-bionic main

to:

deb https://download.mono-project.com/repo/ubuntu stable-bionic/snapshots/5.20.1.34 main

That will pin it to version 5.20.1.34

Basic Steps to Downgrade:

sudo apt-get remove mono-runtime

Edit your mono-official-stable.list file per above

sudo apt-get update
sudo apt-get install mono-runtime
sudo apt-get install sonarr

More details on the mono website:

http://www.mono-project.com/docs/getting-started/install/linux/#accessing-older-releases

Reference for the versions available:

http://download.mono-project.com/repo/debian/pool/main/m/mono/

[behold]

Thanks for the how to, shall see if it works so eps dl and move correctly, but sudo apt-get install sonarr was Unable to locate package sonarr, had to use sudo apt-get install nzbdrone

[Obelisk]

I had this issue as well because I am using docker with watchtower updating containers daily. The latest tags for sonarr and radarr are using mono 6 in their containers but they have a 5.14 tag for both that is using mono 5.

linuxserver/radarr:5.14
linuxserver/sonarr:5.14

[glc650]

When did v3 switch to mono 6.0?

[markus101]

Sonarr v3 (or any version) does not require mono 6.

[HabsKilla]

@Xtropy74
Thanks for the rollback instructions.

I was also having the same issue as you. I thought a recent power outage corrupted the TV volume on my NAS. Thankfully, it was just mono 6.0 jerking us around.

[rhom]

linuxserver/sonarr:5.14

thats for v2 (stable), the last v3 image with mono 5.x seems to be linuxserver/sonarr:3.0.2.537-ls102 which has 5.20.1.19

[matttwinkletoes]

sudo apt-get install mono-runtime

When I do this I get a bunch of dependency errors which I have traced back to this

The following packages have unmet dependencies:
 mono-runtime-sgen : Depends: libc6 (>= 2.27) but 2.23-0ubuntu11 is to be installed
                     Depends: mono-runtime-common (= 5.20.1.34-0xamarin4+ubuntu1804b1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

How do i get libc6 greater than 2.27 when the repo listed above only has 2.23?

[Obelisk]

Yeah… as I had stated I had been using the tag “latest” which is v2 so 5.14 is the correct alternative if you had been using that. The only tag which uses v3 is “preview” but as you suggest if you were using “preview” and want ot continue to run v3 then the tag you suggested is appropriate.