Up until 5 or 6 days ago, my configuration worked fine without a hitch. I was out of town and when I came back, sonarr apparently stopped working automatically.
Now, whenever I have a look at the logs, I see that it did nothing for hours on end and only starts working, when I manually initiate it.
Here’s a sample from my log:
NzbSearchService Searching 1 indexers for [New Girl : S04E22] 11:34am
EpisodeSearchService Episode search completed. 0 reports downloaded. 4:27pm
From 4.30pm to 11.30am the next day, it did absolutely nothing, despite the fact that at the very least, there should be an RSS sync every 15 minutes.
This also means that it doesn’t download anything automatically and even if and when I initiate a backlog search from the Wanted tab, it sends the download links to sabnzbd and once the downloads finish, it doesn’t import anything without me explicitly hitting “Rescan Drone factory folder”.
On a technical note:
I have the latest sonarr develop build on Ubuntu Server 14.04 x64 and the service itself has been up and running for a while, I restarted sonarr from the web interface and the terminal and restarted the server.
Is this a known bug of current develop builds? Is it something else (recent backend changes)? Or is it my configuration (although it stopped working without me changing anything)?
I want to know whether it’ll work again on its own or whether I have to reinstall.