Package for NZBDrone [Request]

[evtk]

Hi there,

I don't know if it is even possible to request here, but I would really like to install NZBDrone as package on my synology NAS. Can this be added to the repository?

I read NZBDrone is build on mono, and I have seen an official synology mono package. But I'm no expert and would not know how to use this package to run NZBDrone.

Many thanks!

[Diaoul]

Well, if someone can make it work without a package to test that'd be great.

[evtk]

There is a debian package available:

https://github.com/NzbDrone/NzbDrone/wiki/Installation#linux

But I don't have a clue how to install it on synology.

[Nonobis]

Maybe ...

1 - download deb.
2 - Unzip it
3 - Copy content of folder "data\opt\NzbDrone" on your nas.
4 - run mono package on nas ..
5 - Make a script "mono [Your Path]/NzbDrone.exe"

i am at work so ... will try tonight.

[evtk]

just tried on my syno box... whoops:

DiskStation> mono /volume2/Downloads/NzbDrone/NzbDrone.exe
[Info] Bootstrap: Starting NzbDrone Console. Version 2.0.0.691
[Info] MigrationLogger: *** Migrating data source=/root/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal ***
[Info] MigrationLogger: *** VersionMigration migrating ***
[Fatal] ConsoleApp: EPIC FAIL!

System.EntryPointNotFoundException: sqlite3_column_database_name
at (wrapper managed-to-native) System.Data.SQLite.UnsafeNativeMethods:sqlite3_column_database_name (intptr,int)
at System.Data.SQLite.SQLite3.ColumnDatabaseName (System.Data.SQLite.SQLiteStatement stmt, Int32 index) [0x00000] in :0
at System.Data.SQLite.SQLiteDataReader.GetStatementColumnParents (System.Data.SQLite.SQLiteBase sql, System.Data.SQLite.SQLiteStatement stmt, Int32 fieldCount, System.Collections.Generic.Dictionary2& parentToColumns, System.Collections.Generic.Dictionary2& columnToParent) [0x00000] in :0
at System.Data.SQLite.SQLiteDataReader.GetSchemaTable (Boolean wantUniqueInfo, Boolean wantDefaultValue) [0x00000] in :0
at System.Data.SQLite.SQLiteDataReader.GetSchemaTable () [0x00000] in :0
at System.Data.Common.DataAdapter.BuildSchema (IDataReader reader, System.Data.DataTable table, SchemaType schemaType, MissingSchemaAction missingSchAction, MissingMappingAction missingMapAction, System.Data.Common.DataTableMappingCollection dtMapping) [0x00000] in :0
at System.Data.Common.DataAdapter.BuildSchema (IDataReader reader, System.Data.DataTable table, SchemaType schemaType) [0x00000] in :0
at System.Data.Common.DataAdapter.FillTable (System.Data.DataTable dataTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords, System.Int32& counter) [0x00000] in :0
at System.Data.Common.DataAdapter.FillInternal (System.Data.DataSet dataSet, System.String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) [0x00000] in :0
at System.Data.Common.DataAdapter.Fill (System.Data.DataSet dataSet, System.String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) [0x00000] in :0
at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet, Int32 startRecord, Int32 maxRecords, System.String srcTable, IDbCommand command, CommandBehavior behavior) [0x00000] in :0
at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet) [0x00000] in :0
at FluentMigrator.Runner.Processors.Sqlite.SqliteProcessor.Read (System.String template, System.Object[] args) [0x00000] in :0
at FluentMigrator.Runner.Processors.Sqlite.SqliteProcessor.ColumnExists (System.String schemaName, System.String tableName, System.String columnName) [0x00000] in :0
at FluentMigrator.Runner.VersionLoader.get_AlreadyMadeVersionUnique () [0x00000] in :0
at FluentMigrator.Runner.VersionLoader.LoadVersionInfo () [0x00000] in :0
at FluentMigrator.Runner.VersionLoader..ctor (IMigrationRunner runner, System.Reflection.Assembly assembly, IMigrationConventions conventions) [0x00000] in :0
at FluentMigrator.Runner.MigrationRunner..ctor (System.Reflection.Assembly assembly, IRunnerContext runnerContext, IMigrationProcessor processor) [0x00000] in :0
at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.MigrateToLatest (System.String connectionString, MigrationType migrationType) [0x00000] in :0
at NzbDrone.Core.Datastore.DbFactory.Create (MigrationType migrationType) [0x00000] in :0
at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (IContainer container) [0x00000] in :0
at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupArguments args, IUserAlert userAlert) [0x00000] in :0
at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x00000] in :0

[Nonobis]

make a report on their issue tracker maybe they could patch the soft.

[evtk]

I have done so:

http://forums.nzbdrone.com/discussion/588/nzbdrone-as-synology-package

Let's see what happens!

[Diaoul]

Open a ticket to Synology and have them to update sqlite. Seems there's no other way unless recompile mono with our sqlite.
I'd like to avoid recompile every package Synology can't compile properly...

[evtk]

Allright, thanks. I will contact synology and post any results here.

[evtk]

this is the answer on updating sqlite.

Unfortunately there is no announced plan to support this feature at the moment. I apologize for your inconvenience. However, I have passed this message to our developers and product management group. They will have more research on such feature. Thank you for bringing this issue to our attention.

[Diaoul]

That's the reason we build our own packages, if something needs an update we update it.
So it seems the solution is to build mono from scratch using spksrc. If someone's up to it let me know.

[Senaxx]

I want to kick a bit of life in this issue. It seems that sql lite 3 has been updated by Synology on the DSM software, so i'm curious to see ift it would be able to get working now?

NAS> sqlite3
SQLite version 3.8.1 2013-10-17 12:57:35

Currently with latest sqlite installed still the same error :(

[maxrogers]

@Diaoul does having SQLite version 3.8.1 2013-10-17 make this package a real possibility now? I would be happy to test a package out. Thanks for your help!

[danfozzy]

is there any word if this will now be possible with this new version of SQlite?

[kevinmce]

Ive just tried while running DSM 5 and ive gotten something similar

Tried with available libs below and added the OSX one for a laugh, still no joy.
libsqlite3.0.dylib
libsqlite3.so
libsqlite3.so.0
libsqlite3.so.0.8.6

/volume1/@appstore/NzbDrone> mono --debug NzbDrone.exe
[Info] Bootstrap: Starting NzbDrone Console. Version 2.0.0.1181
[Info] ps: Starting ps -p 21113 -o args=
[Error] ps: /bin/ps: invalid option -- 'p'
[Error] ps: BusyBox v1.16.1 (2014-01-20 02:24:47 CST) multi-call binary.
[Error] ps: Usage: ps
[Error] ps: Report process status
[Error] ps: Options:
[Error] ps: w Wide output
[Info] MigrationLogger: *** Migrating data source=/root/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal ***
[Info] MigrationLogger: *** VersionMigration migrating ***

[Fatal] ConsoleApp: EPIC FAIL!

System.EntryPointNotFoundException: sqlite3_column_database_name
at (wrapper managed-to-native) System.Data.SQLite.UnsafeNativeMethods:sqlite3_column_database_name (intptr,int)
at System.Data.SQLite.SQLite3.ColumnDatabaseName (System.Data.SQLite.SQLiteStatement stmt, Int32 index) [0x00000] in :0
at System.Data.SQLite.SQLiteDataReader.GetStatementColumnParents (System.Data.SQLite.SQLiteBase sql, System.Data.SQLite.SQLiteStatement stmt, Int32 fieldCount, System.Collections.Generic.Dictionary2& parentToColumns, System.Collections.Generic.Dictionary2& columnToParent) [0x00000] in :0
at System.Data.SQLite.SQLiteDataReader.GetSchemaTable (Boolean wantUniqueInfo, Boolean wantDefaultValue) [0x00000] in :0
at System.Data.SQLite.SQLiteDataReader.GetSchemaTable () [0x00000] in :0
at System.Data.Common.DataAdapter.BuildSchema (IDataReader reader, System.Data.DataTable table, SchemaType schemaType, MissingSchemaAction missingSchAction, MissingMappingAction missingMapAction, System.Data.Common.DataTableMappingCollection dtMapping) [0x0003b] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DataAdapter.cs:284
at System.Data.Common.DataAdapter.BuildSchema (IDataReader reader, System.Data.DataTable table, SchemaType schemaType) [0x00000] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DataAdapter.cs:257
at System.Data.Common.DataAdapter.FillTable (System.Data.DataTable dataTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords, System.Int32& counter) [0x00011] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DataAdapter.cs:428
at System.Data.Common.DataAdapter.FillInternal (System.Data.DataSet dataSet, System.String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) [0x0009b] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DataAdapter.cs:533
at System.Data.Common.DataAdapter.Fill (System.Data.DataSet dataSet, System.String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) [0x00000] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DataAdapter.cs:589
at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet, Int32 startRecord, Int32 maxRecords, System.String srcTable, IDbCommand command, CommandBehavior behavior) [0x0004e] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DbDataAdapter.cs:337
at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet) [0x00000] in /source/Mono/src/mcs/class/System.Data/System.Data.Common/DbDataAdapter.cs:265
at FluentMigrator.Runner.Processors.Sqlite.SqliteProcessor.Read (System.String template, System.Object[] args) [0x00032] in c:\Community\tommarien\fluentmigrator\src\FluentMigrator.Runner\Processors\Sqlite\SqliteProcessor.cs:197
at FluentMigrator.Runner.Processors.Sqlite.SqliteProcessor.ColumnExists (System.String schemaName, System.String tableName, System.String columnName) [0x00000] in c:\Community\tommarien\fluentmigrator\src\FluentMigrator.Runner\Processors\Sqlite\SqliteProcessor.cs:52
at FluentMigrator.Runner.VersionLoader.get_AlreadyMadeVersionUnique () [0x00000] in c:\Community\tommarien\fluentmigrator\src\FluentMigrator.Runner\VersionLoader.cs:109
at FluentMigrator.Runner.VersionLoader.LoadVersionInfo () [0x00050] in c:\Community\tommarien\fluentmigrator\src\FluentMigrator.Runner\VersionLoader.cs:127
at FluentMigrator.Runner.VersionLoader..ctor (IMigrationRunner runner, System.Reflection.Assembly assembly, IMigrationConventions conventions) [0x00066] in c:\Community\tommarien\fluentmigrator\src\FluentMigrator.Runner\VersionLoader.cs:40
at FluentMigrator.Runner.MigrationRunner..ctor (System.Reflection.Assembly assembly, IRunnerContext runnerContext, IMigrationProcessor processor) [0x000d6] in c:\Community\tommarien\fluentmigrator\src\FluentMigrator.Runner\MigrationRunner.cs:86
at NzbDrone.Core.Datastore.Migration.Framework.MigrationController.MigrateToLatest (System.String connectionString, MigrationType migrationType) [0x000c4] in m:\BuildAgent1\work\328d72309b633a8\src\NzbDrone.Core\Datastore\Migration\Framework\MigrationController.cs:53
at NzbDrone.Core.Datastore.DbFactory.Create (MigrationType migrationType) [0x00049] in m:\BuildAgent1\work\328d72309b633a8\src\NzbDrone.Core\Datastore\DbFactory.cs:74
at NzbDrone.Core.Datastore.DbFactory.RegisterDatabase (IContainer container) [0x00000] in m:\BuildAgent1\work\328d72309b633a8\src\NzbDrone.Core\Datastore\DbFactory.cs:32
at NzbDrone.Host.Bootstrap.Start (ApplicationModes applicationModes, NzbDrone.Common.EnvironmentInfo.StartupContext startupContext) [0x00012] in m:\BuildAgent1\work\328d72309b633a8\src\NzbDrone.Host\Bootstrap.cs:65
at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext startupContext, IUserAlert userAlert, System.Action`1 startCallback) [0x00064] in m:\BuildAgent1\work\328d72309b633a8\src\NzbDrone.Host\Bootstrap.cs:39
at NzbDrone.Console.ConsoleApp.Main (System.String[] args) [0x0000f] in m:\BuildAgent1\work\328d72309b633a8\src\NzbDrone.Console\ConsoleApp.cs:19

Press any key to exit...

[maxrogers]

@kevinmce, you got me motivated, so I installed Synology DMS 5.0 in a virtual machine (vmware) and gave it a go also. I am now stuck at the exact same error as you (above:)

System.EntryPointNotFoundException: sqlite3_column_database_name

I am willing to try whatever on this test (virtual machine) so if anyone has any ideas. Throw them at me!

My sqlite version on DSM 5.0beta:
DStest> sqlite3
SQLite version 3.8.0.2 2013-09-03 17:11:13

Mono info:
DStest> mono -V
Mono JIT compiler version 2.11.1 ((no/426188e Mon Jan 13 12:11:24 CST 2014)

Mediainfo:
DStest> mediainfo --version
MediaInfo Command line,
MediaInfoLib - v0.7.61

[maxrogers]

If you don't want to test on your live Synology box like me, I posted a method for setting up a virtual DSM 5.0 here:

http://forums.nzbdrone.com/discussion/comment/3758#Comment_3758

[kevinmce]

Humm, ive been looking up the virtual machine also yesterday. It makes me wonder was buying the synology really worth the 550 euro. I could have built a home server for a lot less.

I think requesting support from the synocommunity guys would help. They should be familiar with the issues when creating these packages.

[maxrogers]

So here is what I have been able to figure out.

It seems that sqlite defaults to not include/enable the column metadata function when compiled. This means that, the sqlite on the synology doesn't include that function. Hence the error we are getting:

System.EntryPointNotFoundException: sqlite3_column_database_name

So..... this means that we either need to get synology to update sqlite on DSM5.0 to include the column_metadata function when compiled or we compile sqlite ourselves with the function. As near as I can figure, adding this flag will compile with the needed feature:

CPPFLAGS="-D SQLITE_ENABLE_COLUMN_METADATA"

I have been trying to compile a version myself but I don't know what I am doing (never really done this before.) You can cross-compile for synology on linux. Here is what I have been trying to follow to do it:

http://usdl.synology.com/download/ds/userguide/Synology_DiskStation_Manager_3rd_Party_Apps_Developer_Guide.pdf

Anyways, I am out of my depth here.....

[maxrogers]

See this comment here: https://bugzilla.xamarin.com/show_bug.cgi?id=327#c4
(where I found the info about sqlite not compiling with that feature.)

Edit: from sqlite: http://www.sqlite.org/c3ref/column_database_name.html

"These APIs are only available if the library was compiled with the SQLITE_ENABLE_COLUMN_METADATA C-preprocessor symbol."

const char sqlite3_column_database_name(sqlite3_stmt,int);
const void sqlite3_column_database_name16(sqlite3_stmt,int);
const char sqlite3_column_table_name(sqlite3_stmt,int);
const void sqlite3_column_table_name16(sqlite3_stmt,int);
const char sqlite3_column_origin_name(sqlite3_stmt,int);
const void sqlite3_column_origin_name16(sqlite3_stmt,int);

[kevinmce]

Nice find Max!

One step closer!(fingers crossed)
I unfortunately know probably less about compiling than you.

Ill look into it also, but just reading the first bit and im lost.

Edit:
Requested some help over at the synology fourms: http://forum.synology.com/enu/viewtopic.php?f=27&t=75217&p=284643&hilit=nzbdrone#p284643

[kevinmce]

Would another option be to use an updated version of mono?
Since the version of mono we are using(2.11) pre-dates the fix that is mentioned here: https://bugzilla.xamarin.com/show_bug.cgi?id=327

Just found this guide to compile it for synology... maybe its an easier path than compiling SQlite
http://blog.hexad.dk/2013/11/mono-323-on-synology-ds210.html

[Diaoul]

SQlit is the easy part. Recompiling mono is a tough task but is the solution so we don't depend on some Synology package.

[kevinmce]

Indeed, compiling mono is going to be difficult. I didnt get past the configure command(./configure --prefix=/opt/mono-3.2.3)

Fails when testing the compiler:
checking whether the C compiler works... no
configure: error: in `/volume1/@appstore/mono-3.2.3':
configure: error: C compiler cannot create executables

[Senaxx]

I'd love to get this running but we definitly need someone with some more (compiling) knowledge. I've tried to compile the new mono but also failed :( Someone posted a guide howto compile mono on a Synology DS210 @ http://blog.hexad.dk/2013/11/mono-323-on-synology-ds210.html

[kevinmce]

Ive goten further in compiling mono.... but now the next problem.

Anyone able to help diagnose the AWK command problem?

config.status: executing default commands
awk: cmd. line:3: Unexpected token

    mcs source:    mcs

Engine:
GC: sgen and bundled Boehm GC with typed GC and parallel mark
TLS: pthread
SIGALTSTACK: no
Engine: Building and using the JIT
oprofile: no
BigArrays: no
DTrace: no
LLVM Back End: no (dynamically loaded: no)

Libraries:
.NET 2.0/3.5: yes
.NET 4.0: yes
.NET 4.5: yes
MonoDroid: no
MonoTouch: no
JNI support: IKVM Native
libgdiplus: assumed to be installed
zlib:

[Diaoul]

Don't compile on the NAS itself, that's unusable for packaging. Use spksrc instead.

[kevinmce]

I have not tried a VM / Debian OS. i thought that the NAS unix should be able to do that?

Its already been WAY more time/effort that i expected. Since ive started as a person with no unix knowledge, only some DOS/command prompt memories from way back when.

I may try gettingspkscr going. Will see.

[maxrogers]

Edit: I posted an error that I was working to resolve but then found that it may be a result of my using a 64 bit Debian install (instead of the recommended 32 bit.) I will report back with the error if it happens on 32 bit also. Thanks

[Diaoul]

Awesome 🎉
@maxrogers Once the new spkrepo version will be in production I'll give you permission to publish updates to mono and sonarr. This should happen this month.

[Stanzilla]

@Dr-Bean Looks like the icon is missing though: http://i.imgur.com/ktjDaEM.png

[maxrogers]

@Dr-Bean Thanks!

@Diaoul, that will be so awesome! 👍 Let me know

@Stanzilla, good catch! Fixed here: #1422

[SpiderDice]

I'm on Sonarr Ver. 2.0.0.2594 and all of my shows are displaying an air time of 12:00am. Anyone else seeing this?

[derik0709]

@SpiderDice Yeah, it is because Sonarr switched to using theTVDB instead of Trakt. theTVDB doesn't have air times for shows. Everything else that has changed is explained here https://forums.sonarr.tv/t/sonarr-now-with-tvdb/3314

[SpiderDice]

@derik0709 Ahh..okay. Guess it's not that big of a deal since it's still picking up showing when they are released.

[schumi2004]

I thought I saw a list of architectures mono is working for in the past but can't seem to find it. What is current status for Sonarr + Mono, what architectures are excluded?

[maxrogers]

@schumi2004, the architectures not on this list:
bromolow cedarview evansport x86 armada370 88f6281 armadaxp comcerto2k avoton armada375 alpine x64

[schumi2004]

This is the working list right? (got confused since my arch is in the list and i mentioned excluded so not sure if you mean working or not ;) )

[maxrogers]

@schumi2004, correct. It is the current working list. The architectures not mentioned are not compatible.

[SickPotato]

Can someone update the Synology Mono package to 3.12.0?

''Mono 3.12.0 is the result of about 3 months of work, featuring over 600 commits and 68 fixes. It was the work of 70 contributors.''

http://www.mono-project.com/docs/about-mono/releases/3.12.0/

[markus101]

At this point I'd recommend sticking with 3.10, 3.12 introduced an bug that prevented Sonarr from starting up properly. We have implemented a workaround, but recommend erring on the side of caution.

[maxrogers]

@SickPotato @markus101, I will update the Mono package as soon as the outstanding 3.12 bug is resolved with a new release.

[Diaoul]

@maxrogers: do you think sonarr can hit the repo (non-beta)?

[maxrogers]

@Diaoul, absolutely! Should I go ahead and remove the beta flag?

[maxrogers]

Also mono I would think?

[Diaoul]

Yes, both. However I have a problem when cross compiling mono:

install -m 755 -d /spksrc/spk/mono/work-armadaxp-5.1/staging/lib
tar -cpf - -C /spksrc/spk/mono/work-armadaxp-5.1/../../../native/mono/work-native/install/usr/local/lib . | tar -xpkf - -C /spksrc/spk/mono/work-armadaxp-5.1/staging/lib
tar: ./libmonoboehm-2.0.a: Cannot open: File exists

Do you have this issue? If possible I'd like to put latest Mono online.

[Taloth]

Just a heads up, be careful which mono version you put as non-beta, there have been some unstable ones. atm we have 3.10 as stable, coz there seems to be a problem on some OS with 3.12, nothing concrete, just random reports.

[Dr-Bean]

I suppose that we could release mono3.10 as-is as a stable package, and put up a beta mono3.12 on the repository (might be helpful from a troubleshooting pov?)

[Diaoul]

OK so 3.10 as stable and 3.12 as beta.

[Taloth]

Sounds good. That way some daredevils can run 3.12 and see if it's stable. We had problems with it on atleast OSX.

If you compile 3.10 and 3.12 straight from their respective branches in the mono repo it will include some security vulnerabilities.

Ref: http://www.mono-project.com/news/2015/03/07/mono-tls-vulnerability/

[maxrogers]

Here are the pull requests with beta flags removed. I also removed that redundancy in spk/mono/Makefile

Mono: #1605
Sonarr: #1606

[danfozzy]

Looking at replacing my ds212+ with the new ds715. Is it to early to say if these packages will be supported on there, as I know some archs aren't able to run certain apps.

it's running on a Alpine AL-314

[Diaoul]

Too early to say. Please follow #1703

[fredguy]

Hi guys,
Wondering if you could share with me the following.
Sonarr tends to crash from time to time. So i'm triggering an alert with monit.
Best would be to restrat the service when necessary, but i couldn't figure out the proper start command line.
/usr/local/mono/bin/mono --debug /usr/local/nzbdrone/share/NzbDrone/NzbDrone.exe => failed
/var/packages/nzbdrone/scripts/start-stop-status start => failed.

I guess i'm missing some ENV details but can't figure them out. Any help appreciated.
I'm on DSM5 (not planing to migrate jst yet coz Zarafa is running)
Cheers.

[Dr-Bean]

@fredguy Please ask your question in a new issue. Take a look at the guidelines too: https://github.com/SynoCommunity/spksrc/blob/master/CONTRIBUTING.md#issues.

For new readers, I've reported this before: This issue is closed, and questions should be reported in a new issue.
To prevent new comments from being made, I'm locking the conversation: this issue is too large and too many people will be pinged when comments are made.