eggs
eggs copied to clipboard
pelican-eggs
[Bug]: Satisfactory - Shutdown Procedure
Panel Version
1.11.5
Wings Version
1.11.8
Service
Satisfactory
Modified
No, I did not modify the egg
Expected Behavior
Shutting down, the server saves and completely shuts down (without having to kill)
Actual Behavior
The server ends up hanging on "preparing to exit" forever. i end up having to kill the process.
Steps To Reproduce
- Install server
- create world
- stop the server in the pterodactyl GUI
- Server should hang without actually reporting it is shut down. only option is to "kill"
Install logs
https://pteropaste.com/n98ca0yfjxj3
IIRC, I believe I have the same issue as well, but would have to double check. I think it's a regression with the latest Satisfactory server version, but I'm not positive. If it is, best thing we could do in the meantime is go back to force-quitting the server, but that would not save the world.
i have been in contact with the satisfactory community on discord, and there is someone running the server in a docker container (not through pterodactyl) and he says the world saves and shuts down within 1 minute, so i think double checking would be a good place to start :)
Best of luck, and fingers crossed!
For me it proceeded to run even after hours. Think it was 6h and still running. Kill Button was the only working solution.
Edit: running on unraid in pterodactyl, if that is an helpful information
For me it proceeded to run even after hours. Think it was 6h and still running. Kill Button was the only working solution.
Edit: running on unraid in pterodactyl, if that is an helpful information
Not related to this issue but unraid is not supported by pterodactyl, its kernel is know for having issues with some game engines.
its a know issue with the Server and there is No fix for it. you must kill the server.
cant believe, that ue8 Server stops fine in unraid ;)
the egg has not been updated since this issue right? for me stop/restart works fine with actual version.
Idk about the egg but I know I encounter this issue with the actual version.
No other way to make it work but killing the dedicated server
