Emby Crashing around once a day - Ubuntu

[guimello 1]

Hi All

 

My emby server (latest version) is running on an Ubuntu 16.04 machine.  Has previously worked flawlessly, although recently it has been crashing (roughly once a day or every 2 days).  The error message generated is below:

2017-04-18 06:32:55.9459 Debug LibraryMonitor: New file refresher created for /nas_share/Media/TV/American Dad!/Season 13/American Dad! - S13E09 - Anchorfran [HDTV.720p.x264-KILLERS].mkv
2017-04-18 06:32:55.9459 Debug LibraryMonitor: Resetting file refresher from /nas_share/Media/TV/American Dad!/Season 13/American Dad! - S13E09 - Anchorfran [HDTV.720p.x264-KILLERS].mkv to /nas_share/Media/TV/American Dad!/Season 13
2017-04-18 06:32:56.2259 Error Main: UnhandledException
    *** Error Report ***
    Version: 3.2.12.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 3.19.8.0
    64-Bit OS: True
    64-Bit Process: True
    Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016)
    Processor count: 4
    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 <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.IO.InotifyWatcher.Monitor () [0x0003c] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0
    System.NullReferenceException
      at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x000ac] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.IO.InotifyWatcher.Monitor () [0x0003c] in <bd46d4d4f7964dfa9beea098499ab597>:0
      at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <8f2c484307284b51944a1a13a14c0266>:0
      at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0

A full log file is also attached.

 

Would be grateful if you could offer any help at all!

 

Thanks

Gui

Log.txt

Edited April 18, 2017 by guimello

[Luke 37280]

Hi, try turning off the realtime monitor for your Emby libraries. Let us know if that helps. Thanks.

[guimello 1]

Thanks Luke - this appears to have resolved the issue of Emby crashing.

 

However, having realtime monitor is a feature that I would quite like to keep enabled.  Is there a way fix this?

 

Thanks again.

[Luke 37280]

The error is being thrown by the mono runtime's file system monitor that we're using and it is sometimes difficult for us to catch it and recover, so that's the reason for the crash. I'll take another look at this for the next release, thanks.