Skip to content
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

RA server bootstrap error #13138

Closed
KaoImin opened this issue Aug 29, 2022 · 9 comments
Closed

RA server bootstrap error #13138

KaoImin opened this issue Aug 29, 2022 · 9 comments
Assignees

Comments

@KaoImin
Copy link

KaoImin commented Aug 29, 2022

Type: Bug

When I update the extension to the latest version and reload, the server cannot bootstrap:

INFO [8/29/2022, 3:14:57 PM]: PersistentState: { serverVersion: '0.3.1162' }
INFO [8/29/2022, 3:14:57 PM]: Using server binary at /home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer
ERROR [8/29/2022, 3:14:57 PM]: Bootstrap error [Error: Failed to execute /home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer --version
	at IS (/home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/out/main.js:85:2328)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async kS (/home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/out/main.js:84:1060)
	at async pv (/home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/out/main.js:84:891)
	at async E._activate (/home/user/.vscode-server-insiders/bin/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/api/node/extensionHostProcess.js:85:8224)
	at async E._waitForDepsThenActivate (/home/gao/.vscode-server-insiders/bin/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/api/node/extensionHostProcess.js:85:8166)
	at async E._initialize (/home/user/.vscode-server-insiders/bin/35b971c92d210face8c446a1c6f1e470ad2bcb54/out/vs/workbench/api/node/extensionHostProcess.js:85:7530)]
INFO [8/29/2022, 3:20:12 PM]: Extension version: 0.3.1178

Extension version: 0.3.1178
VS Code version: Code - Insiders 1.71.0-insider (35b971c92d210face8c446a1c6f1e470ad2bcb54, 2022-08-26T05:19:46.020Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2

System Info
Item Value
CPUs AMD Ryzen 9 5900X 12-Core Processor (24 x 4175)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 63.93GB (28.69GB free)
Process Argv
Screen Reader no
VM 0%
Item Value
Remote WSL: Ubuntu
OS Linux x64 5.10.102.1-microsoft-standard-WSL2
CPUs AMD Ryzen 9 5900X 12-Core Processor (24 x 4174)
Memory (System) 31.31GB (28.16GB free)
VM 0%
@bjorn3
Copy link
Member

bjorn3 commented Aug 29, 2022

What does running /home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer --version in WSL output?

@KaoImin
Copy link
Author

KaoImin commented Aug 29, 2022

What does running /home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer --version in WSL output?

/home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer)
/home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/user/.vscode-server-insiders/extensions/rust-lang.rust-analyzer-0.3.1178-linux-x64/server/rust-analyzer)

@bjorn3
Copy link
Member

bjorn3 commented Aug 29, 2022

You need at least glibc 2.29 to run rust-analyzer since recently. You may be able to update your distro running in WSL. If not see #13081 (comment) for how to get use rust-analyzer through rustup, which has the same glibc requirements as the rest of rustc.

@KaoImin
Copy link
Author

KaoImin commented Aug 29, 2022

You need at least glibc 2.29 to run rust-analyzer since recently. You may be able to update your distro running in WSL. If not see #13081 (comment) for how to get use rust-analyzer through rustup, which has the same glibc requirements as the rest of rustc.

I have already updated glibc to 2.35, but the problem still occurs.

ldd (GNU libc) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

@michidk
Copy link

michidk commented Aug 30, 2022

Same issue when using the vscode version 1.70.2 and the official Microsoft rust-postgres devcontainer (EDIT: using debian buster).

INFO [8/30/2022, 12:25:32 PM]: PersistentState: { serverVersion: '0.3.1186' }
INFO [8/30/2022, 12:25:32 PM]: Using server binary at /home/vscode/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1186-linux-x64/server/rust-analyzer
ERROR [8/30/2022, 12:25:32 PM]: Bootstrap error [Error: Failed to execute /home/vscode/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1186-linux-x64/server/rust-analyzer --version
	at OS (/home/vscode/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1186-linux-x64/out/main.js:85:2328)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async xS (/home/vscode/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1186-linux-x64/out/main.js:84:1220)
	at async fv (/home/vscode/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1186-linux-x64/out/main.js:84:891)
	at async v._activate (/vscode/vscode-server/bin/linux-x64/e4503b30fc78200f846c62cf8091b76ff5547662/out/vs/workbench/api/node/extensionHostProcess.js:85:8180)
	at async v._waitForDepsThenActivate (/vscode/vscode-server/bin/linux-x64/e4503b30fc78200f846c62cf8091b76ff5547662/out/vs/workbench/api/node/extensionHostProcess.js:85:8122)
	at async v._initialize (/vscode/vscode-server/bin/linux-x64/e4503b30fc78200f846c62cf8091b76ff5547662/out/vs/workbench/api/node/extensionHostProcess.js:85:7486)]

Devcontainer: https://github.com/microsoft/vscode-dev-containers/tree/v0.245.0/containers/rust-postgres
Happens with the latest pre-release and release version available from the extension store.

You need at least glibc 2.29 to run rust-analyzer since recently. You may be able to update your distro running in WSL. If not see #13081 (comment) for how to get use rust-analyzer through rustup, which has the same glibc requirements as the rest of rustic.

The fix mentioned in the comment (using the rust-analyzer via rustup) worked for me. However the path was:

{
    "rust-analyzer.server.path": "/usr/local/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rust-analyzer"
}

@lnicola
Copy link
Member

lnicola commented Aug 30, 2022

@michidk Bullseye has GLIBC 2.31, so it should work. Are you sure your container is not based on an older version of Debian, like Buster?

@lnicola
Copy link
Member

lnicola commented Aug 30, 2022

@KaoImin how did you install GLIBC 2.35?

@michidk
Copy link

michidk commented Aug 30, 2022

@michidk Bullseye has GLIBC 2.31, so it should work. Are you sure your container is not based on an older version of Debian, like Buster?

You are right. The dockerfile set it to bullseye but the docker-compose file overwrote it with buster.
With bullseye (or the fix to override the path) everything works fine.

vscode ➜ /workspace (main ✗) $ ldd --version
ldd (Debian GLIBC 2.31-13+deb11u3) 2.31
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

@lnicola lnicola self-assigned this Sep 7, 2022
@lnicola
Copy link
Member

lnicola commented Sep 12, 2022

Presumably fixed in #13214.

@lnicola lnicola closed this as completed Sep 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants