Jump to content

Recommended Posts

Posted (edited)
Veteran ARK server host here: I've just spun up a test Atlas server and even though the process is running and listening on the correct ports (this is Linux) and the server is receiving packets to the listening port, the server is reporting offline when polled by steam view > servers list (prompted manually).
 
Well, I think it's running. The stdout from the application is:
ATLAS@Games:~$ bash servertest.sh
Using binned.
4.5.1-0+UE4 7038 3077 409 10
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Setting breakpad minidump AppID = 834910

It's definitely listening and using a bunch of memory:

alexicon@Games:/home/ATLAS/ATLAS/ShooterGame/Saved/Logs$ sudo netstat -nlp | grep Shoot
tcp        0      0 0.0.0.0:32336           0.0.0.0:*               LISTEN      26313/ShooterGameSe
udp        0      0 0.0.0.0:5762            0.0.0.0:*                           26313/ShooterGameSe
udp    43008      0 0.0.0.0:57556           0.0.0.0:*                           26313/ShooterGameSe
26313 ATLAS     20   0 6568776 3.639g  72304 S   1.3 46.7   0:52.85 ShooterGameServer

Edit:

After some additional troubleshooting I found the following from the ShooterGame logs:

alexicon@Games:/home/ATLAS/ATLAS/ShooterGame/Saved/Logs$ sudo tail -f ShooterGame.log
[2019.03.03-09.35.18:020][  0]Log file open, 03/03/19 01:35:18
[2019.03.03-09.35.18:020][  0]ATLAS Version: 20.12 (Rev. 109371)
[2019.03.03-09.35.18:020][  0]PID: 28103
[2019.03.03-09.35.34:517][  0]Primal Game Data Took 16.15 seconds
[2019.03.03-09.35.37:022][  0]SteamSocketsOpenSource: gethostname failed ()
[2019.03.03-09.35.37:022][  0]gethostbyname failed ()
[2019.03.03-09.35.42:669][  0]Network range scales set to: 48 start, 77 end, 0.440000 endscale

I can see from the below post that this all looks okay, it's just that the server never starts: 

In this admin's case, the server took over 400 seconds to load. So I've left it for over 1200 and no dice.

Edited by alexicon
formatting

Share this post


Link to post
Share on other sites

The issue is due to poor error handling and hard-coded relative paths.

You _MUST_ execute the binary from the `./ShooterGame/Linux/Binaries` folder or it will just hang as the server never errors out when it cannot write the .atlas file.

Quote

[pid  3621] openat(AT_FDCWD, "/atlas/ShooterGame/../../../ShooterGame/Saved/AA/ocean.atlas", O_RDWR|O_CREAT|O_CLOEXEC, 0644) = -1 ENOENT (No such file or directory)
[pid  3621] openat(AT_FDCWD, "/atlas/ShooterGame/../../../ShooterGame/Saved/AA/ocean.atlas", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×