Jump to content
solabc16

XPEnology Users Read Me

Recommended Posts

Luke

Hi,

 

Been trying to get Emby to work on my new xpenology box with an Intel Pentium G4560. I can get it to install and am able to get it running long enough to setup everything then the Emby server stops and I can't get it to start again. Tried restarting synology and server still doesn't start. If I reinstall Emby it will do the same thing. Ran diagnostics and sent logs.

 

hi @@Firecatman, can you please attach your emby server log to this post? you can learn how to do that here:

 

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks !

Share this post


Link to post
Share on other sites
Firecatman

Sorry about that @@Luke

Updated post with log files

Share this post


Link to post
Share on other sites
solabc16

Hello @@Firecatman

 

Can you confirm this is your log reference, this will contain every I need to troubleshoot: sendlogs_Tanner_NAS_synology_bromolow_3615xs_20170514T153324UTC

 

Best

- James

Share this post


Link to post
Share on other sites
solabc16

@@Luke - this one doesn't look like a CPU architecture issue, which is normally what we have to address when Emby Server doesn't run properly on XPEnology.

 

See attached.

System.NullReferenceException: Object reference not set to an instance of an object
  at MiOSEmbyZWaveControllerCS.ServerEntryPoint+<GetVeraDeviceIp>d__d.MoveNext () [0x0016d] in <20c1d9349ce549d48bcb36b61fb4445b>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at MiOSEmbyZWaveControllerCS.ServerEntryPoint+<PluginThread>d__5.MoveNext () [0x0012f] in <20c1d9349ce549d48bcb36b61fb4445b>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
System.NullReferenceException
  at MiOSEmbyZWaveControllerCS.ServerEntryPoint+<GetVeraDeviceIp>d__d.MoveNext () [0x0016d] in <20c1d9349ce549d48bcb36b61fb4445b>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at MiOSEmbyZWaveControllerCS.ServerEntryPoint+<PluginThread>d__5.MoveNext () [0x0012f] in <20c1d9349ce549d48bcb36b61fb4445b>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 

Best

- James

server-63630315151.txt

unhandled_29e86381-1288-4dd2-af69-bc9a6b05521b.txt

embysvr-stdout.txt

Share this post


Link to post
Share on other sites
Firecatman

Hello @@Firecatman

 

Can you confirm this is your log reference, this will contain every I need to troubleshoot: sendlogs_Tanner_NAS_synology_bromolow_3615xs_20170514T153324UTC

 

Best

- James

 

Yes it is

Share this post


Link to post
Share on other sites
Luke

This is coming from the vera community plugin, or zwave. Recall that when you first installed the plugin, you agreed that it might result in decreased stability. Please shutdown Emby Server, and go to:

/var/packages/EmbyServer/target/var/plugins

Then manually delete the .dll files for these plugins. @@chef, I will need to pull this plugin from the catalog again. 

 

Thanks.

Share this post


Link to post
Share on other sites
Firecatman

Awesome that seems to have fixed it.

 

Thanks!

Share this post


Link to post
Share on other sites
chef

Is there a vera device on your network?

 

I would want to find out why the entry point is tanking emby.

Share this post


Link to post
Share on other sites
Luke

@@chef you can also make sure that whoever is calling GetVeraDeviceIp wraps it with try/catch. that way the failure will be printed to the log instead of crashing the server.

  • Like 1

Share this post


Link to post
Share on other sites
Firecatman

Is there a vera device on your network?

 

I would want to find out why the entry point is tanking emby.

 

No there was not.

Share this post


Link to post
Share on other sites
mattstrike

Hi,

 

I've ran and sent the diagnostics ref sendlogs_DiskStation_synology_bromolow_3615xs_20170603T002218UTC.tgz

 

What else do I need to do?

 

Thanks

Share this post


Link to post
Share on other sites
Luke

Hi,

 

I've ran and sent the diagnostics ref sendlogs_DiskStation_synology_bromolow_3615xs_20170603T002218UTC.tgz

 

What else do I need to do?

 

Thanks

 

@@mattstrike what problem are you having?

Share this post


Link to post
Share on other sites
Huberer

Hello,

 

I'm running DSM (latest 6.1.3-xx) in a virtual machine (xpenology on Virtualbox) with DS916+ settings on my server (see sig.). I've added the url from the first page to the package source but Emby doesn't show up to install.

I've also tried to use the "original" link from the download part of the emby homepage for an original Synolgoy-NAS and this works without any problems. Now I will stay with that but why it doesn't show up for an xpenology version?

 

Forget this question because I didn't read till the end of the first post here. So I will stay with the original Synology-package because my server has a haswell cpu and as long the original version is working I don't care.

 

Thanks anyway

Edited by Huberer

Share this post


Link to post
Share on other sites
liandenis

Hello,

 

my Emby Server don't want to run.

 

Here are my requirements:

 

1. 4 CPUs x Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz

2. DS3617xs (virtual)
3. DSM Version: DSM 6.1.3-15152 Update 3
4. Emby Server Version: 3.2.30.0-1
5. Open VM TOOLS: open-vm-tools_bromolow-6.0_10.0.7-1.spk
 
My logs I have attached.
 
I hope sombody can help me, or i'll go crazy :wacko:
 
Thanks a lot!!!!
 
greets,
 
Liandenis

DS Diagnostic.txt

DS Support Logs.txt

Edited by liandenis

Share this post


Link to post
Share on other sites
solabc16

Hello All

 

Emby Server is now fully support on XPEnology systems that are based on the newer Synology DS3617xs, see the link above if you want more details.

 

We've also added an optimised build for systems based on Intel's 'westmere' microarchitecture, see https://github.com/MediaBrowser/Wiki/wiki/Synology-:-Custom-Package-Architectures-for-XPEnology.

 

Let us know how you get on...

 

Best

- James

Edited by solabc16

Share this post


Link to post
Share on other sites
solabc16

Hello All

 

A quick note for those of you running systems based on AMD processors, you should consider using the following URL when adding Emby to Package Center:-

https://synology.emby.media/?package_repository=360efc6e-de72-4073-b603-2bfbd7001586&package_architecture=xpen-barcelona

Although it might seem to work ok, running the Intel packages on AMD h/w may be the cause of subtle errors and/or occasional crashes. (e.g. https://emby.media/community/index.php?/topic/50599-emby-not-scraping-images/)

 

If you have newer AMD h/w and would like an optimised build for your h/w, just shout here!

 

Best

- James

Share this post


Link to post
Share on other sites
memetopal

Hi!

First i would like to say thank you to everyone involved in developing Emby for Synology and Xpenology.

 

I have an Xpenology with an Intel Core 2 Quad Q9400 @2.66 Ghz. Is there any package already developed for this architecture? Should i use xpen-core2-sse41 maybe?

 

Thanks in advance

Share this post


Link to post
Share on other sites
solabc16

Hello @@memetopal

 

Thanks for the feedback, the Intel Q9400 is a Yorkfield-6M variant and supports SSE4.1.

 

So you are correct, the xpen-core2-sse41 package would be optimal for your h/w.

 

Best

- James

Share this post


Link to post
Share on other sites
memetopal

Hello @@memetopal

 

Thanks for the feedback, the Intel Q9400 is a Yorkfield-6M variant and supports SSE4.1.

 

So you are correct, the xpen-core2-sse41 package would be optimal for your h/w.

 

Best

- James

 

Thanks! Already installed it and working great so far.

Share this post


Link to post
Share on other sites
mixedd

What about a older hardware and CPU support!

I run xpenology 6.1 on and scraped Intel Atom D525 based small home NAS!

Can i somehow install and use Emby server here too???

Share this post


Link to post
Share on other sites
solabc16

Hello @@mixedd

 

A good question and the short answer is yes. We're just working through getting the 3.2.32.0 release out, then I'll give this some attention.

 

Best

- James

Edited by solabc16

Share this post


Link to post
Share on other sites
ultimatevc
Good afternoon everyone.

 

thanks to you I am learning a lot these days. I have mounted a NAS with Xpenology 6.0 and I have installed Emby from the repository  "https://synology.emby.media/?package_repository=360efc6e-de72-4073-b603-2bfbd7001586&package_architecture=xpen-barcelona"   but when I run Emby, it shows me an error "The service could not be executed".

 

I have an "ASUS E35M1-I DELUXE" base station with cpu "Fusion APU E-350 Dual-Core Processors" and chipset "AMD® FCH A50 (Hudson M1)".

 

Do you think Emby can not work on my computer?

Thank you very much!

Edited by ultimatevc

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...