OKDaG 1 Posted July 16, 2017 Share Posted July 16, 2017 Hi, i'm running emby 3.2.25.0 on Ubuntu 16.04 and in the Last time it crashes sometimes: 2017-07-16 13:25:20.7766 Error Main: UnhandledException *** Error Report *** Version: 3.2.25.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.4.0.83 64-Bit OS: True 64-Bit Process: True Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Tue May 2 22:26:20 UTC 2017) Processor count: 8 Program data path: /var/lib/emby-server Application directory: /usr/lib/emby-server/bin System.NullReferenceException: Object reference not set to an instance of an object at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <5641e4edad4f4464ba58c620a7b8ea48>:0 at System.IO.InotifyWatcher.Monitor () [0x0003c] in <5641e4edad4f4464ba58c620a7b8ea48>:0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] 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.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 System.NullReferenceException at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <5641e4edad4f4464ba58c620a7b8ea48>:0 at System.IO.InotifyWatcher.Monitor () [0x0003c] in <5641e4edad4f4464ba58c620a7b8ea48>:0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] 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.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 Bevor 3.2.20.0 i couldn't remember about crashes, so i guess this is a new behavior. After the crash the Restart=on-abort in the systemd service is not honored. I've changed it to Restart=always but this will be overwritten after each update. Please also change it in the sources to always. Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted July 16, 2017 Share Posted July 16, 2017 gonna need to upload the full log. Link to comment Share on other sites More sharing options...
hadr0n 3 Posted July 20, 2017 Share Posted July 20, 2017 (edited) Hi, The reference to Inotify in the error may indicate an issue with the Emby feature allowing to automatically track changes on the file system (i.e. to automatically detect additionnal files in the library when copied on the disk,...). Maybe you can disable this feature (in the properties of the corresponding media libraries) and check if the error is still there, it may help find the source of the error. Edited July 20, 2017 by hadr0n Link to comment Share on other sites More sharing options...
OKDaG 1 Posted July 27, 2017 Author Share Posted July 27, 2017 Thank you. Pretty sure it is related to the track changes feature, crash happend while files moved in one of the directories and while scanning by emby some files where deleted. Link to comment Share on other sites More sharing options...
hadr0n 3 Posted July 27, 2017 Share Posted July 27, 2017 Have you try to disable this feature? It seems like it can be disabled in the media library properties. I'm not an emby dev but I think it may help devs if you specifiy the file system you are using, since it appears inotify is not supported on every file systems. Link to comment Share on other sites More sharing options...
Luke 37184 Posted July 27, 2017 Share Posted July 27, 2017 Yea try disabling the realtime monitor for your emby libraries. please let us know if this helps. thanks ! Link to comment Share on other sites More sharing options...
Luke 37184 Posted August 6, 2017 Share Posted August 6, 2017 Did this resolve your crashes? thanks. 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