avalon65 2 Posted October 21, 2016 Share Posted October 21, 2016 Yesterday the emby plugin on my FreeNAS box worked as it should and played continuous music for a good hour or so. Today I wanted to play some music again using emby, but there was continuous error messages saying server couldn't be reached etc. So I checked my FreeNAS build to see what was happening, and emby was stopped! Also there was an update button next to it, so I updated emby, which seemed to take a while. Anyways, when it had finished updating, emby was still off. I started it again using this cmd ina shell 'service emby-server onestart', and it started. I then tried again to get the emby app on my tablet to load up the music files on my NAS box, but was still getting the same error. After checking emby on my FreeNAS box again, I saw that it was OFF yet again. Anyone know what is the cause or why it keeps stopping. Link to comment Share on other sites More sharing options...
avalon65 2 Posted October 22, 2016 Author Share Posted October 22, 2016 Emby server keeps stopping since it was updated on FreeNAS-9.10.1-U2 (f045a8b) Updated version of emby is 3.0.8300-amd64, and the previous version which was running ok as it should is 3.0.7200-amd64 root@emby_2:/ # service emby-server onestatus emby_server is not running. I have to start it back up again by: service emby-server onestart. Failing the above, I have not tried anything else as I don't know what to do about it I have attached a screenshot of the installed plugins web page. Link to comment Share on other sites More sharing options...
Luke 37112 Posted October 22, 2016 Share Posted October 22, 2016 Hi there, we're sorry to hear about this. In order to best help you, please provide the information requested in how to report a problem. Thanks ! Link to comment Share on other sites More sharing options...
Kezine 16 Posted November 12, 2016 Share Posted November 12, 2016 Hi, I have the issue for me. FreeNAS-9.10.1-U4Emby plugin version 3.0.8300.0Mono 4.4.2 (Stable 4.4.2.11/f72fe45 Mon Aug 22 04:48:30 UTC 2016) The Unhandled Error than made the server crash (The same every time) : Host is down System.Net.Sockets.SocketException at System.Net.Sockets.Socket.EndSend (IAsyncResult result) <0x810bf17c0 + 0x000b6> in <filename unknown>:0 at Rssdp.UdpSocket+<>c__DisplayClass4_0.<SendTo>b__0 (IAsyncResult result) <0x8118c7f90 + 0x00067> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x8181b7540 + 0x00038> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x8131b87c0 + 0x00118> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x8131b86f0 + 0x000b3> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x806edd290 + 0x00042> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () <0x806edd260 + 0x0001a> in <filename unknown>:0 at Rssdp.Infrastructure.SsdpCommunicationsServer+<SendMessageIfSocketNotDisposed>d__28.MoveNext () <0x8118c5fd0 + 0x002a1> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x8181b7540 + 0x00038> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x8131b87c0 + 0x00118> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x8131b86f0 + 0x000b3> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x806edd290 + 0x00042> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () <0x806edd260 + 0x0001a> in <filename unknown>:0 at Rssdp.Infrastructure.SsdpCommunicationsServer+<Repeat>d__29.MoveNext () <0x8118c4d60 + 0x002c6> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x8181b7540 + 0x00038> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x8131b87c0 + 0x00118> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x8131b86f0 + 0x000b3> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x806edd290 + 0x00042> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () <0x806edd260 + 0x0001a> in <filename unknown>:0 at Rssdp.Infrastructure.SsdpCommunicationsServer+<SendMessage>d__21.MoveNext () <0x8127eed80 + 0x004a9> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x8181b7540 + 0x00038> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x8131b87c0 + 0x00118> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x8131b86f0 + 0x000b3> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x806edd290 + 0x00042> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () <0x806edd260 + 0x0001a> in <filename unknown>:0 at Rssdp.Infrastructure.SsdpDevicePublisherBase+<SendSearchResponse>d__25.MoveNext () <0x8127ee240 + 0x00580> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x8181b7540 + 0x00038> in <filename unknown>:0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) <0x8217f1ae0 + 0x00044> in <filename unknown>:0 at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) <0x8044ebcb0 + 0x00050> in <filename unknown>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x8044e46e0 + 0x00233> in <filename unknown>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x8044e4380 + 0x00028> in <filename unknown>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x8044ebc40 + 0x00057> in <filename unknown>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x8044ea5c0 + 0x00222> in <filename unknown>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x8044ea4d0 + 0x00010> in <filename unknown>:0 FullLog.txt Link to comment Share on other sites More sharing options...
Luke 37112 Posted November 12, 2016 Share Posted November 12, 2016 Hi, please try updating to 3.0.8500. if it still persists it is definitely resolved for the next release. Thanks. Link to comment Share on other sites More sharing options...
Vidman 589 Posted November 12, 2016 Share Posted November 12, 2016 ..... When 3.0.8500 becomes available for freenas Link to comment Share on other sites More sharing options...
Kezine 16 Posted November 19, 2016 Share Posted November 19, 2016 Same issue with 3.0.8500. I have doubled the amout of ram for the system, but the isue is still there. Link to comment Share on other sites More sharing options...
MRobi 159 Posted November 26, 2016 Share Posted November 26, 2016 Having the same issue as well on 3.0.8500.0 Link to comment Share on other sites More sharing options...
Luke 37112 Posted November 26, 2016 Share Posted November 26, 2016 Ok thanks for the report guys. The above issue has been corrected for the next release of Emby Server. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now