• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

TFS 0.X How to understand why server crashes?

hiwyn

Member
Joined
Aug 30, 2021
Messages
78
Reaction score
8
I put a test server in a host and after 3 months without crash, its crashing everyday...
How to check it?
 
You can run the server on cmd to see the crash before the server close
 
You can run the server on cmd to see the crash before the server close
i'm already running on cmd, i'm running on linux, but its a VPS, the connection was closed, i cant see the terminal no more
there is no logs? (i'm using 0.4)
 
i'm already running on cmd, i'm running on linux, but its a VPS, the connection was closed, i cant see the terminal no more
there is no logs? (i'm using 0.4)

Install gdb and then launch your server like this:

Code:
#!/bin/bash
ulimit -c unlimited
while true; do ./tfs --log-file "output.txt" "error.txt"; done

After crash, a dump will be generated in your server folder, to read the backtrace:

Code:
gdb tfs core

and then

Code:
bt full
 
Install gdb and then launch your server like this:

Code:
#!/bin/bash
ulimit -c unlimited
while true; do ./tfs --log-file "output.txt" "error.txt"; done

After crash, a dump will be generated in your server folder, to read the backtrace:

Code:
gdb tfs core

and then

Code:
bt full

i named a file with gdb.sh with:
Code:
#!/bin/bash
ulimit -c unlimited
while true; do ./tfs --log-file "output.txt" "error.txt"; done

but after i close ssh with server the server shutdowns...
how to mantain it online?
 
i named a file with gdb.sh with:
Code:
#!/bin/bash
ulimit -c unlimited
while true; do ./tfs --log-file "output.txt" "error.txt"; done

but after i close ssh with server the server shutdowns...
how to mantain it online?

Code:
screen -s otserver

Then run it

To close the screen use CTRL + A and CTRL + C, and to resume it:

Code:
screen -r otserver

Maybe you'll need to install screen first.

Code:
sudo apt-get install screen
 
Code:
screen -s otserver

Then run it

To close the screen use CTRL + A and CTRL + C, and to resume it:

Code:
screen -r otserver

Maybe you'll need to install screen first.

Code:
sudo apt-get install screen

let me see if i get it:

I should rename gdb.sh to otserver.sh

the first start i should type:
screen -s otserver

ctrl+c to shutdown the server (and if i had disconnected?)

and next times i start the server its
screen -r otserver
 
My bad, CTRL + A and CTRL + D to close the screen without shutting down the server (CTRL + C to shut down).
You can resume the console with screen -r and the name of the screen (in this case otserver).

You don't need to create a new .sh file tho, just run the full command directly into the new screen.
 
Back
Top