hsran 0 Posted October 9, 2017 Posted October 9, 2017 I have installed Emby server on OMV 3 using the debian method but it has been really unstable.Crashes randomly few times a week and has been pretty unreliable as a media server. It's been going on from the last month and I have gone through a few version changes. Version: 3.2.33.0 Operating system: Unix 4.9.0.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 5.2.0.224 This is unhandled log text created when the server went down. System.NullReferenceException: Object reference not set to an instance of an object at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x0009d] in <2736c63206b04ee9bdd526624de6640b>:0 at System.IO.InotifyWatcher.Monitor () [0x00031] in <2736c63206b04ee9bdd526624de6640b>:0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 System.NullReferenceException at System.IO.InotifyWatcher.ProcessEvents (System.Byte[] buffer, System.Int32 length) [0x0009d] in <2736c63206b04ee9bdd526624de6640b>:0 at System.IO.InotifyWatcher.Monitor () [0x00031] in <2736c63206b04ee9bdd526624de6640b>:0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 server-63643017600.txt server-63643165087.txt
Luke 42078 Posted October 9, 2017 Posted October 9, 2017 Hi, I notice you are running mono 5.2. We officially support up to 4.8.1. Can you roll it back? Thanks !
hsran 0 Posted October 14, 2017 Author Posted October 14, 2017 Hi, I notice you are running mono 5.2. We officially support up to 4.8.1. Can you roll it back? Thanks ! Tried rolling back to 4.8.1 but too many dependencies are missing.Tried building it from source code and emby requests for mono-devel. 5.0 is the minimum that installs without any issues on Jessie
Luke 42078 Posted October 14, 2017 Posted October 14, 2017 5.0 will definitely crash and burn, fyi. You might want to look at our new .net core based packages that no longer use mono: https://emby.media/community/index.php?/topic/50012-emby-server-for-net-core They will soon replace the current packages. Thanks.
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