Update is not working

JBDragon · June 14, 2014, 6:12pm

I’m trying to update nzbdrone to the newest Windows version. Clicking on the update button, but it’s failing!!! As in not working. The first Update I did to 2.0.0.1516 it seemed to go just fine. It got updated and the Update button disappeared. But on 2.0.0.1533, I clicked on the Update button I get the Box Downloading update, then shows Extracting and then Installing. The problem is the Install button for 2.0.0.1533 is still there. it doesn’t look like it updated. Now it’s the same with the 2.0.0.1581 update. I click on the Install button and it looks like it’s working, but in the end, nothing has changed. Just now I have to Updates and 2 Install buttons and I think I’m still running 2.0.0.1516. Actually clicking on the INFO button and looking in about, it’s showing 2.0.0.1522. So I’m not sure what the hell is going on?!?!?!

About is still showing 2.0.0.1522

JBDragon · June 14, 2014, 6:17pm

Went into the Directory for nzbdrone and found those logs, so this is the last one.

System.ArgumentOutOfRangeException: Number of arguments are unexpected, expected: 3, found: 2
Parameter name: args
at NzbDrone.Update.UpdateApp.ParseArgs(String[] args) in m:\BuildAgent1\work\328d72309b633a8\src\zbDrone.Update\UpdateApp.cs:line 108
at NzbDrone.Update.UpdateApp.Start(String[] args) in m:\BuildAgent1\work\328d72309b633a8\src\zbDrone.Update\UpdateApp.cs:line 55
at NzbDrone.Update.UpdateApp.Main(String[] args) in m:\BuildAgent1\work\328d72309b633a8\src\zbDrone.Update\UpdateApp.cs:line 45

JBDragon · June 14, 2014, 6:23pm

I’m not sure why it looks like it’s showing the m: drive?!?! I know m: is reserved for one of my Internal Card Reader slots. Why Nzbdrone would be trying to go there?!?!?!

markus101 · June 15, 2014, 1:46am

@JBDragon said:
So I’m not sure what the hell is going on?!?!?!

Thats a pretty aggressive way to ask for help.

I have an idea what is going on, but I need more information to confirm, please provide debug logs of the update process: https://github.com/NzbDrone/NzbDrone/wiki/Log-Files

@JBDragon said:
I’m not sure why it looks like it’s showing the m: drive?!?! I know m: is reserved for one of my Internal Card Reader slots. Why Nzbdrone would be trying to go there?!?!?!

Again with the wild punctuation…

M:\ has nothing to do with your system, it comes from the system where drone was built (our systems), the information there is important to us when there are issues, but you can safely ignore it.

JBDragon · June 15, 2014, 3:24am

I wasn’t trying to be aggressive. I didn’t mean to come off that way. I thought the log I gave above is what you just asked for? That’s where I got it on my computer in the Programdata/NzbDrone/UpdateLogs. The first couple Logs are larger in size back in May 26th 2014 like 53 KB in size. Which shows Updating to 2.0.0.1516. It looks kind of normal to me showing updating a bunch of files. The next file on May 27th 2014, it’s a update to 2.0.0.1522. Again looks normal to me for a update process on a program. So the first 2 logs looks normal to me and much longer. After that starting on June 3 2014 all the way up to just now when I tried it once again, the file sizes are 1 KB in size and they all look the same as shown above. There must be like 200 of these Update files with the Date and time. all looking the same inside. I can randomly pick one like this one.

System.ArgumentOutOfRangeException: Number of arguments are unexpected, expected: 3, found: 2
Parameter name: args
at NzbDrone.Update.UpdateApp.ParseArgs(String[] args) in m:\BuildAgent1\work\328d72309b633a8\src\zbDrone.Update\UpdateApp.cs:line 108
at NzbDrone.Update.UpdateApp.Start(String[] args) in m:\BuildAgent1\work\328d72309b633a8\src\zbDrone.Update\UpdateApp.cs:line 55
at NzbDrone.Update.UpdateApp.Main(String[] args) in m:\BuildAgent1\work\328d72309b633a8\src\zbDrone.Update\UpdateApp.cs:line 45

So the first two updates were great, and after that, not so much. I’ve tried update and then Reboot the computer. This is a brand new Desktop PC I built. I’m just not sure what’s going on. Is is bug in the program? A issue with some other piece of software? My computer? I didn’t see any other posting having this issue, so I would guess it’s something with my setup? Something got out of whack on my end? I’m a fan of the program. I’ve used Sickbeard for over a year, but there’s a number of things I just like better with Nzbdrone. I didn’t want to do anything crazy like uninstalling the software to re-install, configuring it again just to have the same issue. I’ve done that before on other programs and it didn’t fix anything, just wasted a bunch of time.

Do you want a Debug log that worked? All the others look like the the one I posted above. That’s the whole log in that 1KB file of around 200 of them. I have the program set to Debug mode. Again, sorry if I seem to be coming off strong.

markus101 · June 15, 2014, 3:26am

Sorry, looking for the debug log when the update is started (not the log of the updater), need to determine what parameters are being sent to the updater, since they seem to be interpreted wrong.

protocol77 · June 15, 2014, 6:04am

What Version of windows are you using perhaps a permissions issue Windows 8 is tighter with them especially for C:\ Drive i assume this is for enhanced security but has caused me headaches before with other software

markus101 · June 15, 2014, 3:02pm

@protocol77 its not permissions related, its something internal to drone, but I need to know whats causing it to prevent it.

JBDragon · June 15, 2014, 10:23pm

I hate Windows 8, so I’m using Windows 7. As for the Logs, I have the nzbdrone along with nzbdrone.0 though nzbdrone.4 that are all 1000 KB in size except for the one with no point number. They all look to have been updated today at different times. Is it one of those you want to look at? Any of them seem way to long to post here. Is it the Log in the program it’s self? Maybe I’m just not getting it. In the Logs Table after a update, it looks like this.
Component Message Time
InstallUpdateService NzbDrone will restart shortly. 7:13 PM
InstallUpdateService Starting update client C:\Users\Joe Jr\AppData\Local\Temp
zbdrone_update\zbDrone.Update.exe 7:13 PM
InstallUpdateService Preparing client 7:13 PM
InstallUpdateService Update package extracted successfully 7:13 PM
InstallUpdateService Extracting Update package 7:13 PM
InstallUpdateService Update package verified successfully 7:13 PM
InstallUpdateService Verifying update package 7:13 PM
InstallUpdateService Downloading update 2.0.0.1533 7:11 PM
InstallUpdateService Deleting old update files 7:11 PM
DbFactory Database Compressed 7:11 PM
DbFactory Vacuuming database 7:11 PM

To me, that looks like everything worked just fine in that log, but it didn’t.

markus101 · June 15, 2014, 11:50pm

Enable debug logging, clear the log files (via the UI), run the update (via the update page), pastebin the log file afterwards.

How to enable debug logging is in the link I posted above.

JBDragon · June 16, 2014, 12:38am

I tried posting the Log, but it’s way to long. It grows way to fast. I delete, run the update and then I get that and a bunch of other stuff also going on. By the time it’s done with the Update Process on screen and I grab a copy of the log, it’s huge. Anyway I grabbed a copy and it’s at http://pastebin.com/rCSi33v6

markus101 · June 16, 2014, 1:49am

Thanks, found what I need, I’ll take a look.

markus101 · June 16, 2014, 11:00am

This issue was already fixed in develop, it will be available in the next release.

JBDragon · June 16, 2014, 8:54pm

Ok, and when that version comes out will it install or will I have the same issue, and have to do a complete new install with that version to get the fixed version working? Other then this one issue, I’m a big fan of Nzbdrone. It’s been working out great for me.

markus101 · June 16, 2014, 9:21pm

It should update seamlessly, worst case you would have to install if over top of the existing install manually (which you could now).

JBDragon · June 17, 2014, 11:59pm

Ok, thanks for the help.