1. Community
  2. Game Support
  3. Rust
Exception: Magic number is wrong: 542Not An Issue
Posted 3 years ago
#1
(20:39:14) | Exception while starting compiler version : (Exception: Magic number is wrong: 542)
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <fb001e01371b4adca20013e0ac763896>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <fb001e01371b4adca20013e0ac763896>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <fb001e01371b4adca20013e0ac763896>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
at System.ConsoleDriver..cctor () [0x0004d] in <fb001e01371b4adca20013e0ac763896>:0
(20:39:14) | Compiler may not be set as executable; chmod +x or 0744/0755 required
(20:39:14) | BaseException: (Exception: Magic number is wrong: 542)
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <fb001e01371b4adca20013e0ac763896>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <fb001e01371b4adca20013e0ac763896>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <fb001e01371b4adca20013e0ac763896>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
at System.ConsoleDriver..cctor () [0x0004d] in <fb001e01371b4adca20013e0ac763896>:0
(20:39:14) | Error while compiling: compiler version couldn't be started

I have tried literally everything to fix this, from setting term to xterm. Reinstalling oxide, adding new packages. self-installing the compiler, setting chmod +x to the file and alot more I haven't been able to fix this damn issue. note- I fixed it before but I have no clue how ;l
Posted 3 years ago
#2

Let me know if theres a way to check if the CHMOD is actually working because when I run the command I get no response

Posted 3 years ago
#4

Already looked through all of that

Posted 3 years ago
#5

That's the solution and fix for it. Make sure you are adding it TO your startup script, not running it somewhere as a command.

Posted 3 years ago
#6
export TERM=xterm done this and verified and restarted
Posted 3 years ago
#7

It isn't a command, it would be part of your shell script that starts the server.

Posted 3 years ago
Last updated 3 years ago
#8

unless I put this somewhere in my startup options

export 'TERM=roxterm' && ./start.sh


Merged post

export TERM=xterm ./RustDedicated -nographics -batchmode +server.port ${port} so my script would be like this?
Posted 3 years ago
#9

It would be at the top of your script generally after the #! declaration, not inlined with another.

Posted 3 years ago
#10

I'm using pufferpanel & I can set a server definition which is the launch command, and a pre run hook which checks for rust updates like this

steamcmd/steamcmd.sh +login anonymous +force_install_dir .. +app_update 258550 +quit

Posted 3 years ago
#11

It'd part of be part of your .sh script that runs the server.

Posted 3 years ago
#12

Welp I don't even have a .sh script

Posted 3 years ago
#13

Pufferpanel provides methods for custom scripts and modifying them I believe, so you'd need to figure out which one is used to start your server.

Posted 3 years ago
#14

Well I'm undenounced to that so I have no clue how to add that line & now my server wont even start ever since I tried starting it with that xterm thing

Posted 3 years ago
#15

Are you using LGSM on Debian 11?

Locked automatically