I see the shutdown icon in the system page, but not a restart one. Am I blind as usual?
Restart is windows only because mono hides the location of the drone executable, need to figure out how to properly find it before we add it.
Ah. Possibly make it a configurable item? In the config file only?
Yeah, maybe, but it’s an ugly way to do it so I’m hoping we can find a better way.
I see you found the fix. 
Awesome!
Yeah, wasn’t too crazy, very happy. Working properly for you?
Yep. It’s fast and quiet. Just a little pop-up in the bottom right. I like it.
Hmm . . . I’m not sure this is working correctly.
First off, I start drone w/ a shell script in cron @reboot.
I just updated drone via apt-get, and went into the web gui to do a restart. It’s not actually restarting.
I’m guessing I should be using a different method to start drone. Does that sound correct to you?
It shouldn’t really matter how drone is started, the restart mechanism will start a 2nd instance and kill off the other instance. I didn’t test your specific startup scenario, but this should all be logged.
I’m not seeing anything in the log. Honestly the only thing I can tell that is happening when I hit the restart button is it changes the outline color for a moment. I’ll manually kill it & restart it, see if the updates fixed it.
EDIT: I’m now seeing the ‘restart requested’ in log files. Seems to be working now. I’ll keep an eye on it and see how things go.
Okay, let me know. I disabled the UI messaging because it was sticking post restart/shutdown, will work out a better solution for that.
I’m getting absolutely and utterly spammed by this every second for about the past 24 hours.
14-2-16 00:49:22.6|Info|Bootstrap|Starting NzbDrone Console. Version 2.0.0.1127
14-2-16 00:49:24.3|Info|ps|Starting ps --pid 12147 -o args=
14-2-16 00:49:24.3|Info|SingleInstancePolicy|1 instance(s) of NzbDrone are running
14-2-16 00:49:24.3|Warn|SingleInstancePolicy|Another instance of NzbDrone is already running.
14-2-16 00:49:24.4|Info|Bootstrap|Application is being terminated. Reason : Another instance is already running
Any ideas? I’m using Method 1 from https://github.com/NzbDrone/NzbDrone/wiki/Autostart-on-Linux to start NZBDrone on reboot and startup of my NAS.
Sounds like upstart is upset that the PID it was tracking for drone was killed during a restart and keeps trying to start a new one, which is how upstart is supposed to work.
Just shutdown drone and upstart will restart it, if you need to restart you will need to do it manually until I can sort out a way around this.