Configuration with Satisfactory - Server Uses high CPU

Technical Support
,
1

System Information

Field Value
Operating System Linux - Ubuntu 24.04.2 on x86_64
Product AMP ‘Phobos’ v2.6.2.0 (Mainline)
Virtualization None
Application Satisfactory
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

Somehow there is an issue where the server will see very low usage and then randomly start climbing until it sits at 75-100% CPU utilization until I restart the server again. It causes issues for the server users and seems to be something that has occurred repeatedly.

Reproduction Steps

  • everytime I restart the server, in a few hours, it tends to be using 75% or more of the CPU power of the server.
  • After a few hours or someone logs in, the server spins up cpu use but never spins down until I restart
  • CPU usage returns to low numbers immediately after a restart and stays there for several hours until one of the above things occurs
2

I have the same issue.

This is a known issue with Satisfactory. Basically your port 8888 gets bombed with requests/there is some internal corruption with requests to it.

The solution is to change the port 8888 to something that won’t regularly get hit by botnet scanners. I am actually just trying to solve the same issue, since I can’t find an option to change the ReliablePort.

The easiest fix would be if the CubeCoder guy/dev just changes the ReliablePort to something else by default that is in a way higher port range.

Seems what happens is whenever the server received a TCP:ACK or TCP:SYN packet on this port without it being accompanied by someone joining the server, it would wake up and go into a waiting period indefinitely. couple this several hundred times and now you’ve got a server filled with network threads that are just waiting and eating up CPU power.

Sources:

I hope for a quick reply here aswell :slight_smile: If I indeed can change the port somehow easily please let me know.

Edit: Looking at the GitHub from the AMP Templates you could probably just add some setting ApplicationPort2 in the json?

    {
        "Protocol": "TCP",
        "Port": 8888,
        "Offset": 0,
        "Range": 1,
        "Ref": "ApplicationPort2",
        "Name": "Reliable Port",
        "Description": "Satisfactory Management Port",
        "ChildPorts": null
    },

Something like that and just allow the user to change it :+1:

3

The reliable port is already configured in the template, since several weeks ago. Only new instances created after it was added get it tho