-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
segmentation fault on start #61
Comments
This looks like a bug with the game, not the server. Check that you have enough resources available to host (5GB+ RAM, reasonably modern CPU) |
My current memory looks like this:
I am also running on an |
Could you try running the |
The |
I'm able to reproduce. Working on a fix now. |
This is now fixed. I had to rollback the change that addresses #57, so I need to rethink that part. |
maybe reopen #57 and close this issue? |
thanks for all the quick work! |
This issue is already closed. |
I'm still getting segfaults with the |
Could you try the following:
Then try running. If it doesn't work, please paste your full Docker command as well as your log :) Ideally in a new issue please! |
Ok, that seems to have fixed it. I think my volume mounts to backup my save files collided with the recent symlinks you added. I cleared that all away and it seems to work now. Thanks again. |
Describe the Bug
whenever the server is started I am getting a segmentation fault of the game. I am unsure if this is due to the image or due to the game server itself.
Your Runtime Command or Docker Compose File
System Specs (please complete the following information):
... taken from
lsb_release -a
Additional Context
The text was updated successfully, but these errors were encountered: