[Remote-SSH Bug]: Bug caused by version 1.86.0 #9467
Comments
|
Second this, I restarted vscode and got the |
|
I found you can also downgrade just the Remote-SSH extension itself (through the GUI) when the latest version relies on 1.86.0. I bet it will also fix the problem and will be easier than downgrading the VSCode. (I haven't try it tho)
|
|
I think this is all part of a greater issue mentioned here: microsoft/vscode#203375? |
|
I am facing the same problem, my friends. How can I solve this problem |
|
Downgrading to and staying at |
I attempted to downgrade only the "Remote - SSH" extension from version 0.108.0 to 0.107.1 but it doesn't seem to fix the issue. The only workaround currently would be to downgrade both VSCode from version 1.86.0 to 1.85.2 and the "Remote - SSH" extension from version 0.108.0 to 0.107.1. |
|
Just want to add that I'm using CentOS 7 on my remote machine and I get the same issue. From the docs I saw that they dropped support for CentOS 7 with the January 2024 release. However, CentOS 7 is not end-of-life until June 2024. Having VSCode drop support for a distribution BEFORE it's EOL is kind of concerning... |
|
Dropping support for RHEL7 a few months before EOL was the surprise I didn't need this morning! I managed to downgrade to VS Code 1.85.2 and VS Code Server 0.107.1 by following these steps:
Working out how to stop VS Code from updating itself and the extension was a bit harder than I expected but I'm able to continue connecting to RHEL7 and not have it undo the above steps automatically for me. |
|
I have same problem, I don't really want to downgrade but, I did use previous version. |
|
Same problem on a Mac, from day to day anything not working even down remote extensions, as well with the remote kill the ssh option. Down to 1_85 work good ! |
Couldn't agree more. |
You are the best!!! Many thanks |
No need to downgrade.... here is a workaround. It works for me at least, and hopefully it will work for most.
Et voila ! When the next VS Code update comes (with a new commit-id), you will only have to repeat steps 2 and 3 (doesn't take more than 2 minutes) and you should be good to go. |
|
Same problem. My solution is downgrade to VS Code 1.85 ,and it worked |
|
Looks like glibc and libstdc++ >= 2.28 is required by vscode going forward per the docs here. In my case CentOS 7 ships with 2.7 and I really like CentOS so minimum of 8+(streaming) happy coding ~ |
Not quite, the requirements are glibc >=2.28 and libstdc++ >= 3.4.25, see the prerequisites I was lucky enough that my system meets the libstdc++ requirements. If your doesn't, you can try to generalize the approach for glibc:
Good luck ! Alternatives:
|
Workaround works! Thank you very much! |
I face the same problem too, I done as you said and just disable automatic update and it's worked now. Waiting for new patched version. |
|
I first had this problem on vscode-insiders and vscode was running fine until two days ago when vscode was upgraded to I downgraded to |
|
Definite upvote from here. Looking forward for "non-workaround" solution. |
I tried the following for #!/usr/bin/env sh
#
# Copyright (c) Microsoft Corporation. All rights reserved.
#
case "$1" in
--inspect*) INSPECT="$1"; shift;;
esac
ROOT="$(dirname "$(dirname "$(readlink -f "$0")")")"
export LD_LIBRARY_PATH=/home/hadoop/anaconda3/lib
"$ROOT/node" ${INSPECT:-} "$ROOT/out/server-main.js" "$@" |
Without details of the error message, or details about the result, it's quite hard to say.... Two things that would be useful:
|
|
Yes, there is a difference. If I run (from within the LD_LIBRARY_PATH=/home/hadoop/anaconda3/lib ldd ./bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/nodethen it says
and whereas if I run unset LD_LIBRARY_PATH
ldd ./bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/nodethen it gives
and |
|
That's all looking good.... I'm guessing that if in the same terminal (with |
|
Looking at the log file, just realized it's not complaining about
|
Just stating the obvious, but that's the main issue discussed in this thread (and many other ones....). The new requirement to run vscode-server is glibc >= 2.28 which your system does not meet.... Two options: 1/ Build and install your own glibc as discussed here. That's not hard at all, you don't need to be actively involved a lot, but it will take patience (it's pretty long to build). Or 2/ similarly to what you did for |
|
Thank you David. The statement "instead of using patchelf you can use other mechanisms with a similar effect, for example set LD_LIBRARY_PATH" gave me the impression that I did not need to go the patchelf route, but perhaps I misunderstood. In any case, I upgraded to VSCode version 1.86.1 which gives some breathing room (for 12 months if I understand correctly). |
Just to clarify: using When it comes to |
|
VSCode 1.86.1 "fixes" it by warning you that you are about to use an unsupported OS version. You have to click "Allow" and will still see a warning that you cannot hide, but it seems to work. |
The warning you can't hide is sad. |
can confirm. it is weird to have this warning hanging there while it still works. for the ones using ssh remote we most of them cant upgrade the OS. it would be better if the support can continue. |
|
RHEL7 ELS ends 30 June 2028... We'll be seeing RHEL 7 servers for a few years, not months. Sometimes vscode remoting could actually help with the OS updates, so this is just very, very bad. |
|
unfortunately, same... it doesn't make sense to 'upgrade' a tool if it just disables all your access and/or show undismissable warnings |
|
Hello everyone, I saw the ssh issue in VS code 1.86 is "fixed" according to the comment above . It means we can use ssh remote with old version of glibc now ? |
and others
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServersettingConnect Locally
It connects successfully
->
No response
Expected Behavior
Connect to the remote server
Steps To Reproduce
Open a remote server via Remote-SSH
Remote-SSH Log
Remote-SSH Log
Anything else?
I'm pretty sure this is a problem brought by the update to
1.86.0by 3 control experiments1.86.0. After that I'm no longer able to access the server through Remote-SSH.1.85.sth(the previous version). And it connects just fine through Remote-SSH. And in the same time, I cannot connect to it via my laptop that is on1.86.01.86.0, now the desktop VSCode is not working too.I downgraded for now to fix it.
The text was updated successfully, but these errors were encountered: