Segmentation fault on dedicated Server after Update 1.0.1.0

After Update 1.0.1.0 our dedicated server casn not sart

Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162 
CommonUnixCrashHandler: Signal=11
[2024.11.28-15.53.37:789][  0]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x00000000000004ea

Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162 
CommonUnixCrashHandler: Signal=11
[2024.11.28-15.53.37:789][  0]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x00000000000004ea

0x00007f30ab3acd47 libFactoryServer-UnixCommonStartup-Linux-Shipping.so!CommonUnixMain(int, char**, int (*)(char16_t const*), void (*)()) [C:/BuildAgent/work/9fc8da665efb5ffd/UE4/Engine/Source/./Runtime/Unix/UnixCommonStartup/Private/UnixCommonStartup.cpp:269]
0x00007f30ab20209b libc.so.6!__libc_start_main(+0xea)
0x0000000000217f09 FactoryServer-Linux-Shipping!_start()

[2024.11.28-15.53.37:792][  0]LogExit: Executing StaticShutdownAfterError
Segmentation fault

0x00007f30ab3acd47 libFactoryServer-UnixCommonStartup-Linux-Shipping.so!CommonUnixMain(int, char**, int (*)(char16_t const*), void (*)()) [C:/BuildAgent/work/9fc8da665efb5ffd/UE4/Engine/Source/./Runtime/Unix/UnixCommonStartup/Private/UnixCommonStartup.cpp:269]
0x00007f30ab20209b libc.so.6!__libc_start_main(+0xea)
0x0000000000217f09 FactoryServer-Linux-Shipping!_start()

[2024.11.28-15.53.37:792][  0]LogExit: Executing StaticShutdownAfterError
Segmentation fault

8 Replies

KrakelLPOP•4w ago

I found the Modular Load Balancers produce the exception. When I deactivate this mod the server starts fine. @SirDigby

SirDigby•4w ago

Yep, it broke from today's update

KrakelLPOP•4w ago

the SMM marked this mod as fixed, but my dedicated server is terminating with the same error 🙂 after the last update check, the server is running now

sjhoward•4w ago

did you reboot the server before connecting? servers can only update mods when they aren't running

KrakelLPOP•4w ago

yes, the server was not running

sjhoward•4w ago

it's working for me >debug

FICSIT-Fred•4w ago

We need more information to help you. Before launching the game again, open the Mod Manager and use the "Generate debug info" option, then send the zip file produced in #help-using-mods. This ensures that your help request won't get buried and forgotten in other, non-help channels! If you need to access older log files, see https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_Logs

KrakelLPOP•4w ago

our server is running! oh there was a "not" on my broken English text, sorry 😦

Gaming

Programming

Segmentation fault on dedicated Server after Update 1.0.1.0