Receiving errors (NoAttachedServer, ENOTCONN) upon opening a connection to VSCode Server

[sirlupusdev]

• VSCode Version: 1.74.3
• Local OS Version: Windows_NT x64 10.0.19045
• Remote OS Version: Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0 x86_64)
• Remote Extension/Connection Type: Server

Steps to Reproduce:

1. Setup VSCode Server through the standalone CLI download
2. Connect to VSCode via tunnel or opening the link in the browser
3. Open any folder (preferably one with a git repo)

• Logs: (Started Tunnel with --verbose flag)

The full log can be found here: https://pastebin.com/Fj9FKrtj

Errors thrown in the log are: Error: Unable to retrieve mac address (unexpected format) [IPC Library: Pty Host] Uncaught Exception: Error: read ENOTCONN

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: No

Notes:

• I am also getting a Resource temporarily unavailable (mostly bash: fork: retry: Resource temporarily unavailable) error when running any commands in an SSH connection (not related to VSCode), terminal inside VSCode. The Server does have enough memory available (at least 15 GB free( and CPU load is low (around 30%).
• When opening the folder, startup commands fail with the following errors: Unable to initialize Git; AggregateError(2) Error: Unable to find git Error: Unable to find git Do note that git is installed, sometimes it gets recognised and sometimes it doesn't. The terminal process failed to launch: A native exception occurred during launch (forkpty(3) failed.). TypeScript language server exited with error. Error message is: spawn /home/wcrd/.vscode-cli/server-stable/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/node EAGAIN
• I also get the error NoAttachedServerError sometimes, mostly when reconnecting to the instance, however this isn't included in this log.
• These errors vary broadly, sometimes the startup works fine, but as soon as I open a terminal or go to the Srouce Control tab, the error messages flood in. I'm not sure what causes this and the logs of VSCode Server or the Tunnel Service don't really help me in resolving this bug/error.

Thank you for your help in advance!

[sirlupusdev]

Correction: When I start the server for the first time, it seems to work fine. However, after I restart the Tunnel Service (and Server) or when I reconnect, I get the errors described above.

[sirlupusdev]

Update:

• I've searched for issues containing the Resource temporarily unavailable and it gave me some regarding the SSH Connection to VSCode. The main issue in those threads seem to be that VSCode Server is spawning too many processes which could explain the error (I'm not sure tho?). This would also explain why my server's doing fine when I haven't established a connection yet, because the tunnel service didn't start any processes. (Issues #6403, #2774). However, my process limit (ulimit -u) exceeds 62000 (and VSCode shouldn't decide to spawn that many processes).

• Additionally, I've found a problem with /tmp/ being filled with VSCode sockets (that are not being used (?) / created a few days ago), which shouldn't happen I assume. (This is also mentioned here: https://github.com/microsoft/vscode-remote-release/issues/6403#issuecomment-1064127918)

I hope this helps in some way

[sirlupusdev]

Another update after some time:

• With the latest release I just downloaded, it doesn't get me past the "Do you accept the terms in the License Agreement?". If I input "yes" there, it won't show any other information.
• From that point, opening a new SSH connection or running commands is no longer possible, trying to open another connection fails with error "end of file".

Let me know if this helps or if you need other information

[connor4312]

Duplicates https://github.com/microsoft/vscode/issues/175878

[sirlupusdev]

Duplicates microsoft/vscode#175878

Mmh, the issue persists, even if I use the release that supposedly fixed the issue, the latest CLI release or insiders build. I can't really apply the patch mentioned in the issue, as VSCode doesn't create the server files anymore. It also doesn't show any other information with --log set to trace.

[connor4312]

The release it's in is not out to stable yet; you'll want to make sure to use Insiders from the machine you're connecting from to get it (or insiders.vscode.dev)

[sirlupusdev]

With the insiders build, I'm now receiving the error [2023-03-25 13:07:38] debug [rpc.0] Serving new connection [2023-03-25 13:07:38] info [rpc.0] Checking /home/user/.vscode-cli/server-insiders/.b9226e1ccc11625bcb42b55efb795e07ee533bb0.log and /home/user/.vscode-cli/server- insiders/.b9226e1ccc11625bcb42b55efb795e07ee533bb0.pid for a running server... thread 'tokio-runtime-worker' panicked at 'The global thread pool has not been initialized.: ThreadPoolBuildError { kind: IOError(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }) }', /home/cloudtest/.cargo/registry/src/github.com-1ecc6299db9ec823/rayon-core-1.9.3/src/registry.rs:170:10 note: run withRUST_BACKTRACE=1environment variable to display a backtrace [2023-03-25 13:07:38] info [rpc.0] Checking /home/user/.vscode-cli/server-insiders/.b9226e1ccc11625bcb42b55efb795e07ee533bb0.log and /home/user/.vscode-cli/server-insiders/.b9226e1ccc11625bcb42b55efb795e07ee533bb0.pid for a running server... thread 'tokio-runtime-worker' panicked at 'The global thread pool has not been initialized.: ThreadPoolBuildError { kind: GlobalPoolAlreadyInitialized }', /home/cloudtest/.cargo/registry/src/github.com-1ecc6299db9ec823/rayon-core-1.9.3/src/registry.rs:170:10

The full log can be found here: https://pastebin.com/h52d6aiP

Upon running the server again, I receive: [2023-03-25 13:13:05] error https://go.microsoft.com/fwlink/?LinkID=533484#vscode ` More info at This machine not meet Visual Studio Code Server's prerequisites, expected either... - find libstdc++.so or ldconfig for GNU environments - find /lib/ld-musl-x86_64.so.1, which is required to run the Visual Studio Code Server in musl environments/remote/linux`

However, apt list --installed libc6 libstdc++6 python-minimal ca-certificates tar shows all packages installed with the right version. (Python and minimal-python are installed on 2.7.15).

[sirlupusdev]

After updating the server machine to Ubuntu 20.04 due to 18.04 LTS dropping support soon, the problem has disappeared all together, at least until now. Thanks for your help.