Giters

CM2Walki / Squad

Dockerfile for automated build of a Squad gameserver: https://hub.docker.com/r/cm2network/squad/

Home Page:https://CM2.Network

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to start server

razum90 opened this issue · comments

commented

Hey! I was planning to dockerize a Squad server myself when I stumbled over this, very nice.

However when I am starting the server I get a lot of these logs:

[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoaded : OnlineService of type String
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoadedHash1 : OnlineService of type String
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoadedHash2 : OnlineService of type String
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Empty session setting SessionPassword : OnlineServiceAndPing of type String
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,NUMPUBCONN:100 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,NUMPRIVCONN:0 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,MatchTimeout_f:120.000000 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,SEARCHKEYWORDS_s:Custom overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,CurrentModLoadedCount_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,AllModsWhitelisted_b:false overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,PlayerReserveCount_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueueLimit_i:25 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueue_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.17:241][392]LogOnlineSession: Warning: STEAM: Server setting ,ReservedQueue_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoaded : OnlineService of type String
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoadedHash1 : OnlineService of type String
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoadedHash2 : OnlineService of type String
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Empty session setting SessionPassword : OnlineServiceAndPing of type String
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,NUMPUBCONN:100 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,NUMPRIVCONN:0 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,MatchTimeout_f:120.000000 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,SEARCHKEYWORDS_s:Custom overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,CurrentModLoadedCount_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,AllModsWhitelisted_b:false overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,PlayerReserveCount_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueueLimit_i:25 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueue_i:0 overflows Steam SetGameTags call
[2022.04.19-15.59.47:250][887]LogOnlineSession: Warning: STEAM: Server setting ,ReservedQueue_i:0 overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoaded : OnlineService of type String
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoadedHash1 : OnlineService of type String
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoadedHash2 : OnlineService of type String
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Empty session setting SessionPassword : OnlineServiceAndPing of type String
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,NUMPUBCONN:100 overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,NUMPRIVCONN:0 overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,MatchTimeout_f:120.000000 overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,SEARCHKEYWORDS_s:Custom overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,CurrentModLoadedCount_i:0 overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,AllModsWhitelisted_b:false overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,PlayerReserveCount_i:0 overflows Steam SetGameTags call
[2022.04.19-16.00.17:257][379]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueueLimit_i:25 overflows Steam SetGameTags call

Also those:

[2022.04.19-15.50.07:220][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerAmmoCrate1_1 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:220][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerAmmoCrate2 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:220][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerAmmoCrate3 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:220][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerAmmoCrate4 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:220][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerAmmoCrate5 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerRepairStation1 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team1SpawnerRepairStation2 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerAmmoCrate1_3 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerAmmoCrate2 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerAmmoCrate3 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerAmmoCrate4 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerAmmoCrate5 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerRepairStation1 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.07:221][996]LogSquad: ASQDeployableSpawner::TrySpawn : Spawner Team2SpawnerRepairStation2 Deployable was not able to find a matching deployable !
[2022.04.19-15.50.12:050][236]LogSquad: Error: Failed to spawn EquipableItem
[2022.04.19-15.50.12:058][236]LogSkeletalMesh: USkeletalMeshComponent::InitArticulated : Could not find root physics body: '/Game/Maps/Anvil/Gameplay_Layers/Anvil_AAS_v1.Anvil_AAS_v1:PersistentLevel.BP_Arbalet_Kord_Desert_C_2147482365.WeaponMesh1P'
[2022.04.19-15.50.12:058][236]LogSkeletalMesh: USkeletalMeshComponent::InitArticulated : Could not find root physics body: '/Game/Maps/Anvil/Gameplay_Layers/Anvil_AAS_v1.Anvil_AAS_v1:PersistentLevel.BP_Arbalet_Kord_Desert_C_2147482365.WeaponMesh3P'
[2022.04.19-15.50.12:058][236]LogSquad: Error: Failed to spawn EquipableItem
[2022.04.19-15.50.12:058][236]LogSquad: Error: Failed to spawn EquipableItem
[2022.04.19-15.50.12:060][236]LogSkeletalMesh: USkeletalMeshComponent::InitArticulated : Could not find root physics body: '/Game/Maps/Anvil/Gameplay_Layers/Anvil_AAS_v1.Anvil_AAS_v1:PersistentLevel.BP_Arbalet_Kord_Desert_C_2147482343.WeaponMesh1P'
[2022.04.19-15.50.12:060][236]LogSkeletalMesh: USkeletalMeshComponent::InitArticulated : Could not find root physics body: '/Game/Maps/Anvil/Gameplay_Layers/Anvil_AAS_v1.Anvil_AAS_v1:PersistentLevel.BP_Arbalet_Kord_Desert_C_2147482343.WeaponMesh3P'
[2022.04.19-15.50.12:060][236]LogSquad: Error: Failed to spawn EquipableItem
[2022.04.19-15.50.12:060][236]LogSquad: Error: Failed to spawn EquipableItem

And the server does not appear to start (because of this?). High chance that this is not an issue within your repo, but I am giving it a shot anyway since I would have no idea where to report this otherwise.

This is how my docker-compose looks like:

version: '3.9'

services:
  squad:
    image: cm2network/squad
    container_name: squad
    restart: unless-stopped
    network_mode: "host"
    cpuset: "0-3"
    volumes:
      - /data/Squad:/storage/squad/
    environment:
      - PORT=7787
      - QUERYPORT=27165
      - RCONPORT=21114
      - FIXEDMAXPLAYERS=100

Thanks guys.

commented

For error investigation purposes, what's supposed to be stored in the volume you provide? And at what point? Nothing is stored in mine.

commented

Sorry to keep you waiting for so long.

Your internal bind mount mapping is wrong:

    volumes:
      - /data/Squad:/storage/squad/

It should be:

    volumes:
      - /data/Squad:/home/steam/squad-dedicated/

Then the bind mount should be filled correctly. However, this doesn't explain why the server isn't starting, since the game files were instead pulled into the container filesystem, which will still make them work.

When you say "it's not starting" do you mean that the container exits instantly after these logs? Or are you unable to connect?

commented

Hey no worries @CM2Walki, thanks for your answer. Ah, yeah, I fixed that now and can see the files. Great, changing in those files is supported as well, right? Just considering it's written in the docs that files can be changed like this $ docker exec -it squad-dedicated nano /home/steam/squad-dedicated/SquadGame/ServerConfig/Server.cfg

It doesn't exit, but I don't see it in the Custom Browser inside Squad, looking at the logs it's just printing this over and over:

squad | [2022.04.24-15.21.39:411][448]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueueLimit_i:25 overflows Steam SetGameTags call
squad | [2022.04.24-15.21.39:411][448]LogOnlineSession: Warning: STEAM: Server setting ,PublicQueue_i:0 overflows Steam SetGameTags call
squad | [2022.04.24-15.21.39:411][448]LogOnlineSession: Warning: STEAM: Server setting ,ReservedQueue_i:0 overflows Steam SetGameTags call
squad | [2022.04.24-15.22.09:400][942]LogOnlineSession: Warning: STEAM: Empty session setting CurrentModLoaded : OnlineService of type String

I am not sure how to confirm that it's actually running as it should?

commented

Great, changing in those files is supported as well, right? Just considering it's written in the docs that files can be changed like this $ docker exec -it squad-dedicated nano /home/steam/squad-dedicated/SquadGame/ServerConfig/Server.cfg

Yes, this is written like this to also cover the case where the game files are inside the container file system. Since you use a bind mount, you can also just edit the files there and the changes will be present inside the container.

I haven't run this image in some time, so I wouldn't be able to tell you if this is running as intended. Back in the day, when I was operating a licensed server, I usually checked via console if I could connect.

commented

Having the same issue. Did someone figure out what needed to be done for this? I can see my server using the steam server browser, but I can't join it. I triple checked my port forwarding and its good.

version: '3.9'

services:
  squad:
    image: cm2network/squad
    deploy:
      resources:
        limits:
          cpus: '4'
          memory: '10g'
    container_name: squad
    restart: unless-stopped
    volumes:
      - D:\squad-dedicated:/home/steam/squad-dedicated/
    environment:
      - PORT=7787
      - QUERYPORT=27165
      - RCONPORT=21114
      - FIXEDMAXPLAYERS=100
    ports:
      - 7787:7787/tcp
      - 7788:7788/tcp
      - 27165:27165/tcp
      - 27166:27166/tcp
      - 21114:21114/tcp
      - 7787:7787/udp
      - 7788:7788/udp
      - 27165:27165/udp
      - 27166:27166/udp
      - 21114:21114/udp
commented

I would like to ask you, how do I use frp to start this server