I have tried setting the service to Automatic and even Automatic(Delayed) and it still never works. I must remember to login to the machine and manually start the service, which always works.
I just noticed this too. I also set the failure options under Recovery to restart the service to no avail.
Yes I have those option set as well yet it is never running after reboot.
For me it has been like this for a few months for sure.
It seems to be a Windows problem, I’ve seen this issue happen with services from Microsoft (Exchange Server).
Not exactly sure what causes it, but it doesn’t seem to happen on new Windows installations (only over time as things slow down) and is accompanied with an event log message saying the service failed to start after X second or milliseconds (but no log messages in Sonarr’s logs so it never got the request to start).
There is never any other service on this windows 8 machine that is not running after startup.
Also if I log in and manually start the service it always works.
This might be because sonarr has other dependencies, which are not yet up when you (re)boot the machine. So when you log in later and start the service, every other service has been running for a while already.
markus: I don’t know what sonarr needs and how easy it is, but you could add a dependency in the service. A quick google suggests adding a dependency on the LanmanServer service. This ensures the sonarr service will be started after that service is up.
For people feeling lucky, you can do this yourself, but beware, here be dragons. You’re going to be messing around with Windows settings that you generally don’t want to mess with:
I just tried that with LanmanServer, but no change after reboot. Then I tried setting the dependency to SabNZB and still not starting.
Is there maybe a batch file that would wait 5 minutes or something?
It’s incredibly annoying when someone else reboot our server and forgets to start NZBDrone.exe manually.
Scheduled task maybe? Or use the startup folder (user needs to login though).