Service Auto-Start Not working

This has been an issue for me for a while but not really very temporarily difficult to fix so haven’t really said anything however i am curious if other people are having this issue

On my Windows Server i run ND as a service and it works great however sometime when i reboot the server or if it does an ND update (Especially on V1 when it ND had to be rebooted for a update) the service sometimes never seems to want to auto-start despicte me having it set to do that in the service settings so sometimes i think it is running and i go to access the page and it won’t connect so i then have to remote into the server open up services find it and start it back up

this is my settings pretty much default can anyone see why it would be causing this

Restarting after a drone update and after a system restart are completely different actions. If it doesn’t restart after a drone update thats an issue, but I haven’t seen that myself.

The service not starting after a reboot is an issue, I think the first thing we need to do is add a service dependency on the TCP/IP stack, right now we don’t have any dependencies which may cause issues when it starts up and doesn’t have network access. This will require the service to be re-installed. I have added a card to Trello to track this: https://trello.com/c/WfppfAcN/428-add-dependency-on-tcp-ip-protocol-driver

awesome glad you are gonna take a look at it

Like i said not really a major issue for me but just a little annoyance that if it can be fixed i would appreciate it :slight_smile:

@protocol77 I’ve pushed a change to a new branch “service-dependencies”, if you could switch your branch (Settings -> General - advanced settings need to be shown) to that branch, update, then uninstall and reinstall the service.

Then try a couple reboots to see if the service starts up properly and consistently. Let me know how it goes and we can add more dependencies if needed.

okay will do :slight_smile:

Update: Okay switched to service-dependencies, ran update, then uninstalled service, left it for a minute or two and checked page to see if it was off then re-installed it then rebooted server

and still it wouldnt start remote desktop’d into the service to force a initial login in case it required me to login before service would start (i had to do this for sab anyways) still didn’t start so went to service and status is “Stopped”

Not sure if this helps but going to the dependencies on the services NzbDrone Properties it says

TCP/IP Protocol Driver is listed as a dependencies but i cannot see it in my list of services

Yeah, its not actually listed as a service, but its valid. Do you happen to have SABnzbd running on that box as a service?

They also take a dependency on event log, which I was considering, but I’m not sure if it will help. Pushed another build with EventLog as a depency, on the same branch, let me know how it goes.

yeah i have sabnzbd running on the same box as it is my server but i could not get sabnzbd to even install as a service let alone run as one and the sab forums weren’t very helpful in their replies to my thread so what i did is set sabnzbd as a task that runs at startup so it will start sab without me even logging in

I thought about doing this with nzbdrone as there is that nzbdrone.exe in the folder this is sort of a hodge-podge way of doing it instead of using the service option

I might give it a go as you can set it to run whether someone is logged on or not and you can set it to run admin rights this option may work out pretty well perhaps if it does it could be a alternative we could add to the help wiki for those who have the same issue as me it it working well for sabnzbd

I used to run SAB like this, but now use the service. You can get windows to auto login on boot too, its a work around, but of course it would be better to make it work.

yeah obviously the service would be much simpler but i have tested it and it works this way i set it to wait 30 seconds after reaching the login screen to get things settled bit it then starts both NzbDrone and Sabnzbd i had to create two seperate tasks though because for some reason they would not work having two actions attached to the same task but anyways it seems to work this way

for some reason i just cannot get the service to stay running but hey as i said before not a big deal was easy to start ND backup and even easier now :slight_smile:

If i am using task schedule to start ND now should i switch back to develop from service-dependencies branch

will i get the latest updates from develop on this or???

If you could switch back to service-dependencies and test the service that would be great, I don’ know of anyone else having this issues currently. Let me know if it works, if not, switch back to develop and another method to start it.

I’d recommend using the Start up folder instead of a scheduled task, its what the folder is designed for. It will run as the context of the user running it and its as easy as dropping a shortcut in a folder (one for each app), then look at: http://wiki.ljackson.us/Control_Userpasswords2 to log into Windows on boot.

okay i will stick with service-dependencies i just uninstall the service and re-installed you said you push another build or something didnt you my current one is .695

Ahh looks like something failed during the build, fixing it now.

Went live about 20 minutes ago.

yep just checked it is now .697 let’s see how this one goes :slight_smile:

@protocol77 Any news? good or bad, we can take it. :slight_smile:

yeah still no good had to shut off my server to swap out a drive i had it off for about 10 minutes when turned back on it did not start back up will give it another test though and see what happens i will report back in a little bit

I also have a bit of spare time so i am gonna give a few more tests at the linux version as well up until now i have been running Ubuntu Distros i found a nice Debian Testing Distro called SolydX so i will give that a try and see if we have the Mono Issue on that

UPDATE: Just turned my server off again for another 10 minutes then turned back on and left it to sit another 10 minutes and unfortunately the service did not start so still not working :frowning: the only way i have been able to get it to start on boot is using it in task scheduler and setting to boot at startup that way

Update: Been running it on service-dependencies for the last couple of days and so far it seems to be starting with windows as a service i cannot say for sure if it is working and fixed but it is running okay so far