Sonarr on Synology with Mono 3.10 won't stay running

Help & Support
1

Yesterday I upgraded Mono on my Synology to 3.10 and this broke Sonarr. I was using the dev branch. If you start Sonarr it stays running for only about 1-2 seconds, then stops. I tried uninstalling Sonarr und reinstalled it but without any luck.

Does anyone know what could be causing this?

Edit: Looking at the log it looks like an issue with the DB after reinstallation:

15-1-1 13:38:33.0|Info|Bootstrap|Starting NzbDrone - /volume1/@appstore/nzbdrone/share/NzbDrone/NzbDrone.exe - Version 2.0.0.2556
15-1-1 13:38:34.2|Debug|ProcessProvider|Found 0 processes with the name: NzbDrone.Console
15-1-1 13:38:34.3|Debug|ProcessProvider|Found 1 processes with the name: NzbDrone
15-1-1 13:38:34.8|Info|MigrationLogger|*** Migrating data source=/usr/local/nzbdrone/var/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True ***
15-1-1 13:38:34.8|Fatal|ConsoleApp|EPIC FAIL!

System.TypeInitializationException: An exception was thrown by the type initializer for System.Data.SQLite.SQLiteFactory ---> System.DllNotFoundException: libsqlite3.so.0
  at (wrapper managed-to-native) System.Data.SQLite.UnsafeNativeMethods:sqlite3_config_none (System.Data.SQLite.SQLiteConfigOpsEnum)
  at System.Data.SQLite.SQLite3.StaticIsInitialized () [0x00000] in <filename unknown>:0
  at System.Data.SQLite.SQLiteLog.Initialize () [0x00000] in <filename unknown>:0
  at System.Data.SQLite.SQLiteFactory..cctor () [0x00000] in <filename unknown>:0
  --- End of inner exception stack trace ---
  at NzbDrone.Core.Datastore.Migration.Framework.MigrationDbFactory.CreateFactory () [0x00000] in <filename unknown>:0
  at FluentMigrator.Runner.Processors.DbFactoryBase.get_Factory () [0x00000] in <filename unknown>:0
  at FluentMigrator.Runner.Processors.DbFactoryBase.CreateConnection (System.String connectionString) [0x00000] in <filename unknown>:0
  at NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSqliteProcessorFactory.Create (System.String connectionString, IAnnouncer announcer, IMigrationProcessorOptions options) [0x00000] in <filename unknown>:0
  at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.MigrateToLatest (System.String connectionString, MigrationType migrationType) [0x00000] in <filename unknown>:0
  at NzbDrone.Core.Datastore.DbFactory.Create (MigrationType migrationType) [0x00000] in <filename unknown>:0
  at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (IContainer container) [0x00000] in <filename unknown>:0
  at NzbDrone.Host.Bootstrap.Start (ApplicationModes applicationModes, NzbDrone.Common.EnvironmentInfo.StartupContext startupContext) [0x00000] in <filename unknown>:0
  at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, IUserAlert userAlert, System.Action`1 startCallback) [0x00000] in <filename unknown>:0
  at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00000] in <filename unknown>:0
2

You’ll need to get back onto the develop build since the database is incompatible.

If the UI is loading you can update from System: Update, if its not I would suggest backing up your database, removing the database so it is recreated, starting up, installing the latest develop build via System: Update then restoring the DB. The restore instructions are here to backup you will need to copy nzbdrone.db from that location first (before running the rm command).

3

The UI is not working. And I tried starting it without a DB which resulted in another error. But luckily a new package version was published today which installed just fine and started without the DB. I changed the branch to develop, stopped Sonarr and restored the DB from backup and then it finally worked.

4

Glad to hear its working.

Is that a new package in the syno community repo?

5

It looks like it. It says it is version 20150101-3. So from today I guess.