Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Satisfactory changed startup parameter on 0.5.0.6 patch #3661

Closed
0xlord opened this issue Nov 3, 2021 · 11 comments · Fixed by #3667
Closed

[BUG] Satisfactory changed startup parameter on 0.5.0.6 patch #3661

0xlord opened this issue Nov 3, 2021 · 11 comments · Fixed by #3667

Comments

@0xlord
Copy link

0xlord commented Nov 3, 2021

User Story

As a server admin, I want to request a change to the sfserver startup command so that it works in an automated way after introducing -multihome parameter as a requirement in patch 0.5.0.6.

Basic info

  • Distro: [Rocky Linux 8.4]
  • Game: [Satisfactory]
  • Command: [start]
  • LinuxGSM version: [v21.4.1]

Further Information

With 0.5.0.6 update tonight CSS introduced -multihome as a server parameter (see wiki entry: https://satisfactory.fandom.com/wiki/Dedicated_servers). I think to address demands to have multiple instances running on the same machine but with different ips. Somehow the server crashes if the parameter is not set and the default settings 0.0.0.0 will apply. Curiousily this only applies to Linux servers. Windows server are not being affected by this. This could make this request obsolete with 0.5.0.7 however. On the other hand it could be beneficial to have this automated workaround to be sure.

I've changed common.cfg to these settings and it works now automatically without specifying the IP:

## Gather IP address for startup parameter
IPADDR=$(ip addr show |grep 'inet '|grep -v 127.0.0.1 |awk '{print $2}'| cut -d/ -f1)

## Server Parameters | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters
startparameters="FactoryGame -multihome=${IPADDR} -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"

To Reproduce

Steps to reproduce the behaviour:

  1. Update the server to 0.5.0.6
  2. Start the server
  3. Try to connect it or open up htop to see that the server is not running
  4. Confirm with ./sfserver details
  5. Change common.cfg like described above
  6. Start the server
  7. Confirm it working via htop or a connection attempt

Expected behaviour

The server will work without any issues again.

@johnoclockdk
Copy link
Contributor

I will fix this tomorrow.

@dgibbs64
Copy link
Member

dgibbs64 commented Nov 3, 2021

Thanks. This will need to be addressed soon. Hopfully they dont need to make too many more changes like this

@johnoclockdk johnoclockdk self-assigned this Nov 3, 2021
@johnoclockdk johnoclockdk added branch conflicts Branch of pr has conflicts that need to be worked on priority Top priority issues and removed branch conflicts Branch of pr has conflicts that need to be worked on labels Nov 3, 2021
@0xlord
Copy link
Author

0xlord commented Nov 4, 2021

Thanks. This will need to be addressed soon. Hopfully they dont need to make too many more changes like this

I have the feeling that we'll see even more changes like this due to the experimental nature of the servers current state. I will try to convince Bogdan to tell us changes like these beforehand so we could bring up fixes like these closer to the release time.

@johnoclockdk
Copy link
Contributor

johnoclockdk commented Nov 4, 2021

i have work on this so you can also set the ip if ya want to but need to figure out how to code it in now

ipaddr="0.0.0.0"

if [ ${ipaddr} = 0.0.0.0 ];
then
multihome=$(ip addr show |grep 'inet '|grep -v 127.0.0.1 |awk '{print $2}'| cut -d/ -f1)
else
multihome="${ipaddr}"
fi
echo "${multihome}"

@h3o66 h3o66 linked a pull request Nov 4, 2021 that will close this issue
13 tasks
@h3o66 h3o66 added this to the v21.4.2 milestone Nov 4, 2021
@0xlord
Copy link
Author

0xlord commented Nov 4, 2021

CSS fixed the Linux Server crash issue. Don't know if -multihome is still required: https://questions.satisfactorygame.com/post/61830560831c852052359b1c

Guess we still could benefit from the PR - just for documentation that the issue was addressed internally at CSS.

@botflakes
Copy link

botflakes commented Nov 23, 2021

CSS added a Parameter today with the release of Update 5 to the Early Access branch. If you are or want to still playing the Experimental Branch, the server needs to be started with -beta experimental otherwise the Client-Server-Version doesn't match and you can't connect.

@h3o66
Copy link
Member

h3o66 commented Nov 23, 2021

CSS added a Parameter today with the release of Update 5 to the Early Access branch. If you are or want to still playing the Experimental Branch, the server needs to be started with -beta experimental otherwise the Client-Server-Version doesn't match and you can't connect.

this is probably only a flag for steamcmd, as this is in the wiki, not for the server itself:
https://satisfactory.fandom.com/wiki/Dedicated_servers#Experimental_Branch_Selection

Edit: the branch can be changed all the time with the following howto:
https://docs.linuxgsm.com/steamcmd/branch

@botflakes
Copy link

CSS added a Parameter today with the release of Update 5 to the Early Access branch. If you are or want to still playing the Experimental Branch, the server needs to be started with -beta experimental otherwise the Client-Server-Version doesn't match and you can't connect.

this is probably only a falg for steamcmd, as this is in the wiki, not for the server itself: https://satisfactory.fandom.com/wiki/Dedicated_servers#Experimental_Branch_Selection

Yeah, should have mentioned it. Maybe make a check if the user wants to install the Early Access Branch or Experimental Branch during installation? Like "Do you want to install the Experimental Branch?" "Y | N"

@0xlord
Copy link
Author

0xlord commented Nov 23, 2021

You can set your branch in the config file. No additional parameters needed.
https://docs.linuxgsm.com/steamcmd/branch

@botflakes
Copy link

oh I see. Thanks!

@h3o66 h3o66 modified the milestones: v21.4.2, v21.5.0 Dec 2, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Jan 1, 2023

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.