Closed Fydon closed 3 years ago
WhoisDonlee
commented
3 years ago I had a similar problem earlier today. You can SSH by terminal and delete the lock file.
> Acquiring lock on /home/ubuntu/.vscode-server-insiders/bin/c28c86fcd12e4f8693d65
> 69deadfc740dcf8f55b/vscode-remote-lock.ubuntu.c28c86fcd12e4f8693d6569deadfc740dc
> f8f55bThis worked for me.
Fydon
commented
3 years ago @WhoisDonlee Thank you for trying to help. In the above log it times out at 11:24:52.122. Then it actually attempts to connect and acquire the lock at 11:24:58.341, which is does successfully. However I did try deleting the lock file and bin folder and it didn't make a difference. I have a number of remote servers and can't connect to them either due to the same error.
munael
commented
3 years ago This started happening to me as well once I updated to VSCode 1.61 . Except it never manages to connect. I did the update an hour or so ago and it just killed all momentum. Now looking into how to rollback an update.
ayush-j
commented
3 years ago Same issue. My SSH setup was working fine till yesterday but I'm not able to connect using VS Code today (ssh connections outside VS Code still work).
Version: 1.61.0-insider (user setup)
Commit: c28c86fcd12e4f8693d6569deadfc740dcf8f55b
Date: 2021-09-20T07:28:25.574Z
Electron: 13.4.0
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22463Remote SSH Nightly v2021.9.19620
[13:08:44.295] Log Level: 2
[13:08:44.303] remote-ssh-nightly@2021.9.19620
[13:08:44.303] win32 x64
[13:08:44.332] SSH Resolver called for "ssh-remote+mysshhost", attempt 1
[13:08:44.332] "remote.SSH.useLocalServer": false
[13:08:44.332] "remote.SSH.showLoginTerminal": false
[13:08:44.332] "remote.SSH.remotePlatform": {...}
[13:08:44.332] "remote.SSH.path": undefined
[13:08:44.332] "remote.SSH.configFile": undefined
[13:08:44.332] "remote.SSH.useFlock": true
[13:08:44.333] "remote.SSH.lockfilesInTmp": false
[13:08:44.333] "remote.SSH.localServerDownload": auto
[13:08:44.333] "remote.SSH.remoteServerListenOnSocket": false
[13:08:44.333] "remote.SSH.showLoginTerminal": false
[13:08:44.333] "remote.SSH.defaultExtensions": []
[13:08:44.333] "remote.SSH.loglevel": 2
[13:08:44.334] SSH Resolver called for host: mysshhost
[13:08:44.334] Setting up SSH remote "mysshhost"
[13:08:44.341] Using commit id "c28c86fcd12e4f8693d6569deadfc740dcf8f55b" and quality "insider" for server
[13:08:44.345] Install and start server if needed
[13:08:44.369] Checking ssh with "ssh -V"
[13:08:44.427] > OpenSSH_for_Windows_8.6p1, LibreSSL 3
[13:08:44.427] > .3.3
[13:08:44.434] Remote command length: 6027/8192 characters
[13:08:44.434] Running script with connection command: ssh -T -D 63633 "mysshhost" powershell
[13:08:44.438] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[13:09:01.449] Resolver error: Error: Connecting with SSH timed out
at Function.Timeout (c:\Users\ayjindal\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-nightly-2021.9.19620\out\extension.js:1:397167)
at Timeout._onTimeout (c:\Users\ayjindal\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-nightly-2021.9.19620\out\extension.js:1:488075)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
[13:09:01.453] ------
[13:09:09.003] > Windows PowerShell
> Copyright (C) Microsoft Corporation. All rights reserved.Try the new cross-platform PowerShell https://aka.ms/pscore6]0;C:\WINDOWS\System32\cmd.exePS C:\Users\ayjindal>
> PS C:\Users\ayjindal> $uuid="277ab8837d65"
> PS C:\Users\ayjindal> "${uuid}: running"
> 277ab8837d65: running
> PS C:\Users\ayjindal> "277ab8837d65: pauseLog"
> 277ab8837d65: pauseLog
[13:09:09.004] Got some output, clearing connection timeout
adamaltmejd
commented
3 years ago Same problem here.
munael
commented
3 years ago The latest Insiders update seems to have fixed it.
[11:24:25.107] Running script with connection command: ssh -T -D 1040 "remote.foo.bar" bash [11:24:25.109] Terminal shell path: C:\Windows\System32\cmd.exe [11:24:52.122] Resolver error: Error: Connecting with SSH timed out at Function.Timeout (c:\Users\username.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:397167) at Timeout._onTimeout (c:\Users\username.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.65.8\out\extension.js:1:488075) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7) [11:24:52.127] ------
[11:24:53.357] > ]0;C:\Windows\System32\cmd.exe [11:24:53.358] Got some output, clearing connection timeout [11:24:58.341] > 84d2fadea731: running
Steps to Reproduce:
Note that it times out and then almost immediately attempts to connect, which is successful.
Increasing the timeout via
remote.SSH.connectTimeoutjust increases the time it takes before it attempts to connect. Settingremote.SSH.useLocalServerto false didn't change anything. I tried usingRemote-SSH: Kill Local Connection Server For Host. Using vscode 1.60 works using the same SSH config. The timeout issue might be similar to #5555 but when that issue was occurring it didn't attempt to connect at all.Does this issue occur when you try this locally?: N/A. It didn't get that far Does this issue occur when you try this locally and all extensions are disabled?: N/A. Disabling all extensions except Remote SSH and trying to remote still fails as above.