Replace SharpRaven with new Sentry SDK

v3 Testing
#1

Sonarr version (exact version): 3.0.2.587 ,last that works anything after fails as below
Mono version (if Sonarr is not running on Windows): 5.20.1.34
OS: ubuntu 18.04. Linux sonarr 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Debug logs: I never get any
Description of issue:

Since the SDK change I cannot start sonarr, I get repeated errors

Aug 23 14:29:44 sonarr systemd[1]: Started Sonarr Daemon.
Aug 23 14:29:44 sonarr mono[11143]: NLog Exception: System.TypeLoadException: Could not load type of field ‘Sentry.SentryOptions:k__BackingField’ (29) due to: Could not load file or assembly ‘System.Net.Http, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies.
Aug 23 14:29:44 sonarr mono[11143]: at NzbDrone.Common.Instrumentation.Sentry.SentryTarget…ctor (System.String dsn) [0x00013] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Instrumentation\Sentry\SentryTarget.cs:91
Aug 23 14:29:44 sonarr mono[11143]: at NzbDrone.Common.Instrumentation.NzbDroneLogger.RegisterSentry (System.Boolean updateClient) [0x0002d] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Instrumentation\NzbDroneLogger.cs:106
Aug 23 14:29:44 sonarr mono[11143]: at NzbDrone.Common.Instrumentation.NzbDroneLogger.Register (NzbDrone.Common.EnvironmentInfo.IStartupContext startupContext, System.Boolean updateApp, System.Boolean inConsole) [0x00030] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Instrumentation\NzbDroneLogger.cs:43
Aug 23 14:29:44 sonarr mono[11143]: at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00007] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Console\ConsoleApp.cs:31
Aug 23 14:29:44 sonarr mono[11143]: Press enter to exit…
Aug 23 14:29:46 sonarr systemd[1]: sonarr.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 14:29:46 sonarr systemd[1]: sonarr.service: Failed with result ‘exit-code’.
Aug 23 14:29:46 sonarr systemd[1]: sonarr.service: Service hold-off time over, scheduling restart.
Aug 23 14:29:46 sonarr systemd[1]: sonarr.service: Scheduled restart job, restart counter is at 3.
Aug 23 14:29:46 sonarr systemd[1]: Stopped Sonarr Daemon.

#2

I did back off mono 6 per another reading another post here but that did not help, guessing I missing something in mono that needs updating further or needs replacement?

#3

Does /usr/lib/sonarr/bin/System.Net.Http.dll exist?

Anyway, runs fine on my own machine, ubuntu 16.04.6, mono 5.20.1.19, sonarr 3.0.2.607.

#4

ls -al System.*

-rw-r–r-- 1 sonarr sonarr 273920 Aug 16 07:09 System.Data.SQLite.dll
-rw-r–r-- 1 sonarr sonarr 704792 Aug 16 07:09 System.Data.SQLite.xml
-rw-r–r-- 1 sonarr sonarr 27616 Aug 16 07:09 System.Runtime.InteropServices.RuntimeInformation.dll
-rw-r–r-- 1 sonarr sonarr 78992 Aug 16 07:09 System.ValueTuple.dll

So , where did it go? This is my running version @ 3.0.2.587

Ok, it needs to be there for for .601 and .607? Is that what I might understand?

One more thing if it helps, sonarr update would fail, had to download and install via dpkg. So I have all three deb files, found that 587 would get me back up.

#5

Ok, it needs to be there for for .601 and .607? Is that what I might understand?

Yes

#6

Just install 607, its there.

Fails, won’t start same error

Still poking around

#7

or one of its dependencies

That helps alot, anywhere I can see a log with more info?

Anyway, dpkg -i 3.0.2.587 and back in business

Let me know if there is something I can check, hate to be the odd man out

#8

Did you actually check if System.Net.Http existed in the directory when 607 was installed?

#9

Yes, sorry thought I shared that

-rw-r–r-- 1 sonarr sonarr 21192 Aug 22 21:36 System.Linq.Parallel.dll
-rw-r–r-- 1 sonarr sonarr 21192 Aug 22 21:36 System.Linq.Queryable.dll
-rw-r–r-- 1 sonarr sonarr 198472 Aug 22 21:36 System.Net.Http.dll
-rw-r–r-- 1 sonarr sonarr 21208 Aug 22 21:36 System.Net.NameResolution.dll
-rw-r–r-- 1 sonarr sonarr 22248 Aug 22 21:36 System.Net.NetworkInformation.dll
-rw-r–r-- 1 sonarr sonarr 21168 Aug 22 21:36 System.Net.Ping.dll
-rw-r–r-- 1 sonarr sonarr 22216 Aug 22 21:36 System.Net.Primitives.dll

#10

Run locate System.Net.Http

#11

avid@sonarr:/$ locate System.Net.Http
/usr/lib/mono/msbuild/15.0.old/bin/System.Net.Http.dll
david@sonarr:/$

#12

there it is… run apt install libmono-system-net-http4.0-cil

#13

Very good Sir, thank you we have a winner

Version 3.0.2.607
Package Version 3.0.2.607
Mono Version 5.20.1.34

#14

You likely recently installed mono/sonarr. Our older package (3.0.1) had a msbuild dependency which also had a dependency on system-net-http. 3.0.2.500ish no longer had that msbuild dependency and thus not system-net-http either.
When I tested the new version on my own system, I still had system-net-http installed so didn’t notice the breakage.
Anyway, it’ll be as easy as publishing 3.0.3 to add the missing dpkg dependency.

#15

My uptime shows system life of 79 days if that fits your timeline. (tuptime) ± a day or so. I held on to my original nzbdrone as long as I felted I could

#16

I just mean you likely never installed 3.0.1 or did apt auto-remove, all legitimate. How doesn’t really matter. I just wanted to explain how I didn’t catch it :smiley:

1 Like
#17

One question, did the auto update fail but leave sonarr intact? or did it succeed but then break Sonarr?

#18

I think the answer ti your question is yes, it keep running but would not update via its own update.

Its when I forced the update via dpkg install via sonarr_3.0.2.601_all.deb or sonarr_3.0.2.607_all.deb that it failed

Thats when I started turning on debug etc. But it never got far enough to log anything. Syslog gave me what I posted to you

Sorry seems like I might fall into a fringe condition, waited a few days to see if anyone else complained.

#19

That’s the answer I was hoping for. Coz that means that I didn’t break any system without the user noticing.

And you didn’t fall into a fringe condition, in fact I wished I new earlier that there was a problem :slight_smile: So thank you for reporting it.

#20

Correct, just kept telling me there was an update.

I will add that it did complete thru the backup, So I have a few.