Jump to content


Photo

XPEnology Users Read Me

XPEnology ReadMe GettingStarted

  • Please log in to reply
122 replies to this topic

#21 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 03:45 AM

Posted 28 April 2017 - 03:19 PM

Hello @caralox

 

Thanks for getting in touch and sending the logs across, no problem with the English - understand you very well.

 

If I don't get a chance to look this evening, I will first thing tomorrow and get back to you with what we need to do, to get you up and running.

 

Best

- James



#22 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 03:45 AM

Posted 28 April 2017 - 03:29 PM

Hello Again @caralox

 

Ok, your system contains a 'Kentsfield' microprocessor, which is based on the Core Microarchitecture.
 
This processor supports : MMX, SSE, SSE2, SSE3, SSSE3.
 
So, that's why it's not working (see my opening post).
 
However, we do already have a package which should support your h/w.
 
If you take a look at this Wiki page - https://github.com/M...s-for-XPEnology, follow the instructions there and use the 'xpen-core2' alternate package architecture.
 
Let us know how you get on...
 
Best
- James

Edited by solabc16, 28 April 2017 - 03:29 PM.


#23 caralox OFFLINE  

caralox

    Newbie

  • Members
  • 2 posts

Posted 29 April 2017 - 06:24 AM

hello solabc16, 

 

i install the xpen-core2 package and it's works , i will never think this package were compatible with the xeon , thanks a lot i will now try your media server . thanks for the reactivity . 

 

 

have a nice day and thanks again 



#24 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 03:45 AM

Posted 29 April 2017 - 09:28 AM

Hello @caralox

 

You're welcome and thanks the update, glad to hear you've got everything up and running.

 

Enjoy!

 

Best

- James



#25 Firecatman OFFLINE  

Firecatman

    Newbie

  • Members
  • 6 posts
  • Local time: 08:45 PM

Posted 13 May 2017 - 06:36 PM

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.

 

Attached Files


Edited by Firecatman, 14 May 2017 - 11:35 AM.


#26 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 126928 posts
  • Local time: 10:45 PM

Posted 14 May 2017 - 12:12 AM

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/c...port-a-problem/

 

Thanks !



#27 Firecatman OFFLINE  

Firecatman

    Newbie

  • Members
  • 6 posts
  • Local time: 08:45 PM

Posted 14 May 2017 - 11:36 AM

Sorry about that @Luke

Updated post with log files



#28 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 03:45 AM

Posted 14 May 2017 - 12:52 PM

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



#29 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 03:45 AM

Posted 14 May 2017 - 12:58 PM

@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

Attached Files



#30 Firecatman OFFLINE  

Firecatman

    Newbie

  • Members
  • 6 posts
  • Local time: 08:45 PM

Posted 14 May 2017 - 01:13 PM

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



#31 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 126928 posts
  • Local time: 10:45 PM

Posted 14 May 2017 - 02:20 PM

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.



#32 Firecatman OFFLINE  

Firecatman

    Newbie

  • Members
  • 6 posts
  • Local time: 08:45 PM

Posted 14 May 2017 - 05:11 PM

Awesome that seems to have fixed it.

 

Thanks!



#33 chef OFFLINE  

chef

    Advanced Member

  • Developers
  • 3690 posts
  • Local time: 10:45 PM
  • LocationPeterborough, Canada

Posted 14 May 2017 - 11:04 PM

Is there a vera device on your network?

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

#34 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 126928 posts
  • Local time: 10:45 PM

Posted 15 May 2017 - 12:41 AM

@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.


  • chef likes this

#35 Firecatman OFFLINE  

Firecatman

    Newbie

  • Members
  • 6 posts
  • Local time: 08:45 PM

Posted 15 May 2017 - 11:51 PM

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.



#36 mattstrike OFFLINE  

mattstrike

    Newbie

  • Members
  • 3 posts
  • Local time: 02:45 AM

Posted 02 June 2017 - 08:29 PM

Hi,

 

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

 

What else do I need to do?

 

Thanks



#37 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 126928 posts
  • Local time: 10:45 PM

Posted 02 June 2017 - 10:28 PM

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?



#38 Huberer OFFLINE  

Huberer

    Advanced Member

  • Members
  • 30 posts
  • Local time: 03:45 AM

Posted 25 July 2017 - 07:31 AM

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, 25 July 2017 - 07:38 AM.


#39 liandenis OFFLINE  

liandenis

    Member

  • Members
  • 13 posts
  • Local time: 04:45 AM

Posted 04 September 2017 - 08:34 AM

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

Attached Files


Edited by liandenis, 04 September 2017 - 08:36 AM.


#40 solabc16 OFFLINE  

solabc16

    Advanced Member

  • ForumMod
  • 1967 posts
  • Local time: 03:45 AM

Posted 04 September 2017 - 09:03 AM

Hello @liandenis

 

Let's keep the conversation in one place, over here - https://emby.media/c...ersion-32260-1/.

 

Best

- James







Also tagged with one or more of these keywords: XPEnology, ReadMe, GettingStarted

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users