mmmaxwwwell / space-engineers-dedicated-docker-linux

Space Engineers Dedicated Server running in Docker for Linux
MIT License
177 stars 43 forks source link

Find missing dependencies for non debian based distros #29

Open ransompolley opened 3 years ago

ransompolley commented 3 years ago

Hello, I have recently been experimenting with Linux on a less-than-adequate machine I had lying around for the sole purposes of learning and doing test runs before attempting to switch over my current machines (servers) from windows. I have been running said windows servers for a little over a year now so I'm still somewhat new to the server management world, and I have been wanting to switch them to Linux very much lately. This is all mostly to say that although I have some experience daily driving Linux desktop, this could also be my own inexperience as the issue. Also keep in mind this is for the most part my first dealings with docker.

To start off, I have all detailed prerequisites installed and updated on the host machine, running EndeavourOS (arch-based). I have installed using ./start last night and immediately stopped it once it was all finished and turned off the machine since it was late and I was heading off for the night. Today I run the same ./start and it seems to be up and running, although when trying to connect from my space engineers client it continues to "retry" the connection, always ending up failing. This is on LAN so port-forwarding should not be the issue, as well as my client sees that it is running on star system world type, either that or the default name.

I had a look at the logs, and it seems as though the server crashes and restarts. Not only does it give a "crash-looking" message at the end with error code 137 (not one of the 3 listed error-codes), but it also detaches the docker log immediately after. At this point docker ps shows that the container is still active, so when I reattach with docker logs -t -f space-engineers-dedicated-docker-linux it will just re-paste the logs so far from the current server restart, which essentially is just another copy of exactly what it showed the first time. It will inevitably reach that same last message and detach the log to continue the cycle.

Here is the section of logs that is repeated

If any more info is required I'd be happy to provide, but I may need a bit of help on where exactly to look for them. Many thanks, -Ran

mmmaxwwwell commented 2 years ago

Looking at the logs you posted, this jumps out as me: 2021-11-10T23:29:50.162719952Z 2021-11-10 23:29:50.162: Peer2Peer_ConnectionFailed [007...508], Timeout

I think a debian based install is required for the host system, I haven't really tested anything other than ubuntu. I have had anecdotal reports of similar errors happening on slackware(not debian based).

Open to suggestions to improve compatibility, but I'm a ubuntu running pleb, so I'm not sure how to attack this one.

BaIthamel commented 2 years ago

line 15 2021-11-10T23:28:41.489216081Z /entrypoint-space_engineers.bash: line 3: /home/wine/.bash_profile: No such file or directory you are explicitly sourcing the .bash_profile yet it does not exist. Why?

mmmaxwwwell commented 2 years ago

I was using it to set the PATH variable, but it's not needed any longer

yochrisbolton commented 2 years ago

Hello,

Anecdotal but I have this successfully running in an alpine container hosted on a large Proxmox machine: Proxmox -> Alpine -> Docker (space engineers)

No changes, worked out of the gate.

In your logs OP, these two lines stand out to me:

2021-11-10T23:29:57.541377253Z 2021-11-10 23:29:57.541: Experimental mode: Yes
2021-11-10T23:29:57.541714519Z 2021-11-10 23:29:57.541: Experimental mode reason: InsufficientHardware

I'm unfamiliar with how space engineers is architect, but based on that second line it sounds like your hardware may be the issue here. Those two lines make me feel like the following statement is true:

This is just a guess. Do you have another machine (real or virtual) that you can try and run this on to verify if its Operating System error or hardware? That should help you narrow down the issues