Server Crash Logs

Discussion in 'Rust Discussion' started by JohnRU, Jul 29, 2015.

  1. Code:
    [7/29/2015 6:14:42 PM] Assertion failed: Stomping old lifeStory
    MiniRaven:CleanupStackTrace(String)
    MiniRaven:ReportException(String, String)
    ErrorLogger:CaptureLog(String, String, LogType)
    Facepunch.Output:LogHandler(String, String, LogType)
    UnityEngine.Application:CallLogCallback(String, String, LogType, Boolean)
    UnityEngine.Debug:Internal_Log(Int32, String, Object)
    UnityEngine.Debug:LogError(Object)
    Assert:Test(Boolean, String)
    BasePlayer:LifeStoryStart()
    BasePlayer:Respawn(Boolean)
    ConVar.Global:respawn(Arg)
    System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&)
    System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)
    System.Reflection.MethodBase:Invoke(Object, Object[])
    <BuildFunctions>c__AnonStorey1B:<>m__25(Arg)
    Run:Internal(Arg, Boolean)
    ConsoleSystem:OnClientCommand(Message)
    ServerMgr:OnNetworkMessage(Message)
    Network.Implementation.Raknet.Server:ConnectedPacket(RaknetConnection)
    Network.Implementation.Raknet.Server:Cycle()
    ServerMgr:Update()
    Code:
    [7/29/2015 6:14:42 PM] Assertion failed: Stomping old lifeStory
    This looks to be the cause of my servers crash. Is there anything of note in this what does it mean.
     
  2. Wulf

    Wulf Community Admin

    That message is from Rust, but it simply means it is wiping out old remnants of a player that was likely forcefully respawned somewhere else. It shouldn't cause your server to crash, and doesn't look like your server crashed at that point at least from that.
     
  3. Do you think this caused it?

    Code:
    [7/29/2015 6:13:46 PM] [Oxide] 6:13 PM [Error] Failed to call hook 'CanClientLogin' on plugin 'Enhanced Ban System'
    File: EnhancedBanSystem.lua Line: 148 attempt to compare nil with number:
      at NLua.Lua.ThrowExceptionFromError (Int32 oldTop) [0x00000] in <filename unknown>:0
      at NLua.Lua.CallFunction (System.Object function, System.Object[] args, System.Type[] returnTypes) [0x00000] in <filename unknown>:0
      at NLua.Lua.CallFunction (System.Object function, System.Object[] args) [0x00000] in <filename unknown>:0
      at NLua.LuaFunction.Call (System.Object[] args) [0x00000] in <filename unknown>:0
      at Oxide.Ext.Lua.Plugins.LuaPlugin.OnCallHook (System.String hookname, System.Object[] args) [0x00000] in <filename unknown>:0
      at Oxide.Core.Plugins.Plugin.CallHook (System.String hookname, System.Object[] args) [0x00000] in <filename unknown>:0 
    [DOUBLEPOST=1438191089][/DOUBLEPOST]
    Also do you know anything about a KernelBase.dll error. It may be that again I've been having issues with it for a while now.
     
  4. Wulf

    Wulf Community Admin

    The CanClientLogin wouldn't cause a server crash. The crash logs would be what you'd really need to look at.
     
  5. There is no crash logs. I've just updated steam and oxide also and still the same thing there and nothing in the error log either. I think this short term issue may be down to something with my host if no one is experiencing it. I mentioned it a few days ago my cpu shows 25% cpu always and slight fluctuations ever now and again. On the logs it doesn't show anything.
    [DOUBLEPOST=1438192679][/DOUBLEPOST]Ok I think I found the issue. It was either RustDB, enhanced ban system or Playtime. I'll give it another 12hours to see if this was the solution but the server is running fine again after removing them error plugins.
     
  6. Wulf

    Wulf Community Admin

    If the server is actually crashing, you'd have dated folders with the crash dumps in the server root directory.
     
  7. So in them cases if no crash folders it's 100% plugin caused? Like what do you do if there is no crash folders but you're crashing. There needs to be a tutorial on diagnostics for oxide.
     
  8. Wulf

    Wulf Community Admin

    If there are no dumps, then its 99% likely not a crash. ;) The crash dumps are for Rust, not Oxide.