webrats 0 Posted September 5, 2017 Share Posted September 5, 2017 System.NullReferenceException: Object reference not set to an instance of an objectat System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <f8255d9ef0594d18ae2c0d97286b9a80>:0at System.IO.InotifyWatcher.Monitor () [0x0003c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0System.NullReferenceExceptionat System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <f8255d9ef0594d18ae2c0d97286b9a80>:0at System.IO.InotifyWatcher.Monitor () [0x0003c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 2017-09-05 15:10:13.631 Info TaskManager: Scan media library Failed after 0 minute(s) and 6 seconds2017-09-05 15:10:13.773 Info ServerManager: Sending web socket message NotificationAdded2017-09-05 15:10:13.774 Info ServerManager: Sending web socket message NotificationAdded2017-09-05 15:10:13.774 Info ServerManager: Sending web socket message ScheduledTaskEnded2017-09-05 15:10:13.774 Info TaskManager: ExecuteQueuedTasks2017-09-05 15:10:15.219 Info LibraryMonitor: Watching directory /volume1/Storage/Tv2017-09-05 15:10:16.524 Info LibraryMonitor: Watching directory /volume1/Storage/Movies2017-09-05 15:10:25.320 Info LibraryMonitor: Watching directory /mnt/tv2017-09-05 15:10:25.768 Error Main: UnhandledException *** Error Report *** Version: 3.2.30.0 Command line: /var/packages/EmbyServer/target/server/MediaBrowser.Server.Mono.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -restartpath /var/packages/EmbyServer/scripts/restart Operating system: Unix 3.10.35.0 64-Bit OS: True 64-Bit Process: True Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sat Apr 22 22:46:32 CST 2017) Processor count: 4 Program data path: /var/packages/EmbyServer/target/var Application directory: /volume1/@appstore/EmbyServer/releases/v3.2.30.0 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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 at System.IO.InotifyWatcher.Monitor () [0x0003c] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 at System.IO.InotifyWatcher.Monitor () [0x0003c] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 Link to comment Share on other sites More sharing options...
Luke 30111 Posted September 5, 2017 Share Posted September 5, 2017 That looks like a crash coming from mono's realtime monitor. try turning off the realtime monitor in emby library setup. Link to comment Share on other sites More sharing options...
webrats 0 Posted September 5, 2017 Author Share Posted September 5, 2017 Thanks ill give it a shot Link to comment Share on other sites More sharing options...
nvader2000 12 Posted September 10, 2017 Share Posted September 10, 2017 (edited) Where can I find the real time monitor setting in emby? Edited September 10, 2017 by nvader2000 Link to comment Share on other sites More sharing options...
Luke 30111 Posted September 10, 2017 Share Posted September 10, 2017 Where can I find the real time monitor setting in emby? @@nvader2000, go into Emby library setup and click on each library. Then it will open a settings popup for that library. The realtime monitor setting will be there. Please let us know if this helps. Thanks. Link to comment Share on other sites More sharing options...
runner780 0 Posted September 11, 2017 Share Posted September 11, 2017 Have the same issue, server stops 2 or 3 times a week. Have to manually restart. Allready tried https://emby.media/community/index.php?/topic/40980-emby-on-xpenology-keeps-stopping-after-short-time/page-2 Just disabled real time monitoring in my libraries, see how it goes. DS1815+ Emby server 3.2.30.16-1-beta Link to comment Share on other sites More sharing options...
nightwar 0 Posted September 21, 2017 Share Posted September 21, 2017 Did that work for you? Link to comment Share on other sites More sharing options...
webrats 0 Posted September 21, 2017 Author Share Posted September 21, 2017 Fixed my issue Link to comment Share on other sites More sharing options...
Luke 30111 Posted September 21, 2017 Share Posted September 21, 2017 Thanks for the feedback. Link to comment Share on other sites More sharing options...
webrats 0 Posted September 21, 2017 Author Share Posted September 21, 2017 No problem, I hate it when people don't report back. Link to comment Share on other sites More sharing options...
Luke 30111 Posted September 21, 2017 Share Posted September 21, 2017 I am hoping that once we get Synology switched from Mono to .NET Core that you'll be able to use the realtime monitor again. We are going one by one updating all the NAS packages to Synology will eventually get it's turn. Thanks. Link to comment Share on other sites More sharing options...
webrats 0 Posted September 22, 2017 Author Share Posted September 22, 2017 really not a big deal to me. Sickrage and potato both have notify emby So my stuff pops up pretty quick once its added Link to comment Share on other sites More sharing options...
Luke 30111 Posted September 22, 2017 Share Posted September 22, 2017 Thanks for the feedback. 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