Doesn’t seem to want to work for me. I’m currently on 1516 and attempting to update (manually, but with the new method) to 1522. Basically it seems to be going fine until it starts to extract, which never finishes. It extracts a certain (always the same) number of files, then reports the process as complete.
I’ve navigated to where the extract is happening (/var/folders/nn/80srdv1s1dvfjwnnyfh4p78m0000gn/T/nzbdrone_update/) and these are the files it extracts:
And I’ll PM you the log
EDIT: Ah, it seems to be extracting everything again into that new NzbDrone folder…
Yes, then it runs the update client to “install” the update.
Need to see the log file for the updater (nothing special in either log file so you don’t need to PM it). Update log files are in drone’s app data directory (get it from System -> Info in the drone UI).
What version of OS X?
How do you have drone running?
Does restarting from the drone UI work? Has it ever?
I have Drone running via a plist at startup. It basically just calls “mono /Users/Simon/Handies/NzbDrone/NZBDrone.exe”
Honestly, restarting from the drone UI can be hit and miss. It can either work, take ages, or not work at all. It’s flaky basically. I’d say it’s more common for it to not work.
Ok, here’s the content of each of the update logs:
14-5-27 18:45:08.9|Info|UpdateApp|Updating NzbDrone to version 2.0.0.1522 14-5-27 18:45:09.1|Debug|UpdateApp|NzbDrone process ID: 52009 14-5-27 18:45:09.1|Info|UpdateApp|Starting update process. Target Path:/Users/Simon/Handies/NzbDrone 14-5-27 18:45:09.1|Info|InstallUpdateService|Verifying requirements before update... 14-5-27 18:45:09.1|Debug|ProcessProvider|Finding process with Id:52009 14-5-27 18:45:09.1|Debug|ProcessProvider|Found process 52009:mono [/usr/bin/mono] 14-5-27 18:45:09.1|Info|InstallUpdateService|Verifying Update Folder 14-5-27 18:45:09.1|Info|TerminateNzbDrone|Stopping all instances 14-5-27 18:45:09.1|Info|ProcessProvider|[52009]: Killing process 14-5-27 18:45:09.1|Info|ProcessProvider|[52009]: Waiting for exit 14-5-27 18:45:09.1|Info|ProcessProvider|[52009]: Process terminated successfully
Seems that when drone stops (as part of the update process) any spawned process are killed off, which won’t work, either via the built-in updater or via a custom script, since the general process is the same.
Yeah, I was disappointed to see that was one of the easiest ways to get it working on startup without a terminal window. Couple users in IRC sorted out the plist and have been testing updating for the last day or two.
Phew, took a bit of messing about (had a few issues getting the plist to actually work, strange permission things that I’m not completely across just yet (haven’t really been a Mac user for all that long). It’s all working now though. Loads on startup, and the update process works fine. Thanks again markus
