Sharing violation on oxide logNot An Issue
An exception was thrown! (IOException: Sharing violation on path C:\TCAFiles\Users\johnh2\7901\oxide\logs\oxide_2020-05-11.txt)
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x0019e] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean isAsync, System.Boolean anonymous) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0
at (wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMode,System.IO.FileAccess)
at Oxide.Core.Logging.RotatingFileLogger.BeginBatchProcess () [0x0000c] in <ac41dd3599754d448b8c218b34645820>:0
at Oxide.Core.Logging.ThreadedLogger.Worker () [0x0002f] in <ac41dd3599754d448b8c218b34645820>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <437ba245d8404784b9fbab9b439ac908>:0
If that happens, the first thing I would check is whether not I have a duplicate server process running in the background and end it.
I an not sure how to do that, my server is hosted by Low-MS, I have submited a ticket with them. Thank you.
Locked automatically