[RPi2] 2.0.0.3953 - Mar 12 2016

Anyone else having problems after installing “2.0.0.3953 - Mar 12 2016”

My system:
Raspberry PI 2
Version: 2.0.0.3953
Mono Version: 4.3.0 (master/1c90513 Sun 29 Nov 18:23:22 GMT 2015)
AppData directory: /home/pi/.config/NzbDrone
Startup directory: /opt/NzbDrone

After I installed 2.0.0.3953 I have had two incidents that I cant
access the sonarr web interface. When I check the status of nzbdrone on
my raspberry it says that it’s running. Tried to restart the service but
no go. I had to restart the Raspberry to get access to sonarr.

I will monitor the problem

The logs doesn’t say so much only:
SceneMappingServiceFailed to
Update Scene Mappings:: Error:
NameResolutionFailureYesterdayTaskExtensionsTask Error: Error:
NameResolutionFailureYesterdaySceneMappingServiceFailed to Update Scene
Mappings:: Error: NameResolutionFailureYesterday

It just stopped again :confused:

How can I go back to previous version?

I ran this line:
mono --debug /opt/NzbDrone/NzbDrone.exe

Got this:

pi@rpi:~$ mono --debug /opt/NzbDrone/NzbDrone.exe
[Info] Bootstrap: Starting Sonarr - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.3953
[Debug] ProcessProvider: Found 0 processes with the name: NzbDrone.Console
[Debug] ProcessProvider: Found 2 processes with the name: NzbDrone
[Debug] ProcessProvider: - [9974] NzbDrone
[Debug] ProcessProvider: - [9888] mono-sgen
[Info] SingleInstancePolicy: 1 instance(s) of Sonarr are running
[Warn] SingleInstancePolicy: Another instance of Sonarr is already running.
[Debug] BrowserService: non-interactive runtime. Won’t attempt to open browser.
[Info] Bootstrap: Application is being terminated. Reason : Another instance is already running

Reloaded this page and nothing happened:
http://192.168.0.15:8989/calendar

Went to:
http://192.168.0.15:8989/

and it started up again.

I don’t know if this could be an issue but I have Monit installed and I check sonarr:

check process Sonarr with pidfile /home/pi/.config/NzbDrone/nzbdrone.pid
alert *****@gmail.com but not on { pid, ppid }
start program = “/usr/sbin/service nzbdrone start”
stop program = “/usr/sbin/service nzbdrone stop”
if failed host 127.0.0.1 port 8989 then restart

Look in /home/pi/.config/NzbDrone/logs/ for actual log files.

I have made some changes in my monit configuration and a couple of restarts.
I will monitor this problem today.

Looks like sonarr is running as it should now…

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.