Exception: Magic number is wrong: 542Not An Issue
I am running a linux build with rust and oxide installed. The oxide.version shows up the version when ran. When trying to load a plugin I get "Compiler may not be set as executable; chmod +x or 0744/0755 required" However the permissions have been set correctly. Anyone know of a way to get this to work?
Please provide your full oxide/logs.
@wulf
Here is the log entry for trying to run this.

13:22 [Info] Loading Oxide Core v2.0.3972...
13:22 [Info] Loading extensions...
13:22 [Info] Loaded extension CSharp v2.0.4012 by Oxide and Contributors
13:22 [Info] Loaded extension MySql v2.0.3755 by Oxide and Contributors
13:22 [Info] Loaded extension Rust v2.0.4442 by Oxide and Contributors
13:22 [Info] Loaded extension SQLite v2.0.3754 by Oxide and Contributors
13:22 [Info] Loaded extension Unity v2.0.3768 by Oxide and Contributors
13:22 [Info] Latest compiler MD5: 8ce6d27e7718e3d164766bba8833537a
13:22 [Info] Local compiler MD5: 8ce6d27e7718e3d164766bba8833537a
13:22 [Info] Using Covalence provider for game 'Rust'
13:22 [Info] Loading plugins...
13:22 [Info] Loaded plugin Rust v2.0.4442 by Oxide and Contributors
13:22 [Info] Loaded plugin Unity v2.0.3768 by Oxide and Contributors
13:22 [Error] ExType: TypeInitializationException
13:22 [Error] Exception while starting compiler version : (Exception: Magic number is wrong: 542)
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <a8ed250850854b439cedc18931a314fe>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a8ed250850854b439cedc18931a314fe>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a8ed250850854b439cedc18931a314fe>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a8ed250850854b439cedc18931a314fe>:0
at System.ConsoleDriver..cctor () [0x0004d] in <a8ed250850854b439cedc18931a314fe>:0
13:22 [Warning] Compiler may not be set as executable; chmod +x or 0744/0755 required​
Looks like you may have a conflicting mono install on the server machine, which would need to be uninstalled.
Mono was not installed. which version needs to be installed or is it package with the oxide install?
There should be no mono packages installed at all.
Must have been an Ubuntu 19.10 issue. went to 18.04 and works fine.
pembreezy
Must have been an Ubuntu 19.10 issue. went to 18.04 and works fine.

Most likely came pre-installed with Mono somewhere.

Locked automatically