Messages such as Signal 11 caught, Segmentation fault, Exit code: 139, LowLevelFatalError ... IPlatformFilePak.cpp or OODLE ERROR: LZ corruption all mean the same thing: the game process crashed at a low level. These appear most often on Unreal Engine games such as Palworld and ARK: Survival Ascended.
The cause is in the game files or the runtime the server runs on — usually an interrupted or damaged download of the game, or a runtime image that no longer matches the game version. It is not caused by your world, your save data, or a player joining.
Two things that will not help: restoring a backup only restores your world and player data, which are not the broken part; and deleting your server files does not repair the download. Please do not delete anything — you would lose your world without fixing the crash.
Open a ticket and paste the crash lines exactly as they appear in your console. This is fixed from our side by re-validating the game files or moving the server to the correct runtime image, and your save data is kept.
Steam library errors. Lines such as steamclient.so: cannot open shared object file, [S_API FAIL] Tried to access Steam interface ... before SteamAPI_Init succeeded, dlopen failed trying to load, or flock ... LOCK_SH failed. errno = 13 belong to this same group. They mean the game's Steam files did not load correctly.
Despite the wording, these are not something you fix by changing file permissions, and there is no shell access to run permission commands on. Some of these lines (the flock and errno = 13 ones in particular) are harmless and appear on healthy servers too — what matters is whether the server then starts. Open a ticket with the console output and we will re-validate the game files for you.
If you need help with this, please submit a ticket.