1. I got this error after update the server and oxide, someones know why?
    Code:
    Connected to Steam
    ArgumentNullException: Argument cannot be null.
    Parameter name: newOut
      at System.Console.SetOut (System.IO.TextWriter newOut) [0x00000] in <filename unknown>:0
      at Windows.ConsoleWindow.Shutdown () [0x00000] in <filename unknown>:0
      at ServerConsole.OnDisable () [0x00000] in <filename unknown>:0
    UnityEngine.Behaviour:set_enabled(Boolean)
    Oxide.Game.Rust.RustCore:OnServerInitialized()
    System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&)
    System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)
    System.Reflection.MethodBase:Invoke(Object, Object[])
    Oxide.Core.Plugins.CSPlugin:InvokeMethod(HookMethod, Object[])
    Oxide.Core.Plugins.CSPlugin:OnCallHook(String, Object[])
    Oxide.Core.Plugins.Plugin:CallHook(String, Object[])
    Oxide.Core.Plugins.PluginManager:CallHook(String, Object[])
    Oxide.Core.OxideMod:CallHook(String, Object[])
    Oxide.Core.Interface:CallHook(String, Object[])
    ServerMgr:OpenConnection()
    <StartServer>c__IteratorF:MoveNext()
    UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
    Thanks you
     
    Last edited by a moderator: Jul 14, 2016
  2. Wulf

    Wulf Community Admin

    You can ignore it, it isn't preventing the server from starting.
     
  3. Yes yes, I see it now, it's just give error Rust:IO, same other people xD
     
  4. Wulf

    Wulf Community Admin

    It's not from Rust:IO, it's from Oxide's console trying to enable on Linux.
     
  5. Can you try adding the following to the oxide.root.json file:
    Code:
    "DisableConsole": true
    Keep in mind that you need to add a , either on the end of the line or the line before so that the json remains valid.
    It should then look like this (more or less, depending on where you added it):
    Code:
    {
        "ExtensionDirectory": "RustDedicated_Data\\Managed",    "PluginDirectory": "plugins",
        "ConfigDirectory": "config",
        "DataDirectory": "data",
        "LangDirectory": "lang",
        "LogDirectory": "logs",
       
        "DisableConsole": true,    "InstanceCommandLines":
        [
            "{oxide.directory}",
            "server\\{server.identity}\\oxide",
            "server\\my_server_identity\\oxide"
        ]
    }
    
    When you start the server again it should no longer attempt to start the Oxide console and run the default Rust/Unity one which should normally not throw that error.

    (I could be wrong, I don't have a *nix to test this on)
     
  6. Wulf

    Wulf Community Admin

    This should be fixed as of a few builds ago. :)