Latest update on Qnap fails

v3 Testing
#1

Sonarr version (exact version): 3.0.0.266
Mono version (if Sonarr is not running on Windows): 5.14.0.177
OS: QNap v4.3.5.0756 (10.11.2018)
Description of issue: Sonarr fail updating to latest version 3.0.0.276

Error occurred while executing task ApplicationUpdate: ApplicationName='mono', CommandLine='--debug /share/CACHEDEV1_DATA/SONARR3_CONFIG/sonarr_update/Sonarr.Update.exe 6003 /share/CACHEDEV1_DATA/SONARR3_CONFIG/sonarr_update /share/CACHEDEV1_DATA/.qpkg/QSonarr3/Sonarr/Sonarr.exe /data=/share/CACHEDEV1_DATA/SONARR3_CONFIG', CurrentDirectory='', Native error= Cannot find the specified file

[v3.0.0.266] System.ComponentModel.Win32Exception (0x80004005): ApplicationName='mono', CommandLine='--debug /share/CACHEDEV1_DATA/SONARR3_CONFIG/sonarr_update/Sonarr.Update.exe 4265 /share/CACHEDEV1_DATA/SONARR3_CONFIG/sonarr_update /share/CACHEDEV1_DATA/.qpkg/QSonarr3/Sonarr/Sonarr.exe /data=/share/CACHEDEV1_DATA/SONARR3_CONFIG', CurrentDirectory='', Native error= Cannot find the specified file at System.Diagnostics.Process.StartWithCreateProcess (System.Diagnostics.ProcessStartInfo startInfo) [0x002dc] in <d7a7557bf4f2450984171b394b83a8c0>:0 at System.Diagnostics.Process.Start () [0x0003a] in <d7a7557bf4f2450984171b394b83a8c0>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start() at NzbDrone.Common.Processes.ProcessProvider.Start (System.String path, System.String args, System.Collections.Specialized.StringDictionary environmentVariables, System.Action`1[T] onOutputDataReceived, System.Action`1[T] onErrorDataReceived) [0x00194] in <ddf4e38ed0f44e39a036ba487aa47543>:0 at NzbDrone.Core.Update.InstallUpdateService.InstallUpdate (NzbDrone.Core.Update.UpdatePackage updatePackage) [0x00242] in <3645c133ddd64d9db92f442f3ae90c39>:0 at NzbDrone.Core.Update.InstallUpdateService.Execute (NzbDrone.Core.Update.Commands.ApplicationUpdateCommand message) [0x0006e] in <3645c133ddd64d9db92f442f3ae90c39>:0 at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommand[TCommand] (TCommand command, NzbDrone.Core.Messaging.Commands.CommandModel commandModel) [0x000f6] in <3645c133ddd64d9db92f442f3ae90c39>:0 at (wrapper dynamic-method) System.Object.CallSite.Target(System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,NzbDrone.Core.Messaging.Commands.CommandExecutor,object,NzbDrone.Core.Messaging.Commands.CommandModel) at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2] (System.Runtime.CompilerServices.CallSite site, T0 arg0, T1 arg1, T2 arg2) [0x00110] in <d75ac642318f4f519ab42dbd5a3732c5>:0 at (wrapper dynamic-method) System.Object.CallSite.Target(System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,NzbDrone.Core.Messaging.Commands.CommandExecutor,object,NzbDrone.Core.Messaging.Commands.CommandModel) at NzbDrone.Core.Messaging.Commands.CommandExecutor.ExecuteCommands () [0x0008c] in <3645c133ddd64d9db92f442f3ae90c39>:0 18-11-12 20:16:23.0|Debug|Api|[GET] /api/v3/log?page=1&pageSize=50&sortDirection=descending&sortKey=time: 200.OK (87 ms) 18-11-12 20:17:10.0|Debug|Api|[GET] /api/v3/log/file: 200.OK (10 ms)
#2

Looks like a configuration issue with your system, Sonarr can’t find mono to run the updater.

#3

I assume that the problem is because I have not started v3 from scratch.
I have copied config.xml and db from v2 to v3.
Which means that I have renamed nzbdrone.db to sonarr.db

#4

No, it has nothing to do with that, it has to do with mono not being available without the full path because it’s not in the PATH environment variable.

#5

That is strange. If mono would not work than whole Sonarr should not work.
We have a problem only with the update.
I have deleted Sonarr package and downloaded the latest version from Qnapclub.
Then I have moved backup from v2 to v3 config folder and performed restore.
I have checked PATH on Qnap and added also the path for mono.
Will see if next update will go without problem or not.

#6

Same for me all works OK, on QNAP NAS restart mono sometimes starts after Sonarr and you get that error, but that simply is fixed with Sonarr Stop -> Wait 1 min -> Start.

#7

Qnap is a bit rotten when it comes to starting its packages. Get SortMyQPKGs it will force packages to start in a better order so mono will start before Sonarr

1 Like
#8

You can run it via the full path though, which may be what the startup script for the package is doing.

mono isn’t a service, it doesn’t start before Sonarr, Sonarr runs under mono.

#9

I have a long time ago solved problem loading mono before sonarr. Simple rearrange in /etc/config/qpkg.conf solved that problem.
To clarify. I do not have a problem with the sonarr itself. It works perfectly.
No problem with v2 nor v3.
The only problem is by updating the v3 sonarr to the latest version through the sonarr web interface - system/updates/install latest.
Update in v2 works fine. At least for the last time, it was fine.
The only difference is updated mono to the latest version. Maybe is there an issue with latest mono version.
I will see if the update will work when next update for v2 or v3 arrive.

#10

I am seeing the same issue when trying to update through the GUI with the “Install Latest” button.

I have used SortMyQPKGs and it is a fresh V3 install and still getting the same issue

[v3.0.0.273] System.ComponentModel.Win32Exception (0x80004005): ApplicationName=‘mono’, CommandLine=’–debug /share/CACHEDEV1_DATA/SONARR3_CONFIG/tmp/sonarr_update/Sonarr.Update.exe 27431 /share/CACHEDEV1_DATA/SONARR3_CONFIG/tmp/sonarr_update /share/CACHEDEV1_DATA/.qpkg/QSonarr3/Sonarr/Sonarr.exe /data=/share/CACHEDEV1_DATA/SONARR3_CONFIG’, CurrentDirectory=’’, Native error= Cannot find the specified file

#11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.