QNAP - Updater can't find process

This is what’s in the log:

15-5-18 13:24:27.3|Info|UpdateApp|Starting Sonarr Update Client
15-5-18 13:24:27.4|Info|UpdateApp|Updating Sonarr to version 2.0.0.3146
15-5-18 13:24:27.5|Debug|UpdateApp|NzbDrone process ID: 19522
15-5-18 13:24:27.5|Debug|UpdateApp|Arguments:
15-5-18 13:24:27.5|Debug|UpdateApp| 19522
15-5-18 13:24:27.5|Debug|UpdateApp| /tmp/nzbdrone_update
15-5-18 13:24:27.5|Debug|UpdateApp| /share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-5-18 13:24:27.5|Debug|UpdateApp|Using executing application: /share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-5-18 13:24:27.5|Debug|UpdateApp|Executable location: /share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-5-18 13:24:27.5|Info|UpdateApp|Starting update process. Target Path:/share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone
15-5-18 13:24:27.5|Info|InstallUpdateService|Verifying requirements before update…
15-5-18 13:24:27.5|Debug|ProcessProvider|Finding process with Id:19522
15-5-18 13:24:27.5|Warn|ProcessProvider|Unable to find process with ID 19522
15-5-18 13:24:27.5|Fatal|UpdateApp|An error has occurred while applying update package.

System.ArgumentException: Process with ID doesn’t exist 19522
at NzbDrone.Update.UpdateEngine.InstallUpdateService.Verify (System.String targetFolder, Int32 processId) [0x000c3] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\InstallUpdateService.cs:72
at NzbDrone.Update.UpdateEngine.InstallUpdateService.Start (System.String installationFolder, Int32 processId) [0x00000] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\InstallUpdateService.cs:76
at NzbDrone.Update.UpdateApp.Start (System.String[] args) [0x00020] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:59
at NzbDrone.Update.UpdateApp.Main (System.String[] args) [0x00042] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:43

Is there a process with that ID running?

Not sure if QNAP prevents the updater from seeing the main process because its a separate executable.

When I do top command via ssh and run “update series” on Sonarr the top process is mono. The PID is not the same. I asked Stephane on the QNAP forum and he told me that his Sonarr updates okay. I pasted the same log as above and he has no idea why this might be happening.

I tried to update again and out of nowhere it worked this time! Weird, right? I didn’t do anything different.

I’m copying the log post-update just in case you can spot a bug and make a fix for the future so others don’t have the issue.

Thanks anyway!

http://pastebin.com/8ptDQ6Zz

My only thought is the update was restarted at the same time Sonarr was restarted, but that would require the restart button to be pressed very shortly after the update button.

Glad to hear its working now :smiley:

1 Like

I have the same problem, however I have tried several times and getting the same error. I tried rebooting the QNAP, changing the directory’s permissions to 777 with no luck. Trying to update to 2.0.0.3154 - May 21 2015 Sonarr package. Using Mono ver. 4.0.1 (tarball Wed Apr 29 13:04:42 EDT 2015) with Sonarr 2.0.0.3004. I keep returning the error below. I have attempted the update several times without success. Any ideas?

15-5-21 17:36:57.7|Info|UpdateApp|Starting Sonarr Update Client
15-5-21 17:36:57.8|Info|UpdateApp|Updating Sonarr to version 2.0.0.3154
15-5-21 17:36:58.0|Debug|UpdateApp|NzbDrone process ID: 28776
15-5-21 17:36:58.0|Debug|UpdateApp|Arguments:
15-5-21 17:36:58.0|Debug|UpdateApp| 28776
15-5-21 17:36:58.0|Debug|UpdateApp| /tmp/nzbdrone_update
15-5-21 17:36:58.0|Debug|UpdateApp| /share/CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-5-21 17:36:58.0|Debug|UpdateApp| /nobrowser
15-5-21 17:36:58.0|Debug|UpdateApp|Using executing application: /share/CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-5-21 17:36:58.0|Debug|UpdateApp|Executable location: /share/CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-5-21 17:36:58.0|Info|UpdateApp|Starting update process. Target Path:/share/CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone
15-5-21 17:36:58.0|Info|InstallUpdateService|Verifying requirements before update…
15-5-21 17:36:58.0|Debug|ProcessProvider|Finding process with Id:28776
15-5-21 17:36:58.0|Warn|ProcessProvider|Unable to find process with ID 28776
15-5-21 17:36:58.0|Fatal|UpdateApp|An error has occurred while applying update package.

System.ArgumentException: Process with ID doesn’t exist 28776
at NzbDrone.Update.UpdateEngine.InstallUpdateService.Verify (System.String targetFolder, Int32 processId) [0x000c3] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\InstallUpdateService.cs:72
at NzbDrone.Update.UpdateEngine.InstallUpdateService.Start (System.String installationFolder, Int32 processId) [0x00000] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\InstallUpdateService.cs:76
at NzbDrone.Update.UpdateApp.Start (System.String[] args) [0x00020] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:59
at NzbDrone.Update.UpdateApp.Main (System.String[] args) [0x00042] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:43

Only thing I can really think of is:

  1. Check the process ID of NzbDrone.exe
  2. Start the update process
  3. Check the Process ID of NzbDrone.exe again
  4. Compare them all

If they are all the same then it sounds like there is process isolation that breaks Sonarr’s updater, otherwise it sounds like something is restarting Sonarr.

Thanks for you response, QNAP_Stephane has verified that there is a problem in the updater and has since updated the Package in the QNAP forum.

1 Like

Hi this Stephane from Qnap (Qnap_Stephane) , just found the bug it is related to the use of QMono 4.0.1 which avoid updater to run correctly, may be too recent for Sonarr.

Qnap user should downgrade to Qmono 3.10.0.0 ( http://forum.qnap.com/viewtopic.php?f=214&t=109446 )

:wink:

Since Stephane mentioned that the problem is that mono 4 may be too new, could the Sonarr devs check if there’s a way to make it work? I currently cannot update the app to get the fixed and new features like rtorrent support.

Mono 4.0.1 is working on other systems (with updating), we don’t have a QNAP device to test on, but it sounds like a problem with the mono package for QNAP.

Seriously guys, it must be the app. It works on mono 3.10 but stops working in mono 4.x so it can’t be mono. I don’t like to run old software in my box because it is also a webserver and I don’t want to be affected by security vulnerabilities. I can help with whatever you need, just tell me what to do and how, but please fix this. It’s really annoying! Here’s what it shows when I last tried to update:

15-7-23 13:31:45.8|Info|UpdateApp|Starting Sonarr Update Client
15-7-23 13:31:45.9|Info|UpdateApp|Updating Sonarr to version 2.0.0.3357
15-7-23 13:31:46.0|Debug|UpdateApp|NzbDrone process ID: 30447
15-7-23 13:31:46.0|Debug|UpdateApp|Arguments:
15-7-23 13:31:46.0|Debug|UpdateApp| 30447
15-7-23 13:31:46.0|Debug|UpdateApp| /share/homes/admin/.config/NzbDrone/nzbdrone_update
15-7-23 13:31:46.0|Debug|UpdateApp| /share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-7-23 13:31:46.0|Debug|UpdateApp|Using executing application: /share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-7-23 13:31:46.0|Debug|UpdateApp|Executable location: /share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone/NzbDrone.exe
15-7-23 13:31:46.0|Info|UpdateApp|Starting update process. Target Path:/share/CE_CACHEDEV1_DATA/.qpkg/QSonarr/NzbDrone
15-7-23 13:31:46.0|Info|InstallUpdateService|Verifying requirements before update…
15-7-23 13:31:46.0|Debug|ProcessProvider|Finding process with Id:30447
15-7-23 13:31:46.0|Warn|ProcessProvider|Unable to find process with ID 30447
15-7-23 13:31:46.0|Fatal|UpdateApp|An error has occurred while applying update package.

System.ArgumentException: Process with ID doesn’t exist 30447
at NzbDrone.Update.UpdateEngine.InstallUpdateService.Verify (System.String targetFolder, Int32 processId) [0x000c3] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\InstallUpdateService.cs:75
at NzbDrone.Update.UpdateEngine.InstallUpdateService.Start (System.String installationFolder, Int32 processId) [0x00000] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateEngine\InstallUpdateService.cs:79
at NzbDrone.Update.UpdateApp.Start (System.String[] args) [0x00020] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:59
at NzbDrone.Update.UpdateApp.Main (System.String[] args) [0x00042] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Update\UpdateApp.cs:43

That tells me that it IS mono, something changed in the mono 4.0 package, possibly in a change to mono itself, but something changed. There is a similar issue on other platforms, that we’re going to be looking into as well:


What I meant was that it cannot be Mono’s fault because the app runs, it’s the app that needs to be updated to work with the new version of Mono. Anyway, I don’t disagree that it’s Mono because obviously something has been changed, but the fact is that Mono has been updated and Sonarr is not updating on the new version. Any idea when a fix is coming? Thanks very much.

It’s September now and still having this issue. Won’t any of the developers care about us who are using QNAP? This sucks =/

I’m pleased to say that I asked QNAP_Stephane on the QNAP forums to compile the latest version of Mono as a qpkg and I’ve been running it for a couple of weeks and Sonarr now updates perfectly using this latest version.

I get the same error when trying to use the updater within sonarr, I confirmed with ps that 12107 is the correct process id.
15-11-2 19:33:19.1|Debug|ProcessProvider|Finding process with Id:12107
15-11-2 19:33:19.1|Warn|ProcessProvider|Unable to find process with ID 12107
15-11-2 19:33:19.1|Fatal|UpdateApp|An error has occurred while applying update package.

I installed the newer mono package and was able to get the updater to work
http://www.positiv-it.fr/QNAP/APP/Qmono_4.0.4.1_x86.qpkg.zip

This topic was automatically closed after 2 days. New replies are no longer allowed.