-
Notifications
You must be signed in to change notification settings - Fork 135
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
Game server fails to start on Debian #6
Comments
Some more information: Output of ls:
Executed from:
|
I fixed it. I'll make a resolution pull request. Although I'm not sure if it's going to work for other OSs. |
did you execute the server on your host system? I guess your permissions are now all screwed up, but at least it's working :D But if you want you could purge the whole docker stuff again and start fresh. If the issue reappears you could do this troubleshooting:
Does this also crash with a segfault? If it crashes can you install |
Whatever happens inside your docker container should just work. You should not execute the client you placed next to the I suggest you download it all again and start from scratch. |
Yeah. My host machine is down because of a partitioning error I made, but once I figure out how to fix it I'll post the logs. |
This happens because pwn3 has no write access to /opt/pwn3/server/creds, there is a step in the master server shell script where it writes the creds in that file. Sending a pull request to fix this. |
Got a shell in the docker container and ran it with strace, the tail end yielded the following:
|
Hi! So last night I gathered the relevant files from the repository, pwn3 website, and docker to use docker-compose to setup the repository. Running the docker-compose binary doesn't fail, however there is a problem with the setup scripts that causes the game server to fail to boot, and exit with code 139:
The text was updated successfully, but these errors were encountered: