-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
RustDesk Server 1.1.13 (Docker) hbbs code 132 crashes #503
Comments
Can't reproduce with arch linux, same docker-compose.yaml, could you provide more informations on your environment? Will it crash if running https://github.com/21pages/rustdesk-server/releases/download/test/hbbs on your host? |
Could you help to debug this problem?
|
Remove all envs for your Also try remove all args for hbbs, like |
Might be related: aptos-labs/aptos-core#1019 After some search, I found multiple results mentioned "CPU Instruction" What is the result when running this? sudo cat /proc/cpuinfo | grep avx |
I have same issue because I'm trying to run it on VPS. Your command @xlionjuan returns nothing, so probably it's not possible to run it on this machine. |
@dimmuboy What is the output of the
|
|
A VPS without AVX support is crazy, I guess some code or dependencies in hbbs utilizes AVX. |
Mine doesn't have it too. 1.1.12 continues to work normally
|
Recommend to ask VPS provider |
Thanks, I decided to migrate to different provider. Contabo looks good fine for me 🙂 |
Sorry to +1, but me too. Noticing that we all have QEMU Virtual CPU. Seems that QEMU guests do not include AVX extension by default. So, this would affect a lot of users who are with VPS providers using this same virtualisation technology. I think it would be nice if rustdesk server does not solely rely on AVX :) In the meantime I've just asked my own VPS provider about AVX support, will see...
|
My VPS provider support was very quick and were able to enable AVX on my instance 👍🏼. I recommend anyone seeing this issue to try contact their VPS provider. |
@navhaxs This is not QEMU's problem, it is all on the provider, without AVX support is not acceptable no matter what. |
@xlionjuan Yeah it is unfortunate. I just mean that you should expect to see many more people also run into this crash due to their VPS provider 🙁 The default QEMU guest CPU config does NOT have AVX https://superuser.com/questions/453786/how-do-i-get-avx-support-in-qemu. I just tested a simple VM on my other Proxmox server, which is also QEMU-based, and can confirm this. Maybe a error message can be added, like how MongoDB does it? That would help future users :) |
Question is, is there a feature that was added in 1.1.13 and above that doesn't work without AVX and is now required? From the releases I see on 1.1.13 just "Version check and refactor hbb_common to share with rustdesk client" and on 1.1.14 "Fix windows crash" |
I'm guessing it is related to Rust lang itself, but I can't sure. |
Describe the bug
After upgrading to latest 1.1.13 server version from docker hub, I get code 132 crashes on hbbs. Reverting to 1.1.12 works around the issue
Describe the environment
docker-compose.yaml: (10.x IP is placeholder)
Docker logs:
Arch Linux host OS on the VPS
The text was updated successfully, but these errors were encountered: