-
-
Notifications
You must be signed in to change notification settings - Fork 102
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 error. Not starting. Not docker, neither docker-compose #48
Comments
Please identify your Linux distro name & version, Linux kernel version ( |
Hmmm I genuinely have no idea. Have you tried running the server without Docker (following the official guides)? |
I have good news and bad news. The good news is that I can reproduce this exact bug; the bad news is that in every 2 runs of the server in my environment, only 1 will trigger this bug, while all the config, envs, etc. are exactly the same. |
Did you compare both logs, line by line? I see a lot of warnings and other hiccups during the initialisation process, when looking at the provided log. Maybe one problem is only appearing during the faulty startup, when the segmentation fault happens. |
Still no clue on why the segfault happens (I think there are some strange issues in a library which need further investigation); but if you have time, please try the 64-bit version of the server and see if it helps.
|
Can still occasionally reproduce this bug on either x86 and amd64 version. Still no clue on how this is happening... |
Hi, I ran into the same problem today. I initially started everything by default - the server crashed on this error. Added a server token - the container crashed on the same error. Then I added this environment variable Linux 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Architecture: x86_64 |
So, I just found this a couple of days ago but hadn't been able to get it running bc of the exact same issue, even after adding the DST_SERVER_ARCH=amd64 -e variable, but I noticed @Jamesits updated the nightly about 16 hours ago and switched to it and everything has been working perfectly since. I'm currently running it in a Debian VM on Proxmox: VM: Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux |
The text was updated successfully, but these errors were encountered: