Clarify platform requirements for 1.86 release

Question

Clarify platform requirements for 1.86 release

dragz opened this issue a year ago · 27 comments

Type: Bug

Try to open a remote connection to an external linux server. It fails in recent VSCode Insiders. (Problem appeared sometime last week approximately) It works correctly in regular VSCode towards the same server.

Server OS: CentOS7

No rush, using regular VSCode until a fix arrives...

VS Code version: Code - Insiders 1.86.0-insider (279872b, 2023-12-18T05:36:59.983Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Connection to 'SSH: hpc2.cc.uit.no' could not be established Refused to connect to unsupported server
Connection to 'SSH: hpc2' could not be established Refused to connect to unsupported server

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on 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_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	15.78GB (1.77GB free)
Process Argv	--crash-reporter-id edc6a085-5f26-4644-aa86-28f4101bded5
Screen Reader	no
VM	0%

Connection to 'SSH: hpc2.cc.uit.no' could not be established Refused to connect to unsupported server

Connection to 'SSH: hpc2' could not be established Refused to connect to unsupported server

Extensions: none

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
py29gd2263:30784851
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
a9j8j154:30646983
showlangstatbar:30737417
fixshowwlkth:30771523
showindicator:30805243
pythongtdpath:30726887
i26e3531:30792625
welcomedialog:30812478
pythonnosmt12:30779711
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
pythonmhint1:30901775
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30902439
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
aa_t_chat:30882232
cp7184t:30925682

Answer 1 · 2023-12-18T16:01:26.000Z

Can you please share your remote SSH logs?

To find logs first click on the View menu at the very top of your computer screen, and then select Output from the dropdown. Finally, select Remote-SSH from the dropdown on the top right of the Output window. Please make sure to provide the entire log as all output is helpful to our debugging.

Answer 2 · 2023-12-18T16:11:09.000Z

Sure here goes:
[17:07:59.381] Log Level: 2
[17:08:00.202] SSH Resolver called for "ssh-remote+hpc2.cc.uit.no", attempt 1
[17:08:00.203] "remote.SSH.useLocalServer": false
[17:08:00.203] "remote.SSH.useExecServer": true
[17:08:00.204] "remote.SSH.showLoginTerminal": false
[17:08:00.204] "remote.SSH.remotePlatform": {"hpc2":"linux","knox.homelan":"linux","knoxpub":"linux","knox":"linux","saga.sigma2.no":"linux","desktop.fram.sigma2.no":"linux","octopi.homelan":"linux","fram.sigma2.no":"linux","jupyttest.westeurope.cloudapp.azure.com":"linux","hpc2.cc.uit.no":"linux","ivy":"linux","192.168.2.135":"linux","roysskypc.azure.uit.no":"linux"}
[17:08:00.205] "remote.SSH.path": C:\Windows\System32\OpenSSH\ssh.exe
[17:08:00.216] "remote.SSH.configFile": C:\Users\roy000.ssh\config
[17:08:00.217] "remote.SSH.useFlock": true
[17:08:00.217] "remote.SSH.lockfilesInTmp": false
[17:08:00.218] "remote.SSH.localServerDownload": auto
[17:08:00.218] "remote.SSH.remoteServerListenOnSocket": false
[17:08:00.219] "remote.SSH.showLoginTerminal": false
[17:08:00.219] "remote.SSH.defaultExtensions": []
[17:08:00.219] "remote.SSH.loglevel": 2
[17:08:00.220] "remote.SSH.enableDynamicForwarding": true
[17:08:00.220] "remote.SSH.enableRemoteCommand": false
[17:08:00.220] "remote.SSH.serverPickPortsFromRange": {}
[17:08:00.221] "remote.SSH.serverInstallPath": {}
[17:08:00.228] VS Code version: 1.86.0-insider
[17:08:00.229] Remote-SSH version: remote-ssh@0.108.2023112915
[17:08:00.229] win32 x64
[17:08:00.244] SSH Resolver called for host: hpc2.cc.uit.no
[17:08:00.244] Setting up SSH remote "hpc2.cc.uit.no"
[17:08:00.273] Using commit id "279872bd965e4030c81129a9bf1ce1710ff7cd55" and quality "insider" for server
[17:08:00.305] Install and start server if needed
[17:08:00.318] Checking ssh with " C:\Windows\System32\OpenSSH\ssh.exe -V"
[17:08:00.325] Got error from ssh: spawn C:\Windows\System32\OpenSSH\ssh.exe ENOENT
[17:08:00.325] The specified path C:\Windows\System32\OpenSSH\ssh.exe is not a valid SSH binary
[17:08:00.326] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[17:08:00.329] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[17:08:00.329] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[17:08:00.332] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[17:08:00.333] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[17:08:00.339] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[17:08:00.340] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[17:08:00.343] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[17:08:00.343] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[17:08:01.527] > OpenSSH_for_Windows_8.6p1, Li
[17:08:01.527] > breSSL 3.4.3

[17:08:01.616] Using SSH config file "C:\Users\roy000.ssh\config"
[17:08:01.617] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 52239 -F "C:\Users\roy000.ssh\config" "hpc2.cc.uit.no" bash
[17:08:01.623] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[17:08:03.909] > 62d9d63810e1: running

Found existing installation at /home/royd/.vscode-server-insiders...
Running ssh connection command... /home/royd/.vscode-server-insiders/code-insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55 command-shell --cli-data-dir /home/royd/.vscode-server-insiders/cli --on-port --require-token 48c1c3b24e0e --parent-process-id 12257 &> "/home/royd/.vscode-server-insiders/.cli.279872bd965e4030c81129a9bf1ce1710ff7cd55.log" < /dev/null
printenv:
XDG_SESSION_ID=49
SELINUX_ROLE_REQUESTED=
SHELL=/bin/bash
SSH_CLIENT=129.242.82.126 52247 22
SELINUX_USE_CURRENT_RANGE=
USER=royd
LS_COLORS=rs=0:di=1;35:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lz=01;31:.xz=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.jpg=01;35:.jpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.axv=01;35:.anx=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.axa=00;36:.�]0;C:\WINDOWS\System32\cmd.exe�
.oga=00;36:.spx=00;36:.xspf=00;36:
SSH_AUTH_SOCK=/tmp/ssh-rWUVKSeHI2/agent.12255
VSCODE_AGENT_FOLDER=/home/royd/.vscode-server-insiders
PATH=/usr/local/bin:/usr/bin:/home/royd/bin
MAIL=/var/mail/royd
PWD=/home/royd
LANG=en_US.UTF-8
SELINUX_LEVEL_REQUESTED=
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
HOME=/home/royd
SHLVL=2
LOGNAME=royd
SSH_CONNECTION=129.242.82.126 52247 129.242.2.38 22
XDG_DATA_DIRS=/home/royd/.local/share/flatpak/exports/share:/var/lib/flatpak
k/exports/share:/usr/local/share:/usr/share
LESSOPEN=||/usr/bin/lesspipe.sh %s
XDG_RUNTIME_DIR=/run/user/1000
_=/usr/bin/printenv
[17:08:03.910] Got some output, clearing connection timeout
[17:08:03.949] > Removing old logfile at /home/royd/.vscode-server-insiders/.cli.279872bd965e4030
0c81129a9bf1ce1710ff7cd55.log
Spawned remote CLI: 12287
[17:08:03.964] >
Waiting for server log...
[17:08:03.983] >
[17:08:03.992] > 62d9d63810e1: start
SSH_AUTH_SOCK==/tmp/ssh-rWUVKSeHI2/agent.12255==
DISPLAY====
listeningOn==127.0.0.1:38035==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==76==
execServerToken==48c1c3b24e0e==
62d9d63810e1: end
[17:08:03.993] Received install output:
SSH_AUTH_SOCK==/tmp/ssh-rWUVKSeHI2/agent.12255==
DISPLAY====
listeningOn==127.0.0.1:38035==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==76==
execServerToken==48c1c3b24e0e==

[17:08:03.993] Remote server is listening on port 38035
[17:08:03.994] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":38035},"osReleaseId":"centos","arch":"x86_64","sshAuthSock":"/tmp/ssh-rWUVKSeHI2/agent.12255","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"48c1c3b24e0e"},"serverStartTime":76,"installUnpackCode":""}
[17:08:04.001] Starting forwarding server. local port 52255 -> socksPort 52239 -> remotePort 38035
[17:08:04.002] Forwarding server listening on port 52255
[17:08:04.003] Waiting for ssh tunnel to be ready
[17:08:04.009] [Forwarding server port 52255] Got connection 0
[17:08:04.011] Tunneled port 38035 to local port 52255
[17:08:04.011] Resolved "ssh-remote+hpc2.cc.uit.no" to "port 52255"
[17:08:04.027] Initizing new exec server for ssh-remote+hpc2.cc.uit.no
[17:08:04.027] Resolving exec server at port 52255
[17:08:04.129] [Forwarding server port 52255] Got connection 1
[17:08:04.219] Exec server for ssh-remote+hpc2.cc.uit.no created and cached
[17:08:04.227] ------

[17:08:04.267] [server] Checking /home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/log.txt and /home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/pid.txt for a running server...
[17:08:04.267] [server] Installing and setting up Visual Studio Code Server...
[17:08:04.268] [server] Server setup complete
[17:08:04.268] [server] Starting server...
[17:08:04.268] [server] Starting server with command... Command { std: "/home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/server/bin/code-server-insiders" "--connection-token=remotessh" "--accept-server-license-terms" "--start-server" "--enable-remote-auto-shutdown" "--socket-path=/tmp/code-insiders-9b50fc9b-d8be-43d9-8f2f-87f9cae600c9", kill_on_drop: false }
[17:08:04.345] [server] *
[17:08:04.345] [server] * Visual Studio Code Server
[17:08:04.345] [server] *
[17:08:04.346] [server] * By using the software, you agree to
[17:08:04.596] [server] [17:08:04]
[17:08:04.640] [server]
[17:08:04.640] [server]
[17:08:04.640] [server]
[17:08:04.641] [server] Error: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/server/node_modules/@vscode/spdlog/build/Release/spdlog.node) [17:08:04.641] [server] at Module._extensions..node (node:internal/modules/cjs/loader:1340:18) [17:08:04.641] [server] at Module.load (node:internal/modules/cjs/loader:1119:32) [17:08:04.641] [server] at Module._load (node:internal/modules/cjs/loader:960:12) [17:08:04.644] [server] Error: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/server/node_modules/@vscode/spdlog/build/Release/spdlog.node)
[17:08:04.644] [server] at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
[17:08:04.644] [server] at Module.load (node:internal/modules/cjs/loader:1119:32)
[17:08:04.645] [server] at Module._load (node:internal/modules/cjs/loader:960:12)
[17:08:04.681] [server] [17:08:04] Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/server/node_modules/vsda/build/Release/vsda.node)
[17:08:04.682] [server] [17:08:04] Extension host agent started.
[17:08:04.682] [server] at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
[17:08:04.682] [server] at Module.load (node:internal/modules/cjs/loader:1119:32)
[17:08:04.779] ------

[17:08:04.779] SSH Resolver called for "ssh-remote+hpc2.cc.uit.no", attempt 2, (Reconnection)
[17:08:04.782] SSH Resolver called for host: hpc2.cc.uit.no
[17:08:04.782] Setting up SSH remote "hpc2.cc.uit.no"
[17:08:04.783] Using commit id "279872bd965e4030c81129a9bf1ce1710ff7cd55" and quality "insider" for server
[17:08:04.787] Install and start server if needed
[17:08:04.796] Checking ssh with " C:\Windows\System32\OpenSSH\ssh.exe -V"
[17:08:04.799] Got error from ssh: spawn C:\Windows\System32\OpenSSH\ssh.exe ENOENT
[17:08:04.800] The specified path C:\Windows\System32\OpenSSH\ssh.exe is not a valid SSH binary
[17:08:04.800] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[17:08:04.803] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[17:08:04.803] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[17:08:04.808] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[17:08:04.808] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[17:08:04.812] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[17:08:04.813] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[17:08:04.815] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[17:08:04.816] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[17:08:05.000] > OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

[17:08:05.019] Using SSH config file "C:\Users\roy000.ssh\config"
[17:08:05.019] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 52239 -F "C:\Users\roy000.ssh\config" "hpc2.cc.uit.no" bash
[17:08:05.022] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[17:08:06.387] > c552a2b4c372: running

Found existing installation at /home/royd/.vscode-server-insiders...
Running ssh connection command... /home/royd/.vscode-server-insiders/code-insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55 command-shell --cli-data-dir /home/royd/.vscode-server-insiders/cli --on-port --require-token a16f8095e995 --parent-process-id 12400 &> "/home/royd/.vscode-server-insiders/.cli.279872bd965e4030c81129a9bf1ce1710ff7cd55.log" < /dev/null
printenv:
�]0;C:\WINDOWS\System32\cmd.exe� XDG_SESSION_ID=51
SELINUX_ROLE_REQUESTED=
SHELL=/bin/bash
SSH_CLIENT=129.242.82.126 52267 22
SELINUX_USE_CURRENT_RANGE=
USER=royd
LS_COLORS=rs=0:di=1;35:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lz=01;31:.xz=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.jpg=01;35:.jpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.axv=01;35:.anx=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.axa=00;36:.
.oga=00;36:.spx=00;36:.xspf=00;36:
SSH_AUTH_SOCK=/tmp/ssh-uWhxwS20Dg/agent.12398
VSCODE_AGENT_FOLDER=/home/royd/.vscode-server-insiders
PATH=/usr/local/bin:/usr/bin:/home/royd/bin
MAIL=/var/mail/royd
PWD=/home/royd
LANG=en_US.UTF-8
SELINUX_LEVEL_REQUESTED=
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
HOME=/home/royd
SHLVL=2
LOGNAME=royd
SSH_CONNECTION=129.242.82.126 52267 129.242.2.38 22
XDG_DATA_DIRS=/home/royd/.local/share/flatpak/exports/share:/var/lib/flatpak
k/exports/share:/usr/local/share:/usr/share
LESSOPEN=||/usr/bin/lesspipe.sh %s
XDG_RUNTIME_DIR=/run/user/1000
_=/usr/bin/printenv
Removing old logfile at /home/royd/.vscode-server-insiders/.cli.279872bd965e4030
0c81129a9bf1ce1710ff7cd55.log
[17:08:06.388] Got some output, clearing connection timeout
[17:08:06.400] >
Spawned remote CLI: 12431
[17:08:06.412] >
[17:08:06.431] > Waiting for server log...
[17:08:06.464] > c552a2b4c372: start
SSH_AUTH_SOCK==/tmp/ssh-uWhxwS20Dg/agent.12398==
DISPLAY====
listeningOn==127.0.0.1:45001==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==71==
execServerToken==a16f8095e995==
c552a2b4c372: end
[17:08:06.465] Received install output:
SSH_AUTH_SOCK==/tmp/ssh-uWhxwS20Dg/agent.12398==
DISPLAY====
listeningOn==127.0.0.1:45001==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==71==
execServerToken==a16f8095e995==

[17:08:06.465] Remote server is listening on port 45001
[17:08:06.465] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":45001},"osReleaseId":"centos","arch":"x86_64","sshAuthSock":"/tmp/ssh-uWhxwS20Dg/agent.12398","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"a16f8095e995"},"serverStartTime":71,"installUnpackCode":""}
[17:08:06.472] Starting forwarding server. local port 52271 -> socksPort 52239 -> remotePort 45001
[17:08:06.477] Forwarding server listening on port 52271
[17:08:06.477] Waiting for ssh tunnel to be ready
[17:08:06.481] [Forwarding server port 52271] Got connection 0
[17:08:06.483] Tunneled port 45001 to local port 52271
[17:08:06.483] Resolved "ssh-remote+hpc2.cc.uit.no" to "port 52271"
[17:08:06.487] >
[17:08:06.492] Verified and reusing cached exec server for ssh-remote+hpc2.cc.uit.no
[17:08:06.494] ------

[17:08:06.630] ------

[17:08:06.630] SSH Resolver called for "ssh-remote+hpc2.cc.uit.no", attempt 3, (Reconnection)
[17:08:06.634] SSH Resolver called for host: hpc2.cc.uit.no
[17:08:06.635] Setting up SSH remote "hpc2.cc.uit.no"
[17:08:06.635] Using commit id "279872bd965e4030c81129a9bf1ce1710ff7cd55" and quality "insider" for server
[17:08:06.639] Install and start server if needed
[17:08:06.644] Checking ssh with " C:\Windows\System32\OpenSSH\ssh.exe -V"
[17:08:06.646] Got error from ssh: spawn C:\Windows\System32\OpenSSH\ssh.exe ENOENT
[17:08:06.647] The specified path C:\Windows\System32\OpenSSH\ssh.exe is not a valid SSH binary
[17:08:06.647] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[17:08:06.668] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[17:08:06.668] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[17:08:06.672] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[17:08:06.673] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[17:08:06.681] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[17:08:06.682] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[17:08:06.689] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[17:08:06.689] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[17:08:07.017] > OpenSSH_for_Win
[17:08:07.017] > dows_8.6
[17:08:07.019] > p1, L
[17:08:07.019] > ibreSSL 3.4.3

[17:08:07.043] Using SSH config file "C:\Users\roy000.ssh\config"
[17:08:07.043] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 52239 -F "C:\Users\roy000.ssh\config" "hpc2.cc.uit.no" bash
[17:08:07.046] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[17:08:08.040] > 90cab8badf38: running

�]0;C:\WINDOWS\System32\cmd.exe�Found existing installation at /home/royd/.vscode-server-insiders...
Running ssh connection command... /home/royd/.vscode-server-insiders/code-insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55 command-shell --cli-data-dir /home/royd/.vscode-server-insiders/cli --on-port --require-token 8a8e8c7f0bf8 --parent-process-id 12552 &> "/home/royd/.vscode-server-insiders/.cli.279872bd965e4030c81129a9bf1ce1710ff7cd55.log" < /dev/null
printenv:
XDG_SESSION_ID=53
SELINUX_ROLE_REQUESTED=
SHELL=/bin/bash
SSH_CLIENT=129.242.82.126 52277 22
SELINUX_USE_CURRENT_RANGE=
USER=royd
LS_COLORS=rs=0:di=1;35:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lz=01;31:.xz=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.jpg=01;35:.jpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.axv=01;35:.anx=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.axa=00;36:.
[17:08:08.040] Got some output, clearing connection timeout
[17:08:08.053] >
.oga=00;36:.spx=00;36:.xspf=00;36:
SSH_AUTH_SOCK=/tmp/ssh-zja9iB554U/agent.12549
VSCODE_AGENT_FOLDER=/home/royd/.vscode-server-insiders
PATH=/usr/local/bin:/usr/bin:/home/royd/bin
MAIL=/var/mail/royd
PWD=/home/royd
LANG=en_US.UTF-8
SELINUX_LEVEL_REQUESTED=
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
HOME=/home/royd
SHLVL=2
LOGNAME=royd
SSH_CONNECTION=129.242.82.126 52277 129.242.2.38 22
XDG_DATA_DIRS=/home/royd/.local/share/flatpak/exports/share:/var/lib/flatpak
k/exports/share:/usr/local/share:/usr/share
LESSOPEN=||/usr/bin/lesspipe.sh %s
XDG_RUNTIME_DIR=/run/user/1000
_=/usr/bin/printenv
Removing old logfile at /home/royd/.vscode-server-insiders/.cli.279872bd965e4030
0c81129a9bf1ce1710ff7cd55.log
Spawned remote CLI: 12582
[17:08:08.068] >
[17:08:08.087] > Waiting for server log...
[17:08:08.103] >
[17:08:08.112] > 90cab8badf38: start
SSH_AUTH_SOCK==/tmp/ssh-zja9iB554U/agent.12549==
DISPLAY====
listeningOn==127.0.0.1:44167==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==65==
execServerToken==8a8e8c7f0bf8==
90cab8badf38: end
[17:08:08.113] Received install output:
SSH_AUTH_SOCK==/tmp/ssh-zja9iB554U/agent.12549==
DISPLAY====
listeningOn==127.0.0.1:44167==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==65==
execServerToken==8a8e8c7f0bf8==

[17:08:08.113] Remote server is listening on port 44167
[17:08:08.113] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":44167},"osReleaseId":"centos","arch":"x86_64","sshAuthSock":"/tmp/ssh-zja9iB554U/agent.12549","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"8a8e8c7f0bf8"},"serverStartTime":65,"installUnpackCode":""}
[17:08:08.128] >
[17:08:08.132] Starting forwarding server. local port 52284 -> socksPort 52239 -> remotePort 44167
[17:08:08.133] Forwarding server listening on port 52284
[17:08:08.134] Waiting for ssh tunnel to be ready
[17:08:08.135] [Forwarding server port 52284] Got connection 0
[17:08:08.137] Tunneled port 44167 to local port 52284
[17:08:08.137] Resolved "ssh-remote+hpc2.cc.uit.no" to "port 52284"
[17:08:08.148] Verified and reusing cached exec server for ssh-remote+hpc2.cc.uit.no
[17:08:08.150] ------

[17:08:08.260] ------

[17:08:08.260] SSH Resolver called for "ssh-remote+hpc2.cc.uit.no", attempt 4, (Reconnection)
[17:08:08.263] SSH Resolver called for host: hpc2.cc.uit.no
[17:08:08.264] Setting up SSH remote "hpc2.cc.uit.no"
[17:08:08.265] Using commit id "279872bd965e4030c81129a9bf1ce1710ff7cd55" and quality "insider" for server
[17:08:08.269] Install and start server if needed
[17:08:08.273] Checking ssh with " C:\Windows\System32\OpenSSH\ssh.exe -V"
[17:08:08.275] Got error from ssh: spawn C:\Windows\System32\OpenSSH\ssh.exe ENOENT
[17:08:08.275] The specified path C:\Windows\System32\OpenSSH\ssh.exe is not a valid SSH binary
[17:08:08.276] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[17:08:08.279] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[17:08:08.279] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[17:08:08.281] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[17:08:08.282] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[17:08:08.284] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[17:08:08.285] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[17:08:08.287] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[17:08:08.288] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[17:08:08.481] > OpenSSH_for_W
[17:08:08.487] > indows_8.6p1, LibreSSL 3.4.3

[17:08:08.516] Using SSH config file "C:\Users\roy000.ssh\config"
[17:08:08.516] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 52239 -F "C:\Users\roy000.ssh\config" "hpc2.cc.uit.no" bash
[17:08:08.518] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[17:08:10.632] > a96a4917a3ff: running

�]0;C:\WINDOWS\System32\cmd.exe�
[17:08:10.633] Got some output, clearing connection timeout
[17:08:10.822] > Found existing installation at /home/royd/.vscode-server-insiders...
Running ssh connection command... /home/royd/.vscode-server-insiders/code-insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55 command-shell --cli-data-dir /home/royd/.vscode-server-insiders/cli --on-port --require-token e934125a06c3 --parent-process-id 12660 &> "/home/royd/.vscode-server-insiders/.cli.279872bd965e4030c81129a9bf1ce1710ff7cd55.log" < /dev/null
printenv:
[17:08:10.840] > XDG_SESSION_ID=55
SELINUX_ROLE_REQUESTED=
SHELL=/bin/bash
SSH_CLIENT=129.242.82.126 52293 22
SELINUX_USE_CURRENT_RANGE=
USER=royd
LS_COLORS=rs=0:di=1;35:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lz=01;31:.xz=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.jpg=01;35:.jpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.axv=01;35:.anx=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.axa=00;36:.
.oga=00;36:.spx=00;36:.xspf=00;36:
SSH_AUTH_SOCK=/tmp/ssh-RtrhNqWWEH/agent.12659
VSCODE_AGENT_FOLDER=/home/royd/.vscode-server-insiders
PATH=/usr/local/bin:/usr/bin:/home/royd/bin
MAIL=/var/mail/royd
PWD=/home/royd
LANG=en_US.UTF-8
SELINUX_LEVEL_REQUESTED=
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
[17:08:10.867] >
HOME=/home/royd
SHLVL=2
LOGNAME=royd
SSH_CONNECTION=129.242.82.126 52293 129.242.2.38 22
XDG_DATA_DIRS=/home/royd/.local/share/flatpak/exports/share:/var/lib/flatpak
k/exports/share:/usr/local/share:/usr/share
LESSOPEN=||/usr/bin/lesspipe.sh %s
XDG_RUNTIME_DIR=/run/user/1000
_=/usr/bin/printenv
Removing old logfile at /home/royd/.vscode-server-insiders/.cli.279872bd965e4030
0c81129a9bf1ce1710ff7cd55.log
Spawned remote CLI: 12690
[17:08:10.873] >
[17:08:10.905] > Waiting for server log...
a96a4917a3ff: start
SSH_AUTH_SOCK==/tmp/ssh-RtrhNqWWEH/agent.12659==
DISPLAY====
listeningOn==127.0.0.1:46486==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==66==
execServerToken==e934125a06c3==
a96a4917a3ff: end
[17:08:10.906] Received install output:
SSH_AUTH_SOCK==/tmp/ssh-RtrhNqWWEH/agent.12659==
DISPLAY====
listeningOn==127.0.0.1:46486==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==66==
execServerToken==e934125a06c3==

[17:08:10.906] Remote server is listening on port 46486
[17:08:10.906] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":46486},"osReleaseId":"centos","arch":"x86_64","sshAuthSock":"/tmp/ssh-RtrhNqWWEH/agent.12659","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"e934125a06c3"},"serverStartTime":66,"installUnpackCode":""}
[17:08:10.914] Starting forwarding server. local port 52302 -> socksPort 52239 -> remotePort 46486
[17:08:10.916] Forwarding server listening on port 52302
[17:08:10.917] Waiting for ssh tunnel to be ready
[17:08:10.919] [Forwarding server port 52302] Got connection 0
[17:08:10.921] Tunneled port 46486 to local port 52302
[17:08:10.921] Resolved "ssh-remote+hpc2.cc.uit.no" to "port 52302"
[17:08:10.924] >
[17:08:11.005] Verified and reusing cached exec server for ssh-remote+hpc2.cc.uit.no
[17:08:11.007] ------

[17:08:11.079] ------

[17:08:11.079] SSH Resolver called for "ssh-remote+hpc2.cc.uit.no", attempt 5, (Reconnection)
[17:08:11.082] SSH Resolver called for host: hpc2.cc.uit.no
[17:08:11.082] Setting up SSH remote "hpc2.cc.uit.no"
[17:08:11.084] Using commit id "279872bd965e4030c81129a9bf1ce1710ff7cd55" and quality "insider" for server
[17:08:11.087] Install and start server if needed
[17:08:11.090] Checking ssh with " C:\Windows\System32\OpenSSH\ssh.exe -V"
[17:08:11.092] Got error from ssh: spawn C:\Windows\System32\OpenSSH\ssh.exe ENOENT
[17:08:11.092] The specified path C:\Windows\System32\OpenSSH\ssh.exe is not a valid SSH binary
[17:08:11.093] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[17:08:11.095] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[17:08:11.095] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[17:08:11.097] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[17:08:11.098] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[17:08:11.100] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[17:08:11.101] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[17:08:11.103] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[17:08:11.103] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[17:08:11.510] > OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

[17:08:11.530] Using SSH config file "C:\Users\roy000.ssh\config"
[17:08:11.530] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 52239 -F "C:\Users\roy000.ssh\config" "hpc2.cc.uit.no" bash
[17:08:11.536] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[17:08:13.921] > 6952f2acc33c: running

�]0;C:\WINDOWS\System32\cmd.exe�Found existing installation at /home/royd/.vscode-server-insiders...
Running ssh connection command... /home/royd/.vscode-server-insiders/code-insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55 command-shell --cli-data-dir /home/royd/.vscode-server-insiders/cli --on-port --require-token e7d42c6a98f2 --parent-process-id 12776 &> "/home/royd/.vscode-server-insiders/.cli.279872bd965e4030c81129a9bf1ce1710ff7cd55.log" < /dev/null
printenv:
XDG_SESSION_ID=57
SELINUX_ROLE_REQUESTED=
SHELL=/bin/bash
SSH_CLIENT=129.242.82.126 52332 22
SELINUX_USE_CURRENT_RANGE=
USER=royd
LS_COLORS=rs=0:di=1;35:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lz=01;31:.xz=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.jpg=01;35:.jpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.axv=01;35:.anx=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.axa=00;36:.
.oga=00;36:.spx=00;36:.xspf=00;36:
SSH_AUTH_SOCK=/tmp/ssh-APiH5y8FE4/agent.12773
VSCODE_AGENT_FOLDER=/home/royd/.vscode-server-insiders
PATH=/usr/local/bin:/usr/bin:/home/royd/bin
MAIL=/var/mail/royd
PWD=/home/royd
LANG=en_US.UTF-8
SELINUX_LEVEL_REQUESTED=
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
HOME=/home/royd
SHLVL=2
LOGNAME=royd
SSH_CONNECTION=129.242.82.126 52332 129.242.2.38 22
XDG_DATA_DIRS=/home/royd/.local/share/flatpak/exports/share:/var/lib/flatpak
k/exports/share:/usr/local/share:/usr/share
LESSOPEN=||/usr/bin/lesspipe.sh %s
XDG_RUNTIME_DIR=/run/user/1000
_=/usr/bin/printenv
Removing old logfile at /home/royd/.vscode-server-insiders/.cli.279872bd965e4030
0c81129a9bf1ce1710ff7cd55.log
Spawned remote CLI: 12806
Waiting for server log...
6952f2acc33c: start
SSH_AUTH_SOCK==/tmp/ssh-APiH5y8FE4/agent.12773==
DISPLAY====
listeningOn==127.0.0.1:37004==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==65==
execServerToken==e7d42c6a98f2==
6952f2acc33c: end
[17:08:13.922] Got some output, clearing connection timeout
[17:08:13.923] Received install output:
SSH_AUTH_SOCK==/tmp/ssh-APiH5y8FE4/agent.12773==
DISPLAY====
listeningOn==127.0.0.1:37004==
osReleaseId==centos==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==65==
execServerToken==e7d42c6a98f2==

[17:08:13.923] Remote server is listening on port 37004
[17:08:13.923] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":37004},"osReleaseId":"centos","arch":"x86_64","sshAuthSock":"/tmp/ssh-APiH5y8FE4/agent.12773","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"e7d42c6a98f2"},"serverStartTime":65,"installUnpackCode":""}
[17:08:13.960] Starting forwarding server. local port 52338 -> socksPort 52239 -> remotePort 37004
[17:08:13.962] Forwarding server listening on port 52338
[17:08:13.962] Waiting for ssh tunnel to be ready
[17:08:13.963] [Forwarding server port 52338] Got connection 0
[17:08:13.965] Tunneled port 37004 to local port 52338
[17:08:13.965] Resolved "ssh-remote+hpc2.cc.uit.no" to "port 52338"
[17:08:14.003] Verified and reusing cached exec server for ssh-remote+hpc2.cc.uit.no
[17:08:14.005] ------

[17:08:14.596] [server] [17:08:14] [Error: ENOENT: no such file or directory, scandir '/home/royd/.vscode-server-insiders/data/logs'] {
[17:08:14.596] [server] [17:08:14] [Error: ENOENT: no such file or directory, scandir '/home/royd/.vscode-server-insiders/data/logs'] {
[17:08:14.596] [server] [17:08:14] [Error: ENOENT: no such file or directory, scandir '/home/royd/.vscode-server-insiders/data/logs'] {
[17:08:14.596] [server] [17:08:14] [Error: ENOENT: no such file or directory, scandir '/home/royd/.vscode-server-insiders/data/logs'] {
[17:08:14.597] [server] [17:08:14] [Error: ENOENT: no such file or directory, scandir '/home/royd/.vscode-server-insiders/data/logs'] {
[17:08:14.597] [server] errno: -2,
[17:08:14.597] [server] errno: -2,
[17:08:14.597] [server] errno: -2,
[17:08:14.598] [server] errno: -2,
[17:08:14.598] [server] errno: -2,
[17:08:14.598] [server] code: 'ENOENT',
[17:08:14.598] [server] code: 'ENOENT',
[17:08:14.599] [server] code: 'ENOENT',
[17:08:14.599] [server] code: 'ENOENT',
[17:08:14.599] [server] code: 'ENOENT',
[17:08:14.600] [server] syscall: 'scandir',
[17:08:14.600] [server] syscall: 'scandir',
[17:08:14.600] [server] syscall: 'scandir',
[17:08:14.600] [server] syscall: 'scandir',
[17:08:14.600] [server] syscall: 'scandir',
[17:08:17.632] Opening exec server for ssh-remote+hpc2.cc.uit.no
[17:08:17.697] Verified and reusing cached exec server for ssh-remote+hpc2.cc.uit.no

Answer 3 · 2023-12-18T16:21:51.000Z

Ahh, now that I know where to look it appears that the libstdc++ on CentOS is too old for the Node version used in Insiders. From the log:
[17:08:04.641] [server] Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/royd/.vscode-server-insiders/cli/servers/Insiders-279872bd965e4030c81129a9bf1ce1710ff7cd55/server/node_modules/@vscode/spdlog/build/Release/spdlog.node)

I guess I should upgrade my jumphost. Was planning to do that anyway, but there are still a bunch of CentOS7 servers around so you should be prepared for a lot of complaints when this hits regular VSCode.

Answer 4 · 2023-12-18T16:33:33.000Z

This happened in microsoft/vscode-linux-build-agent#43, will confirm what the new versions of everything are so we can update our checkers which would normally give you a nicer alert

Answer 5 · 2023-12-19T13:12:20.000Z

After the latest update, I'm still getting the same errors.

Answer 6 · 2023-12-19T14:05:41.000Z

Confirmed no terminal launching on update:
Version: 1.86.0-insider (Universal)
Commit: a017b12

Answer 7 · 2023-12-19T14:14:57.000Z

Diving into this more, it looks like the breaking change is the new requirement of minimum GLIBC >= 2.28. If this is the intention, then I think we have a bigger problem on our hands. Amazon Linux 2 is bundled with GLIBC v2.26. I'm sure many people use this for development with VS Code, including myself and my colleagues.

Related breaking change: microsoft/vscode-linux-build-agent#41

Related article: https://repost.aws/questions/QUrXOioL46RcCnFGyELJWKLw/glibc-2-27-on-amazon-linux-2#ANEsMHX3NuRr682Bn6t0z5gw

Answer 8 · 2023-12-20T15:28:47.000Z

Can someone explain why this issue is closed if my terminal still wont launch?

Answer 9 · 2023-12-20T15:29:41.000Z

They upped the minimum requirements. Looks like it's not supported anymore.

Answer 10 · 2023-12-20T16:19:32.000Z

Diving into this more, it looks like the breaking change is the new requirement of minimum GLIBC >= 2.28. If this is the intention, then I think we have a bigger problem on our hands. Amazon Linux 2 is bundled with GLIBC v2.26. I'm sure many people use this for development with VS Code, including myself and my colleagues.

Me,too

Answer 11 · 2023-12-20T20:33:51.000Z

I guess I won't be able to use Ubuntu 18 WSL anymore?

Answer 12 · 2023-12-20T20:40:15.000Z

TBD whether Ubuntu 18 and such will be supported for the next release; we're still evaluating:

Upstream Node.js dropped support for these distros starting with v18 nodejs/node#43246, we have been patching in support with our fork of Node.js https://github.com/microsoft/vscode-node/blob/c963a53bad15793454c93add0efaf342ffe1ae74/azure-pipelines.yml#L50-L137. The idea behind this patch is we will provide support as long as we can but no guarantee when it will break also documented in our release notes https://code.visualstudio.com/updates/v1_82#_update-highlights-for-nodejs, starting with Node.js v20 gcc 10 will be used for compilation https://github.com/orgs/nodejs/discussions/45892 which may not work to support GLIBC 2.17, and Electron 29 will depend on Node.js v20.

Answer 13 · 2023-12-20T22:48:23.000Z

TBD whether Ubuntu 18 and such will be supported for the next release; we're still evaluating:

@connor4312 On what timescale would this be decided? Days, weeks, months? I do all my coding on Ubuntu 18.04, so I need to know if I should hold out or get my system set up all over again on a more recent version of Ubuntu

Answer 14 · 2023-12-21T00:03:11.000Z

If the upcoming release of vs code breaks all of Amazon Linux 2, is there an analysis somewhere I can read to better understand the cost/benefits of that large of an impact in loss of support?

Answer 15 · 2023-12-21T01:43:07.000Z

If the upcoming release of vs code breaks all of Amazon Linux 2, is there an analysis somewhere I can read to better understand the cost/benefits of that large of an impact in loss of support?

I agree, more details should be listed out before making such a drastic change. Dropping support on Amazon Linux 2, which I believe many developers are working off remotely, without any notification in advance feels very irresponsible to me. I don't think the issue should be marked as Closed at all, since the new change has caused new problems.

Seeing as how this will cascade onto the next monthly VSCode release, does anyone know what changes are necessary in order for us to get this working again? Or does it mean all developers have to re-setup their virtual machines?

Answer 16 · 2023-12-21T02:37:49.000Z

There was a warning about dropping support for glibc 2.28 in the August release.

Answer 17 · 2023-12-21T02:40:24.000Z

We will share additional details on the GLIBC version bump after the holidays but the gist is that we are aligning our platform requirements to be same as Node.js v18 that is used for our server binaries. Newer requirements will be GLIBC >= 2.28 and GLIBCXX >= 3.4.25 moving forward.

Answer 18 · 2023-12-21T10:36:30.000Z

A workaround is to sideload a newer version of the needed libraries into a non-system location. For instance using conda to install nodejs will pull inn libgcc-ng and libstdcxx-ng. Then putting

export LD_LIBRARY_PATH=$HOME/myenv/lib:$LD_LIBRARY_PATH

into .bashrc makes the remote server work again. (that is, the embedded terminal doesn't seem to work). (~/myenv is the location of my own conda environment).

Answer 19 · 2023-12-21T12:21:10.000Z

If this is really going to be done a useful addition would be to allow the remote extension to search for GLIBC in a non-standard, VSCode-configurable location. In CentOS 7 one could install GLIBC 2.28+ in a non-standard location (which is not totally painless) but I would not want to set LD_LIBRARY_PATH to point to that location generally since it may mess with other things in the system.

Answer 20 · 2023-12-22T03:36:57.000Z

I guess there are some ways to resolve this problem such as supporting old version remote server by plugin and static complie remote server?

Answer 21 · 2024-01-01T18:33:16.000Z

I upgraded from Ubuntu 18 to 22 in order to get around this problem but I'm now realizing I won't be able to use Code on my university's computing cluster (RHEL7)...this is truly a painful change. I agree that facilitating support for GLIBC in a non-standard location would soften the blow. Or even optionally bundling the needed version of GLIBC?

Answer 22 · 2024-01-05T18:49:25.000Z

I totally see the point of using "official" node.js binaries, especially about not using a self-patched version - but has someone from the team considered to just switch to the "official unofficial" binaries (there are some for risc, armv61 longaarch, ...)? While it is explicit marked as experimental and comes with no guarantees - it actually works quite fine.

From node.js 18.6 on there is a new one: x86_64-glibc-217 and of course it works fine. For upcoming electron releases and updated node.js dependency, they can also be used (the newest one is the 21.5 from December 2023).

If this isn't used in the build pipeline (I'd highly suggest to do that as then it will just work for the users as before - get electron upstream, then replace node by the official unofficial glibc-217 one), then it is still usable, but with a one-time manual work as follows (the details may be a bit different as I don't use the MS builds, but it should work the same).

Of course: check the node.js version in the about menu of vscode first, then check for the URL at https://unofficial-builds.nodejs.org/download/release that matches that minor version (taking the newest patchlevel, of course), if it isn't available, then use the one that comes after - 18.6 is the first one.

Steps for the manual fix for remote workspaces (should also work fine with Amazon Linux - it would be nice if someone could check):

try to connect to the machine the first time
there will be an installation and, as shown above, the server won't start as the node binary has a higher glibc dependency
now manually connect to the machine via ssh (for example in the vscode terminal) and do the following:

$ ls -lt ~/.vscod*-server*/bin/*  # get the server version hash
$ VSC_BIN=~/.vscode-server*/bin/08e6c15293922dd53a864bb041be381322fee401  # use the directory/hash seen above
$ $VSC_BIN/node --version  # executable found but execution fails
$ ldd -v $VSC_BIN/node   # some details showing the broken glibc version
$ cd /tmp
$ wget https://unofficial-builds.nodejs.org/download/release/v18.16.1/node-v18.16.1-linux-x64-glibc-217.tar.xz
$ tar -xvf node-v18.16.1-linux-x64-glibc-217.tar.xz
$ cp -p node-v18.16.1-linux-x64-glibc-217/bin/* $VSC_BIN/
$ $VSC_BIN/node --version  # runs
$ ldd -v $VSC_BIN/node   # some details showing the working glibc version
$ cp -pr node-v18.16.1-linux-x64-glibc-217/lib/node_modules $VSC_BIN/  # this may be unnecessary

The resulting server part can even be copied to other machines including RHEL9 and works fine out of the box.

Answer 23 · 2024-01-11T01:21:44.000Z

I tried to make it running on rhel 7 by pointing the correct env variables to a compatible glibc version.
I somewhat managed to get the server to start as well as opening a workspace.
The opened session then partially works (explorer is working, files open, extensions works (at least python does), etc.).

The only major thing not working as far as I can tell is the terminal.
The host-pty somehow tried to load the wrong version of glibc, making it impossible to use the integrated terminal.
The error is the following:

[01:51:40.255] [server] [IPC Library: Pty Host] Loading "node-pty" failed
[01:51:40.255] [server] [IPC Library: Pty Host] Error: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/victor/.vscode-server-insiders/cli/servers/Insiders-fb769554405bee9be16e21ceb0a496bd29126941/server/node_modules/node-pty/build/Release/pty.node)

I suspect the node bootstrap to spawn new processes, not inheriting from the environment. There must be a simple fix for this, but my limited knowledge on node ends there.

EDIT: Before the above-mentioned there is also this error.

[02:34:43.775] [server] [IPC Library: Pty Host] innerError Error: Cannot find module '../build/Debug/pty.node'

I've noticed that .vscode-server-insiders/cli/servers/Insiders-fb769554405bee9be16e21ceb0a496bd29126941/server/node_modules/node-pty/build/ only contains a Release subdir. Symlinking from the Release removes this specific error but does not solve the issue.

PS: Even if those systems are rather old (10 years in rhel 7 case) and going out of support, they still represent a big marketshare when it comes to enterprise infrastructures (which are all in on stability).
Dropping support altogether for these configs is going to result in a lot of people stuck on vscode 1.85 if we can't provide workarounds with newer versions. I hope this version is well tested for stability because I expect quite a number of tickets with this version.

Answer 24 · 2024-02-05T19:12:49.000Z

The irony here is that javascript developers don't even know what specific feature from glibc 2.28 they really need.
My guess is probably none!
You could probably go rebuild all of your dependencies with older glibc.
Please don't try to ship your own glibc, you will screw up unless you know what you're doing.

EDIT: GitMensch in his fantastic post above proved that none of vscode's dependencies require any glibc 2.28 feature. This seems to be a lazy consequence of a build toolchain upgrade on the external project called "node", and is unrelated to vscode's own CI. It's good practice to build everything yourself and not rely on someone else to cook binaries for you.

Answer 25 · 2024-02-06T13:30:21.000Z

$VSC_BIN/node --version

$ ls -lt ~/.vscod*-server*/bin/*  # get the server version hash
$ VSC_BIN=~/.vscode-server*/bin/08e6c15293922dd53a864bb041be381322fee401  # use the directory/hash seen above
$ $VSC_BIN/node --version  # executable found but execution fails
$ ldd -v $VSC_BIN/node   # some details showing the broken glibc version
$ cd /tmp
$ wget https://unofficial-builds.nodejs.org/download/release/v18.16.1/node-v18.16.1-linux-x64-glibc-217.tar.xz
$ tar -xvf node-v18.16.1-linux-x64-glibc-217.tar.xz
$ cp -p node-v18.16.1-linux-x64-glibc-217/bin/* $VSC_BIN/
$ $VSC_BIN/node --version  # runs
$ ldd -v $VSC_BIN/node   # some details showing the working glibc version
$ cp -pr node-v18.16.1-linux-x64-glibc-217/lib/node_modules $VSC_BIN/  # this may be unnecessary

I've tried these steps, and it does create a working $VSC_BIN/node --version returned, but it doesn't fix anything for letting vscode connect to the centos7 host.

however, an easier work around for now is to change the default setting in vscode to update to the latest release (switch off) and install the november release (1_85) which still works with CentOS 7.

Answer 26 · 2024-02-06T14:24:42.000Z

Quote from @isidorn in #203375

Thank you very much for your feedback and thank you for sharing your passion for VS Code and sharing how it is being used to enable various scenarios. We have discussed this more in the VS Code team and we have decided to allow VS Code to connect to an OS that is not supported by VS Code (no support for glibc >= 2.28) for 12 more months.

We hope this will provide the needed time for you and your companies to migrate to newer Linux distributions. VS Code will show the appropriate dialog and banner that you are connecting to an OS that is not supported by VS Code.

The official working solution is to be posted there "when available".

In the meantime you'd need to additional adjust the new version check script: https://github.com/microsoft/vscode/blob/main/resources/server/bin/helpers/check-requirements-linux.sh on the server, before trying to connect.

Answer 27 · 2024-02-06T21:57:54.000Z

I don't understand the answer.
Node's source code doesn't require a new glibc, so it's a matter of improving your CI to build node using an appropriate toolchain to maximise GNU/Linux compatibility.
You could also publish separate repositories for different linux distribution releases if for some reason there's a will to start using new glibc features, but as far as I understand, there's no need.