Jump to content

Recommended Posts

18 hours ago, CrimsonFusion said:

It seems I am unable to join a game with Linux server build 402.6.  The server shows up in game but when joining I receive Joining failed - Connection Timeout.  The only error that pops server side is:

Using binned.

4.5.1-0+UE4 7038 3077 410 10

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

Setting breakpad minidump AppID = 834910

I made a post a week or so ago asking if anyone had a working linux server and I go no replies.

I did a little digging with strace and from what I'm seeing it keeps trying to read information about the processors. It calls sched_getaffinity() and a few other reads in a loop and it appears to loop forever.

  • Like 1

Share this post


Link to post
Share on other sites
34 minutes ago, MeatShield said:

I made a post a week or so ago asking if anyone had a working linux server and I go no replies.

I did a little digging with strace and from what I'm seeing it keeps trying to read information about the processors. It calls sched_getaffinity() and a few other reads in a loop and it appears to loop forever.

I am having the same exact issue on Linux with a fresh installation.

  • Like 1

Share this post


Link to post
Share on other sites

One wonders ... since they've partnered up with paid hosting they now have no motivations to fix linux builds which the community has made tools to simplify and cheapen the process...

Share this post


Link to post
Share on other sites
On 1/15/2019 at 9:06 PM, Rob said:

Linux servers are now officially supported.

Please post here if its working, or if any issues occur.

Thank you,

Rob

Have been unable to connect to Linux servers for months.  Please review previous posts and respond.  Nobody can connect to a Linux server.

Edited by Thorasta
Trying to figure out why post is hidden.

Share this post


Link to post
Share on other sites

@Jatheish

@ZenRowe

@Dollie

On 1/10/2020 at 9:51 AM, MeatShield said:

I made a post a week or so ago asking if anyone had a working linux server and I go no replies.

I did a little digging with strace and from what I'm seeing it keeps trying to read information about the processors. It calls sched_getaffinity() and a few other reads in a loop and it appears to loop forever.

@Jatheish

@ZenRowe

@Dollie

Share this post


Link to post
Share on other sites

Has Grapeshot Games definitively buried the idea of a dedicated server for their game?

That would be stupid : there are thousands of players waiting for it...

The success of a game like ARK came from the base players' community, and not from the paid hosting companies !

Edited by Selune

Share this post


Link to post
Share on other sites

The windows dedicated server works fine. It's annoying, but I setup a windows 10 VM and I'm running my servers out of it.

Without memory compression I'm averaging about 1.9 GB per grid, 2.7 GB high, 1.4 GB low. With compression they average about 675 MB per, 800 MB high, 500 MB low.

Once the linux dedicated server works again it should just be copying some files over.

I wouldn't wait for the linux client if you want to host your own.

Share this post


Link to post
Share on other sites

Hate to rez but this is the "Linux Servers" thread....

Curious if  404.8 Linux/ShooterGameServer binary was fixed to address the Linux Server Timeout issue because a year later I'm seeing the same issue.

Using atlasmanager install over at https://github.com/BoiseComputer/atlas-server-tools

I was able to easily get 4 servers up and running in less than an hour on my Ubuntu 18.0.4LTS Server.

I was able to verify via serverGridEditos that my ServerGrid.json file loads & looks good

I was able to verify redis starts

I was able to verify ShooterGameServer instances all start without error.

Everything looks as expected and I see the server pop right up on my ATLAS Client....

HOWEVER, when I try and connect to the server, select my starting zone A1,  I'm greeted with timeouts...  

 

LOGS:::::::::::::::::::::::::::::::::::::::::::
2020-03-15 18:17:08: [main] 2020-03-15 18:17:08: start
2020-03-15 18:17:08: [main] 2020-03-15 18:17:08: Running /home/steam/ATLAS/ShooterGame/Binaries/Linux/ShooterGameServer Ocean\?RCONEnabled=True\?RCONPort=32330\?Port=5750\?QueryPort=57550\?ServerPassword=rpass\?ServerAdminPassword=rc0n\?MaxPlayers=70\?AltSaveDirectoryName=A1\?ServerX=0\?ServerY=0\?MapPlayerLocation=True\?SeamlessIP\?culture=en\?listen -NoCrashDialog -log -manualmanagedmods -server
2020-03-15 18:17:08: [main] 2020-03-15 18:17:08: Server PID: 770
2020-03-15 18:17:08: [main] [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
2020-03-15 18:17:08: [main] Setting breakpad minidump AppID = 834910
2020-03-15 18:17:23: [main] 2020-03-15 18:17:23: server is up


2020-03-15 18:17:23: [a2] 2020-03-15 18:17:23: start
2020-03-15 18:17:23: [a2] 2020-03-15 18:17:23: Running /home/steam/ATLAS/ShooterGame/Binaries/Linux/ShooterGameServer Ocean\?RCONEnabled=True\?RCONPort=32332\?Port=5754\?QueryPort=57552\?ServerPassword=rpass\?ServerAdminPassword=rc0n\?MaxPlayers=25\?AltSaveDirectoryName=A2\?ServerX=1\?ServerY=0\?MapPlayerLocation=True\?SeamlessIP\?culture=en\?listen -NoCrashDialog -log -manualmanagedmods -server
2020-03-15 18:17:23: [a2] 2020-03-15 18:17:23: Server PID: 1657
2020-03-15 18:17:24: [a2] [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
2020-03-15 18:17:24: [a2] Setting breakpad minidump AppID = 834910
2020-03-15 18:17:28: [a2] 2020-03-15 18:17:28: server is up


2020-03-15 18:17:38: [b1] 2020-03-15 18:17:38: start
2020-03-15 18:17:38: [b1] 2020-03-15 18:17:38: Running /home/steam/ATLAS/ShooterGame/Binaries/Linux/ShooterGameServer Ocean\?RCONEnabled=True\?RCONPort=32331\?Port=5752\?QueryPort=57551\?ServerPassword=rpass\?ServerAdminPassword=rc0n\?MaxPlayers=70\?AltSaveDirectoryName=B1\?ServerX=0\?ServerY=1\?MapPlayerLocation=True\?SeamlessIP\?culture=en\?listen -NoCrashDialog -log -manualmanagedmods -server
2020-03-15 18:17:38: [b1] 2020-03-15 18:17:38: Server PID: 2569
2020-03-15 18:17:39: [b1] [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
2020-03-15 18:17:39: [b1] Setting breakpad minidump AppID = 834910
2020-03-15 18:17:43: [b1] 2020-03-15 18:17:43: server is up


2020-03-15 18:17:53: [b2] 2020-03-15 18:17:53: start
2020-03-15 18:17:53: [b2] 2020-03-15 18:17:53: Running /home/steam/ATLAS/ShooterGame/Binaries/Linux/ShooterGameServer Ocean\?RCONEnabled=True\?RCONPort=32333\?Port=5756\?QueryPort=57553\?ServerPassword=rpass\?ServerAdminPassword=rc0n\?MaxPlayers=70\?AltSaveDirectoryName=B2\?ServerX=1\?ServerY=1\?MapPlayerLocation=True\?SeamlessIP\?culture=en\?listen -NoCrashDialog -log -manualmanagedmods -server
2020-03-15 18:17:53: [b2] 2020-03-15 18:17:53: Server PID: 3572
2020-03-15 18:17:53: [b2] [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
2020-03-15 18:17:53: [b2] Setting breakpad minidump AppID = 834910
2020-03-15 18:17:58: [b2] 2020-03-15 18:17:58: server is up

 

UNIX::::::::::::::::::::::::::::::::::::::::::::::::

steam@ATLAS:~$ atlasmanager status @all
Running command 'status' for instance 'main'
 Server running:   Yes
 Server PID:   770
 Redis Server running:   Yes
 Redis Server PID:   709
 Server listening:   Yes
Server Name: Tropical Freeport - (v404.8)
Players: 0 / 63
Active Players: 0
 Server online:   Yes
 Steam connect link:   steam://connect/172.115.247.194:57550
 Server build ID:   4670174
Running command 'status' for instance 'a2'
 Server running:   Yes
 Server PID:   1657
 Redis Server running:   Yes
 Redis Server PID:   709
 Server listening:   Yes
Server Name: Atlas_B1 - (v404.8)
Players: 0 / 23
Active Players: 0
 Server online:   Yes
 Steam connect link:   steam://connect/172.115.247.194:57552
 Server build ID:   4670174
Running command 'status' for instance 'b1'
 Server running:   Yes
 Server PID:   2569
 Redis Server running:   Yes
 Redis Server PID:   709
 Server listening:   Yes
Server Name: Atlas_A2 - (v404.8)
Players: 0 / 63
Active Players: 0
 Server online:   Yes
 Steam connect link:   steam://connect/172.115.247.194:57551
 Server build ID:   4670174
Running command 'status' for instance 'b2'
 Server running:   Yes
 Server PID:   3572
 Redis Server running:   Yes
 Redis Server PID:   709
 Server listening:   Yes
Server Name: Atlas_B2 - (v404.8)
Players: 0 / 63
Active Players: 0
 Server online:   Yes
 Steam connect link:   steam://connect/172.115.247.194:57553
 Server build ID:   4670174

 


steam@ATLAS:~$ netstat -plnt
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:32330           0.0.0.0:*               LISTEN      770/ShooterGameServ
tcp        0      0 0.0.0.0:32331           0.0.0.0:*               LISTEN      2569/ShooterGameSer
tcp        0      0 0.0.0.0:6379            0.0.0.0:*               LISTEN      709/redis-server *:
tcp        0      0 0.0.0.0:32332           0.0.0.0:*               LISTEN      1657/ShooterGameSer
tcp        0      0 0.0.0.0:32333           0.0.0.0:*               LISTEN      3572/ShooterGameSer
tcp        0      0 0.0.0.0:57550           0.0.0.0:*               LISTEN      770/ShooterGameServ
tcp        0      0 0.0.0.0:57551           0.0.0.0:*               LISTEN      2569/ShooterGameSer
tcp        0      0 0.0.0.0:57552           0.0.0.0:*               LISTEN      1657/ShooterGameSer
tcp        0      0 0.0.0.0:57553           0.0.0.0:*               LISTEN      3572/ShooterGameSer
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:27000           0.0.0.0:*               LISTEN      770/ShooterGameServ
tcp        0      0 0.0.0.0:27001           0.0.0.0:*               LISTEN      2569/ShooterGameSer
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:27002           0.0.0.0:*               LISTEN      1657/ShooterGameSer
tcp        0      0 0.0.0.0:27003           0.0.0.0:*               LISTEN      3572/ShooterGameSer
tcp6       0      0 :::6379                 :::*                    LISTEN      709/redis-server *:
tcp6       0      0 :::22                   :::*                    LISTEN      -
tcp6       0      0 ::1:25                  :::*                    LISTEN      -
steam@ATLAS:~$
 

Edited by Joe Volcano

Share this post


Link to post
Share on other sites

I can't believe they actually fixed the linux server after all this time. 

Even managed to get it to work on Ubuntu 20.04 after installing a few files from Bionic.

 

Share this post


Link to post
Share on other sites

Hi 🙂

I can confirm that I got my atlasserver up and running again .. I can't say whether WD / GS has actually fixed anything

but in the end it was definitely the problem that I suddenly lacked a lib (Ubuntu 18.04) in such problem cases it is advisable to run the ShooterGameServer without tools etc.

It was strange that the servers were just resting and everything was there beforehand and the servers were running until 1 2 months ago .. you just could not connect ^ ^

 

Here is a small excerpt from my terminal ..
after reinstalling the libraries: libprotobuf.so.10 and reinstalling redis (which no longer worked) everything works again

 

steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ ./ShooterGameServer start
./ShooterGameServer: error while loading shared libraries: libprotobuf.so.10: ca   nnot open shared object file: No such file or directory
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ ./ShooterGameServer start
Using binned.
4.5.1-0+UE4 7038 3077 410 10
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Setting breakpad minidump AppID = 834910
LowLevelFatalError [File:D:\AtlasSVN\Projects\ShooterGame\Source\ShooterGame\Private\DatabaseShared_Redis.cpp] [Line: 144]
Redis Failed To Connect! Check that it's running and connectable from here or edit ServerGrid.ServerOnly.json if this is incorrect. URL=127.0.0.1 EX="connect() failure"
Signal 11 caught.
EngineCrashHandler: Signal=11
Segmentation fault (core dumped)
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ atlasmanager start            Running command 'start' for instance 'A1'
The server is starting...
The server is now running, and should be up within 10 minutes
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ atlasmanager start
Running command 'start' for instance 'A1'
The server is starting...
The server is now running, and should be up within 10 minutes
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ ./ShooterGameServer start
Using binned.
4.5.1-0+UE4 7038 3077 410 10
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
Setting breakpad minidump AppID = 834910
Signal 11 caught.
EngineCrashHandler: Signal=11
Segmentation fault (core dumped)
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ atlasmanager redis-stop
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Could not connect to Redis at 127.0.0.1:6379: Connection refused
Command sent to stop Redis.
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ atlasmanager redis-status
 Redis DB location: /home/steam/ATLAS/AtlasTools/RedisDatabase/
 Redis config location: /home/steam/ATLAS/AtlasTools/RedisDatabase/redis.conf
 Redis Server running: Yes
 Redis Server PID: 3390
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ atlasmanager redis-status
 Redis Server running: No
steam@sfl-server:~/ATLAS/ShooterGame/Binaries/Linux$ atlasmanager redis-start
Attempting to start the Redis server...
4917:C 01 Jun 2020 14:28:30.318 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
4917:C 01 Jun 2020 14:28:30.318 # Redis version=6.0.4, bits=64, commit=00000000, modified=0, pid=4917, just started
4917:C 01 Jun 2020 14:28:30.319 # Configuration loaded
Command sent to start Redis.

 

Share this post


Link to post
Share on other sites

Does anyone got a good manual for creating an atlas server on CentOS? Or even a script to do so? 😄

 

Share this post


Link to post
Share on other sites

Is there a particularly successful version of Linux to start with?

I am using Debian 10, and didn't get very far with missing legacy DLLs, etc. After installing a few I decided that if I went any further I would lose control of the environment, and the server stability is too important to me, so I reverted them and wiped out Atlas.

What I can do, though, is install it on a virtual machine on a VPN. With that architecture I don't particularly care about security, so I'd be happy installing an outdated version of Linux, whether it's Ubuntu or Debian or whatever. I usually use Debian, but it looks like Ubuntu may be the better choice, so I'll do that - but does anyone have recommendations on what version of Ubuntu would be the easiest to start with?

Share this post


Link to post
Share on other sites

I have the server (from the Boise Quick Start guide) running on an Ubuntu server 20.04 guest.

I can connect to it using the Steam link, but it isn't showing up in the browser, probably because I don't know how to set the "Friendly Name". When I connect to it directly, its name shows as "ATLAS Test", and that and "Tropical Freeport" appear to be the only names the server has.

Any ideas how I set a server name?

I found this in ServerGrid.json.

Edited by Leshe

Share this post


Link to post
Share on other sites

It appears the Linux Server is broken right now.  The latest version of the Linux Server appears to be V517.7 but the Windows server and the client both report V518.7 and the client refuses to connect to the linux server even though it reports it is up and running and listening for connections.  I confirmed by manually checking Steam Depot and verifying I really am on the latest release for linux.

Just as a test I installed a single windows server and was able to spin up an instance that I can connect to using v518.7, however, I need the linux version to get updated to get my real map running again.  Any idea when the linux server will get the updates?

Share this post


Link to post
Share on other sites
23 hours ago, atlas_fred said:

It appears the Linux Server is broken right now.  The latest version of the Linux Server appears to be V517.7 but the Windows server and the client both report V518.7 and the client refuses to connect to the linux server even though it reports it is up and running and listening for connections.  I confirmed by manually checking Steam Depot and verifying I really am on the latest release for linux.

Just as a test I installed a single windows server and was able to spin up an instance that I can connect to using v518.7, however, I need the linux version to get updated to get my real map running again.  Any idea when the linux server will get the updates?

How did you check the server version? I was getting Linux server updates that corresponded to Windows server releases, and assumed that they were pushing out Linux server updates to match the Windows ones. The server failed sometime around build 5941388 which was pushed around the time of v518.6 and I assumed that 5955268 (current) corresponded to 518.7.

If the server wasn't updated, it would make sense if it's failing if the protocols change for 517. Maybe they are rebuilding and pushing out old server code.

I agree that it's currently broken, and I went through a similar procedure to you. I had two Blackwood servers and a 2x2 grid that all failed with the 5955268 update. I created a 1x1 grid under Windows using https://atlas.gamepedia.com/Server_setup. I tested it under Windows, then moved it to Linux and got exactly the same failure as the working servers. It appears to be trying to connect, I see outbound packets to Steam, with Steam occasionally replying (about 1 reply for 2-3 outbound) but of course I have no idea what they're saying, and they never move beyond that state.

Share this post


Link to post
Share on other sites
On 12/15/2020 at 9:13 PM, Leshe said:


If the server wasn't updated, it would make sense if it's failing if the protocols change for 517. Maybe they are rebuilding and pushing out old server code.

 

Later thought: that doesn't work, because before I updated all the servers I compared the traffic of the broken updated server to one of the non-updated ones, and the non-updated one connected fine, so it isn't simply a matter of old code vs. new protocol. After I updated all servers they all failed to connect.

Share this post


Link to post
Share on other sites

Hi.

I'm trying again to run an Atlas grid on our Debian 10 box, but without success (Curl 3/4 incompatibility ...).

Has anyone succeeded in installing an Atlas server in a Docker container? (I'm not an expert for docker...)

Rgs

 

Share this post


Link to post
Share on other sites

Spinning up a docker container with atlas is not the issue... but the version missmatch is!

here is an example of a working Dockerfile:

FROM ubuntu:18.04

# quash warnings
ARG DEBIAN_FRONTEND=noninteractive

# Set some Variables
ENV TZ "Europe/Berlin"

# install atlas-server-tools prerequisites
RUN apt-get update && apt-get upgrade -y \
        && apt-get install -y --no-install-recommends \
        perl-modules \
        curl \
        lsof \
        libc6-i386 \
        lib32gcc1 \
        bzip2 \
        jq \
        bash \
        screen \
        vim \
        unzip \
        tzdata \
        wine-stable \
        xvfb \
        ca-certificates \
        wget \
        findutils \
        coreutils \
        perl \
        rsync \
        sed \
        tar


RUN dpkg --add-architecture i386 \
        && apt-get install -y --no-install-recommends \
        dnsutils \
        net-tools \
        libssl1.0.0 \
        libprotobuf-dev \
        libidn11 \
        librtmp1 \
        libgssapi-krb5-2 \
        libcompress-raw-zlib-perl


RUN useradd -s /bin/bash steam \
        && mkdir -p /home/steam/atlas_map/ \
        && chown -R steam.steam /home/steam/atlas_map


# prepare steamcmd
RUN mkdir -p /home/steam/steamcmd \
        && cd /home/steam/steamcmd \
        && wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz \
        && tar -xf steamcmd_linux.tar.gz \
        && rm steamcmd_linux.tar.gz \
        && chown -R steam.steam /home/steam/steamcmd \
        && su - steam -c "/home/steam/steamcmd/steamcmd.sh +quit"


RUN curl -sL http://git.io/fh4HA | /bin/bash -s steam \
        && apt-get install redis-server -y \
        && mkdir -p /home/steam/Steam \
        && chown -R steam.steam /home/steam/Steam


COPY configs/shell/ /root/
COPY --chown=steam configs/shell/ /home/steam/
COPY entrypoint.sh /entrypoint.sh


COPY --chown=steam configs/map/ /home/steam/atlas_map/
COPY --chown=steam configs/etc/atlasmanager/atlasmanager.cfg /etc/atlasmanager/atlasmanager.cfg 
COPY --chown=steam configs/etc/atlasmanager/instances/main.cfg /etc/atlasmanager/instances/main.cfg 
COPY --chown=steam configs/etc/atlasmanager/instances/instance.cfg /etc/atlasmanager/instances/instance.cfg.example


ENTRYPOINT [ "sh", "/entrypoint.sh" ]

 

I did manage to spin up a 2x2 Grid with this and the servers are listed in my steam server list. But at the current moment (12.07.2021) the linux server has version v524.11 and the game client has v526.9 (rev. 123946), which results in not listing the server in the ingame favorits. And directly connecting via steam server list always results in a Network Failure: "Unable to query server info for invite"

 

 

Share this post


Link to post
Share on other sites

Todays update did elevate the linux server version to build 7031483, but still showing version v524.11, the Client is now at v527.3 (Rev. 124054). Resulting in still not being able to see the Linux server in the ingame server list, or being able to connect to it via steam server list.

 

And FYI: i'm also testing a 2x2 Grid in a Kubernetes cluster, server is running and seen by steam... only issue is -> see above...

Share this post


Link to post
Share on other sites

I am currently having issues setting up an Atlas server.

The version is behind

ATLAS Version: 524.11 (Rev. 123497)

and after it starts up it immediately crashes with a 

> Signal 11 caught.
EngineCrashHandler: Signal=11

 

Edited by Gizmo0320

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

×
×
  • Create New...