Sonarr version (exact version): 2.0.0.5163
Mono version (if Sonarr is not running on Windows):5.2.0
OS: Freenas 11.1 U4 in iocage jail
Debug logs:No errors in the logs but was set to trace and not debug, have since changed it to debug
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here. Post in .txt not .doc, .rtf or some other formatted document)
Description of issue:
At random times when I go to the web page I get
This site can’t be reached
192.168.5.71 refused to connect.
Search Google for 192 168 8989 sonarr
ERR_CONNECTION_REFUSED
I can fix it by restarting the iocage jail
Trace logging will output debug logs as well. You’ll need trace logs in this case anyways. You’ll also need to capture the standard output and error to a file, in the event mono is crashing (since nothing will log in that case).
Crashed again and here is part of the log
18-6-13 21:14:48.0|Debug|MonoVersionCheck|Mono version is 3.10 or better: 5.2.0
18-6-13 21:14:48.9|Debug|Api|[GET] /api/config/ui: 200.OK (9 ms)
18-6-13 21:14:48.9|Debug|Api|[GET] /api/system/status: 200.OK (15 ms)
18-6-13 21:14:49.0|Debug|Api|[GET] /api/profile: 200.OK (12 ms)
18-6-13 21:14:49.0|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (20 ms)
18-6-13 21:14:49.1|Debug|Api|[GET] /api/health: 200.OK (8 ms)
18-6-13 21:14:50.0|Debug|Api|[GET] /api/series: 200.OK (926 ms)
18-6-13 21:14:50.1|Debug|Api|[GET] /api/command: 200.OK (6 ms)
18-6-13 21:14:50.1|Debug|Api|[GET] /api/language: 200.OK (10 ms)
18-6-13 21:14:50.1|Debug|Api|[GET] /api/tag: 200.OK (12 ms)
18-6-13 21:14:50.2|Debug|Api|[GET] /api/health: 200.OK (1 ms)
18-6-13 21:14:50.2|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (5 ms)
18-6-13 21:14:50.4|Debug|Api|[GET] /api/update: 200.OK (199 ms)
18-6-13 21:14:54.4|Debug|Api|[GET] /api/health: 200.OK (0 ms)
18-6-13 21:14:54.5|Debug|Api|[GET] /api/health: 200.OK (0 ms)
18-6-13 21:14:54.5|Debug|DiskProvider|Unable to get free space for ‘/’, unable to find suitable drive
18-6-13 21:14:54.5|Debug|DiskProvider|Unable to get free space for ‘/’, unable to find suitable drive
18-6-13 21:14:54.5|Debug|Api|[GET] /api/diskspace: 200.OK (58 ms)
18-6-13 21:14:54.5|Debug|Api|[GET] /api/diskspace: 200.OK (58 ms)
18-6-13 21:14:56.5|Debug|Api|[GET] /api/log?page=1&pageSize=50&sortKey=time&sortDir=desc&filterKey=level&filterValue=Error: 200.OK (189 ms)
18-6-13 21:14:56.5|Debug|Api|[GET] /api/log?page=1&pageSize=50&sortKey=time&sortDir=desc&filterKey=level&filterValue=Error: 200.OK (10 ms)
18-6-13 21:15:01.6|Debug|Api|[GET] /api/log/file: 200.OK (50 ms)
18-6-13 21:15:01.9|Debug|Api|[GET] /api/log/file/sonarr.debug.txt: 200.OK (118 ms)
18-6-13 21:15:04.6|Debug|Api|[GET] /api/log/file/sonarr.debug.txt: 200.OK (8 ms)
You’re going to need to enable trace logging and redirect standard output and error to a file to see what’s happening when Sonarr crashes (since mono crashing means logs aren’t written, most of the time).
I have exactly the same thing happening under Linux.
Version: 2.0.0.5163
Mono Version: 5.12.0.226
Running on a RPi 1B
I’m not exactly sure when this started happening… I did a full reinstall of Sonarr and Sabnzbd a few months ago when I did a Raspbian Stretch image…
Sonarr runs for a day of so and then seems to lock up when doing a sync on RSS… but not all the time and not predictably.
I know how to choose trace logging from the GUI but don’t know how to redirect standard output error to a file. Any tips.
I’m thinking that it all steps from my version of mono 5.2 which is “buggy”.
Redirecting to a file would be done in the command that starts Sonarr. Not sure how to do that within the jail, googling it would be your best bet.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.