search

Didstopia / satisfactory-server

Satisfactory Dedicated Server in a Docker Container
MIT License
12 stars 4 forks source link

Install command fails #2

Closed lowfuel closed 2 years ago

lowfuel commented 3 years ago

Describe the bug Steamcmd is hanging. Any ideas?

docker@satisfactory:/steamcmd/satisfactory$ /steamcmd/linux32/steamcmd +runscript /app/install.txt
Redirecting stderr to '/app/Steam/logs/stderr.txt'
src/tier0/threadtools.cpp (4071) : Probably deadlock or failure waiting for thread to initialize.
[ 0%] Checking for available updates...
Thread failed to initialize
src/tier0/threadtools.cpp (4071) : Probably deadlock or failure waiting for thread to initialize.
Thread failed to initialize
CWorkThreadPool::StartWorkThread: Thread creation failed.
Exiting on SPEW_ABORT

Dids commented 3 years ago

What OS and hardware (CPU/cores, memory and storage)?

Additionally, could you paste the full docker run command?

lowfuel commented 3 years ago

Running in Docker on my Synology NAS (Intel quad-core, 8gb RAM, 8tb storage). I think the OS is referred to as DSM 7, though that's probably not helpful to you. I'm not sure what linux it's based on. I'm using their docker interface so I'm not sure how to find the full docker run command, sorry. If there's a way to see that through a docker command I could report back, just let me know.

For what it's worth I was able to use steamcmd with the cm2network/steamcmd docker image, so I know it's possible for steamcmd to work on this machine via docker, just not sure why it's failing to run on your docker. Could be some library is missing?

Thanks much for any help and apologies for being a bit of a newb with all this.

Dids commented 3 years ago

Hmm, can you check to confirm that the CPU is 64-bit? Just to be sure, as I believe cm2network/steamcmd is 32-bit (i386), which may explain it.

Never mind! It's apparently a confirmed bug with steamcmd on some (newer) linux distros. Looking for a fix now and will let you know once that's available.

lowfuel commented 3 years ago

Oh awesome, thanks! (And just to answer your question anyway, it is indeed 64 bit capable.)

Dids commented 3 years ago

Thanks! I was just about to say that it would still be good to know if it's 64-bit or not.

The weird thing here is that this image (and steamcmd) works fine for quite a few people, so this is more of an edge case combined with a bug, so tracking it down might not be as easy as I'd hoped for, since I have no way of testing or reproducing it.

lowfuel commented 3 years ago

Fair enough. I'll keep poking at it too, and if there's anything I can do from my end to help just let me know!

Dids commented 3 years ago

@lowfuel Fixes are live! Feel free to pull the latest version and give it another go.

lowfuel commented 3 years ago

I'll give it a try and let you know! Does the docker hub image update immediately or is it on a schedule?

Dids commented 3 years ago

It starts building as soon as a new commit appears in the repository, but it also builds when the base image is updated, which happens quite often as our base images update automatically when changes such as dependency or security updates are detected.

The actual build doesn't take long, but sometimes there's a queue which can affect the final build time.

lowfuel commented 3 years ago

Well, interestingly this gets farther, but then gets a similar error (and, quite frustratingly, my NAS is unusable afterwards, have to hard reset it). I don't expect you to troubleshoot my NAS or Synology's attempt at providing Docker, but thought I'd post this here just in case it sparks any ideas. For now I will probably hold off on trying to run the container.

----] Installing update...
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching %appname%...
Redirecting stderr to '/app/Steam/logs/stderr.txt'
src/tier0/threadtools.cpp (4071) : Probably deadlock or failure waiting for thread to initialize.
[ 0%] Checking for available updates...
assert_20211029154442_5.dmp[55]: Uploading dump (out-of-process)
/tmp/dumps/assert_20211029154442_5.dmp

Thread failed to initialize
assert_20211029154442_5.dmp[55]: Finished uploading minidump (out-of-process): success = yes

assert_20211029154442_5.dmp[55]: response: CrashID=bp-f314ba3d-240c-4873-b697-cedc12211029

assert_20211029154442_5.dmp[55]: file ''/tmp/dumps/assert_20211029154442_5.dmp'', upload yes: ''CrashID =bp-f314ba3d-240c-4873-b697-cedc12211029''

Dids commented 3 years ago

@lowfuel While researching this I did come across others with a Synology NAS and similar issues, right down to the hard locking that happens when it crashes.

If you're up for one more attempt, there's a new image tag that uses Ubuntu 18.04 (instead of 20.04), which just might be enough to fix it, as there's some known issues with steamcmd and even barely modern linux distros, but these issues have been around for years and there's still no official fix, or even a statement acknowledging them.

Anyway, the new tag is didstopia/satisfactory-server:ubuntu-18.04 and as I was able to replicate the thread locking issues on a different machine/server, I also managed to fix it with this new image, so I'm very hopeful about it fixing your issue as well!

lowfuel commented 3 years ago

Ah! Thanks for looking into it more! I will definitely give it a shot.

Cheers!

lowfuel commented 3 years ago

Just wanted to say thanks, the 18.04 version works perfectly. First try!

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.