4 minutes ago, IppoKun said:

@ich777 Used the unraid console feature and used this command:

 

 

And it didn't get stuck. Weirdly enough it didn't work when I edited out the start-server.sh file to include these flags.

Actually it works, it just that the log viewer doesn't get updated anymore.

10 minutes ago, IppoKun said:

@ich777 Used the unraid console feature and used this command:

Just put:

-batchmode -nographics

in front of it here:

 

This is basically the same and you don't have to do anything with the command line.

11 minutes ago, ich777 said:

Just put:

-batchmode -nographics

in front of it here:

 

This is basically the same and you don't have to do anything with the command line.

 

Yes, for everyone else this is the easier way, I was doing it via shell because I was trying other stuff and it was faster doing it that way 😁

3 hours ago, Pocketpac said:

Oh thats totally fine. I know how hard this stuff is, just wanted to make sure it is on your radar.

Thanks for the heads up.

Fixed, please force a update from the container itself, both stable and experimental will now launch correctly.

34 minutes ago, ich777 said:

Thanks for the heads up.

Fixed, please force a update from the container itself, both stable and experimental will now launch correctly.

Seemed to have fix it, just out of curiosity was it related to the UE5 update?

29 minutes ago, Pocketpac said:

Seemed to have fix it, just out of curiosity was it related to the UE5 update?

Of course it's fixed because I've tried it, both the old version and experimental...

Yes, the binary changed.

I'm running Ich's latest Valheim it was updated yesterday or the day before. I didn't want it to update automatically, but it did. That's on me, of course. My mods don't work with this version. How do I roll it back one version?

Hello,

 

I just updated beam-mp-server and the server went offline. The container stays up, but when you try to open the logs from unraid it closes immediately and the log file won't update so Idk how to find the error normally.

 

But in portainer I see a constant error:

/beamngmp/BeamMP-Server: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

 

Can't tell if it's related. I've tried to do a force update and still same issue.

The Satisfactory docker does not allow you to properly setup a dedicated server on the experimental branch.

 

According to the wiki, you need to set "-beta experimental" in Steam CD.

 

Please see the link here

 

If you add this to the "game parameters" on the docker, nothing happens. 

 

I think its not working because "-beta experimental" needs to be passed in during the "update server" portion of your script for this docker

 

echo "---Update Server---"
if [ "${USERNAME}" == "" ]; then
    if [ "${VALIDATE}" == "true" ]; then
    	echo "---Validating installation---"
        ${STEAMCMD_DIR}/steamcmd.sh \
        +force_install_dir ${SERVER_DIR} \
        +login anonymous \
        +app_update ${GAME_ID} validate \
        +quit
    else
        ${STEAMCMD_DIR}/steamcmd.sh \
        +force_install_dir ${SERVER_DIR} \
        +login anonymous \
        +app_update ${GAME_ID} \
        +quit
    fi

 

-beta experimental needs to be able to be passed into the code block above as a configurable option. 

 

 

I have tested running the dedicated server locally through steam on my gaming PC and it works perfectly on experimental. Its impossible to get the docker server running on experimental for me right now. 

Edited June 14, 20233 yr by DazedAndConfused

1 hour ago, DazedAndConfused said:

If you add this to the "game parameters" on the docker, nothing happens. 

You need to enable validation.

 

1 hour ago, DazedAndConfused said:

I think its not working because "-beta experimental" needs to be passed in during the "update server" portion of your script for this docker

This is working perfectly fine since I‘ve tried it yesterday and another user here was also able to install it fine on hos system and I even updated the container yesterday to be compatible with the new engine:

 

1 hour ago, DazedAndConfused said:

-beta experimental needs to be able to be passed into the code block above as a configurable option.

Pleaee read the description from the variable GAME ID, you just have to append:

-beta experimental

to the GAME ID and it will work just fine.

 

As said above, you have to enable validation for this so that it pulls the update, if validation is not working, like it is the case for some users, try it on a fresh installed container.

4 hours ago, stig said:

I just updated beam-mp-server and the server went offline.

Thank you for the report I will fix that ASAP and report back.

Should be done in an hour or two.

6 hours ago, stig said:

But in portainer I see a constant error:

This is now fixed, please update the container itself.

7 hours ago, FreddyGSanford said:

My mods don't work with this version. How do I roll it back one version?

I think this is not easily possible, I would rather ask the developers from the mods when they will be updated.

Hello, CSGO servers stop working with the last update.

 

LD_LIBRARY_PATH=/serverdata/serverfiles/bin:/serverdata/serverfiles:/serverdata/serverfiles/bin:
Failed to open libtier0.so (/serverdata/serverfiles/bin/libgcc_s.so.1: version `GCC_7.0.0' not found (required by /lib32/libstdc++.so.6))
Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem
Wed Jun 14 10:44:24 AM BST 2023: Server restart in 10 seconds
Updating server using Steam.

7 minutes ago, penalte said:

Hello, CSGO servers stop working with the last update.

 

LD_LIBRARY_PATH=/serverdata/serverfiles/bin:/serverdata/serverfiles:/serverdata/serverfiles/bin:
Failed to open libtier0.so (/serverdata/serverfiles/bin/libgcc_s.so.1: version `GCC_7.0.0' not found (required by /lib32/libstdc++.so.6))
Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem
Wed Jun 14 10:44:24 AM BST 2023: Server restart in 10 seconds
Updating server using Steam.

 

OK csgo ships with an older version of this file "libgcc_s.so.1", deleting it from /bin/ fix it.

thank you.

14 minutes ago, penalte said:

OK csgo ships with an older version of this file "libgcc_s.so.1", deleting it from /bin/ fix it.

Wait, so is there a modification to the container needed?

23 minutes ago, ich777 said:

Wait, so is there a modification to the container needed?

 

I deleted a dependacy that is shiped with csgo in /gameserver/bin/libgcc_s.so.1

54 minutes ago, penalte said:

 

I deleted a dependacy that is shiped with csgo in /gameserver/bin/libgcc_s.so.1

Please don't do that, I will revert the change from the base image. Thank you for the report.

7Days to die experimental A21 server question 

 

I have this option set up for the beta latest  but when i try and run it  i get the below message and the server never loads  but i f i set it to regular "294420"   it works fine but its not Alpha21   any hints on what im doing wrong?

---Prepare Server---
---Moving SaveGameFolder location---
---Savegame location found---
---Moving UserDataFolder location---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

1 minute ago, IzzleDude said:

7Days to die experimental A21 server question 

Please read this post:

 

Fixed  TY

12 hours ago, ich777 said:

This is now fixed, please update the container itself.

Thanks, beammp all good now 👍

Hi, 

 

I am running 2 Satisfactory servers. They both ran update 7 and different saves. Server 1 ran on the default ports, and server 2 ran on the default ports +1 (7778 instead of 7777). 

With the release of update 8 I wanted to try and switch one over to the experimental branch. Unfortunately, the server kept bootlooping. I assumed that I did something wrong and switched it off with the intention of fixing that later and wanting to play the game. I tried booting the server that I didn't touch, but that one was also broken. I then figured out that while I had the servers running on different ports, they were using the same Satisfactory folder in my appdata. Anyway, to fix it, I decided to remove both servers and templates and then install them again. I now can't get the second server to run properly again even though nothing should be changed. 

 

Server 1 is running just fine on the default ports;

 

I can connect to that server and play the game. 

 

I then tried setting up the second server. 

I installed the container. Before installing it, I changed the ports to these values;

I did remove the old ports and then added these as instructed. The server seems to install correctly and boot. The logfile shows that it is tying to use the ports 7777 and 15000 even though I have changed those;

 

The server does not appear online in my game;

 

I checked the port forwarding, and found no issues. These ports have not changed and 2 days ago, both servers were running happily on these ports. I have been trying to get this to work again, but don't know what I can try. Everything seems to be as it was before. 

 

Does anyone know how to fix this?

12 minutes ago, workermaster said:

Unfortunately, the server kept bootlooping

Please update the container itself.

I pushed a update to the container yesterday to make it compatible with update 8

 

I tested both the stable and experimental branch and both are working fine on my server.

 

15 minutes ago, workermaster said:

I then tried setting up the second server. 

I installed the container. Before installing it, I changed the ports to these values;

Did you also change them in the config?

5 minutes ago, ich777 said:

Please update the container itself.

I pushed a update to the container yesterday to make it compatible with update 8

 

I tested both the stable and experimental branch and both are working fine on my server.

 

Did you also change them in the config?

U have updated the containers and am trying to boot into the experimental one in a few minutes. My game is now updating on Steam. 

 

What config file do I need to change? I am now scrolling through the Satisfactory folder in my appdata looking for config files. The only one that I have found now is the serverconfig. But if I open that with Notepad++, it only shows me weird data. 

 

I don't remember chaning a config file before, but it could be that I just forgot what I did back then

Edited June 14, 20233 yr by workermaster