matt77303 1 Posted January 17, 2018 Posted January 17, 2018 Hi The last couple of weeks Ive noticed emby server crashing when I go to use it on kodi. I have emby server Version 3.2.60.0 running on omv 3.0.96, there are no updates pending so everything is up to date. When emby crashes it is not contactable via kodi, the iOS app or going to the web page. If I restart it with sudo service emby-server restart It all restarts and its good to go, where can I look to get a hint of whats happening? I did sudo service emby-server status when it last crashed but I forgot to save the output, any way to look back at that? Thanks Matt
matt77303 1 Posted January 17, 2018 Author Posted January 17, 2018 Its just done it again, can't do anything. no access to it anywhere, sudo service emby-server restart sorts it. ● emby-server.service - Emby Media Server Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-01-17 16:23:12 GMT; 2min 18s ago Process: 27058 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS) Main PID: 18768 (code=exited, status=34) Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing NewsEntryPoint Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing Notifications Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing WebSocketNotifier Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing CleanMissingEpisodesEntryPoint Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing ApiEntryPoint Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing DlnaProfileEntryPoint Jan 17 16:23:11 omv-Server emby-server[18768]: Info App: Disposing DlnaEntryPoint Jan 17 16:23:11 omv-Server systemd[1]: emby-server.service: Main process exited, code=exited, status=34/n/a Jan 17 16:23:12 omv-Server systemd[1]: emby-server.service: Unit entered failed state. Jan 17 16:23:12 omv-Server systemd[1]: emby-server.service: Failed with result 'exit-code'.
Luke 42078 Posted January 17, 2018 Posted January 17, 2018 Hi there, were any server log files generated, and if so, can you please attach them? Based on that output there should be a log file. thanks !
matt77303 1 Posted January 18, 2018 Author Posted January 18, 2018 Hi Luke, thanks for replying. I believe there was I’ll attach them when I get home. In about 5 hours. Thanks again. Matt
matt77303 1 Posted January 18, 2018 Author Posted January 18, 2018 Think this is the one when it crashed. Best I can do atm I’m on my phone at work. Lol System.ObjectDisposedException: Cannot access a disposed object. Object name: 'SessionManager'. at Emby.Server.Implementations.Session.SessionManager.CheckDisposed () [0x00016] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 at Emby.Server.Implementations.Session.SessionManager.SendMessageToUserSessions[T] (System.Collections.Generic.List`1[T] userIds, System.String name, T data, System.Threading.CancellationToken cancellationToken) [0x0002a] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 at Emby.Server.Implementations.EntryPoints.ServerEventNotifier+<SendMessageToUserSession>c__async0`1[T].MoveNext () [0x00063] in <283e6d64c4f54f1fbcf3f036adb82d8e>: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.ObjectDisposedException at Emby.Server.Implementations.Session.SessionManager.CheckDisposed () [0x00016] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 at Emby.Server.Implementations.Session.SessionManager.SendMessageToUserSessions[T] (System.Collections.Generic.List`1[T] userIds, System.String name, T data, System.Threading.CancellationToken cancellationToken) [0x0002a] in <283e6d64c4f54f1fbcf3f036adb82d8e>:0 at Emby.Server.Implementations.EntryPoints.ServerEventNotifier+<SendMessageToUserSession>c__async0`1[T].MoveNext () [0x00063] in <283e6d64c4f54f1fbcf3f036adb82d8e>: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
Luke 42078 Posted January 18, 2018 Posted January 18, 2018 Thanks, I'd really need to see the complete log file though.
matt77303 1 Posted January 18, 2018 Author Posted January 18, 2018 Ok. Will be home in 30 mins bud. Thank you. Matt
matt77303 1 Posted January 18, 2018 Author Posted January 18, 2018 (edited) logs attached from the time it crashed. Thank you. Matt server-63651803395.txt unhandled_db0a9bad-7744-4803-a3a4-3bfaf588a618.txt Edited January 18, 2018 by matt77303
Luke 42078 Posted January 18, 2018 Posted January 18, 2018 Ok yes this is a crash, but this should be pretty rare. It only occurs due to something that is trying to run while the server is already shutting down or restarting. We'll resolve this, but in the meantime i would remove the server restart plugin because that will be causing the server to restart more often than necessary. thanks.
matt77303 1 Posted January 18, 2018 Author Posted January 18, 2018 Ok. Thank you for looking. I’ll report back if it does it again. Matt
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