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

Reopen stuck at "Installing Server" #6019

Closed
chrmarti opened this issue Dec 8, 2021 · 13 comments
Closed

Reopen stuck at "Installing Server" #6019

chrmarti opened this issue Dec 8, 2021 · 13 comments
Assignees
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster

Comments

@chrmarti
Copy link
Contributor

chrmarti commented Dec 8, 2021

Thanks @chrmarti really great work. Pending from long time.

I have below set-up,

  • windows Host (no docker) + ssh key configured
  • aws ec2 ubuntu instance + docker + repo with dev container.

When I reopen the container for some reason the Reopen stuck at "Installing Server" state.
Last log
[22496 ms] Start: Run in container: (dd iflag=fullblock bs=8192 count=6543 2>/dev/null; dd iflag=fullblock bs=3238 count=1 2>/dev/null) | tar --no-same-owner -xz -C /vscode/vscode-server-insiders/bin/linux-x64/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e-insider_1638943187267

At this stage, all my ssh connection to the remote instance, e.g. via putty etc is almost dead. (extremely slow and unresponsive).
But, if I do Remote : Close remote connection then all ssh connections are normal again. This is strange!

PS: I am using a company internal tool for port forwarding and ssh is done at [email protected]:1337

devconnect forward --local-port 1337 --remote-port 22

Update: installation goes through after around 15-20 mins. and now everything is normal again! 👍

Originally posted by @soumroy88 in #2994 (comment)

@niklasvm
Copy link

niklasvm commented Dec 9, 2021

I can confirm I am having exactly the same issue. It started occuring today. Yesterday I was still able to connect without any issues. I have not made any changes or updades to vscode or extensions.

@chrmarti
Copy link
Contributor Author

chrmarti commented Dec 9, 2021

@niklasvm Is this when connecting to an SSH server? Are you using some tool for forwarding the SSH connection like @soumroy88 does?

@soumroy88 Do you have a way to test this without the port forwarder?

@chrmarti chrmarti self-assigned this Dec 9, 2021
@chrmarti chrmarti added containers Issue in vscode-remote containers info-needed Issue requires more information from poster labels Dec 9, 2021
@niklasvm
Copy link

niklasvm commented Dec 9, 2021

@niklasvm Is this when connecting to an SSH server? Are you using some tool for forwarding the SSH connection like @soumroy88 does?

@soumroy88 Do you have a way to test this without the port forwarder?

I am not 100% sure of your first question. I am connecting from Windows via WSL to an EC2 instance running Ubuntu. The container is running on that instance.
I am not using any port warding

@chrmarti
Copy link
Contributor Author

chrmarti commented Dec 9, 2021

@niklasvm Does 'via WSL' mean you have 'Execute in WSL' enabled in the settings? Could you turn that off and retry?
image

@niklasvm
Copy link

niklasvm commented Dec 9, 2021

@niklasvm Does 'via WSL' mean you have 'Execute in WSL' enabled in the settings? Could you turn that off and retry? image

That setting is already disabled

@niklasvm
Copy link

niklasvm commented Dec 9, 2021

I have reinstalled vscode from scratch and am still unable to connect. I am now receiving the same errors as reported in #6023

@niklasvm
Copy link

niklasvm commented Dec 9, 2021

Update: I have rolled back to vscode 1.62.3 and am getting the originaL error again. This is my full container log:

[84690 ms] Remote-Containers 0.205.2 in VS Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247).
[84690 ms] Start: Resolving Remote
[84692 ms] Setting up container: /launch-control_app_1
[84692 ms] Host: ssh://<HOST>
[84693 ms] Start: Run: docker inspect --type container /<APP>
[96031 ms] Start: Check Docker is running
[96032 ms] Start: Run: docker version --format {{.Server.APIVersion}}
[101811 ms] Server API version: 1.40
[101813 ms] Start: Inspecting container
[101813 ms] Start: Run: docker inspect --type container f13ff35a47bd50a5c62c8d210613d0a00522929decf3a79e4cb3a565d7df56d4
[111389 ms] Start: Run in container: /bin/sh
[111405 ms] Start: Run in container: uname -m
[125094 ms] x86_64
[125095 ms] 
[125095 ms] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[125255 ms] NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
[125256 ms] 
[125257 ms] Start: Run in container: cat /etc/passwd
[125420 ms] Start: Run in container: test -d /root/.vscode-server
[125601 ms] 
[125601 ms] 
[125601 ms] Exit code 1
[125602 ms] Start: Run in container: test -d /root/.vscode-remote
[125761 ms] 
[125762 ms] 
[125763 ms] Exit code 1
[125765 ms] Start: Run in container: test ! -f '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[125928 ms] 
[125929 ms] 
[125930 ms] Start: Run in container: cat /root/.vscode-server/data/Machine/settings.json
[126107 ms] 
[126108 ms] cat: /root/.vscode-server/data/Machine/settings.json: No such file or directory
[126108 ms] Exit code 1
[126109 ms] Start: Run in container: test -d /root/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
[126269 ms] 
[126270 ms] 
[126270 ms] Exit code 1
[126271 ms] Installing VS Code Server for commit ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
[126273 ms] Start: Installing VS Code Server
[126273 ms] Start: Run in container: mkdir -p /root/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247_1639046730842
[126439 ms] 
[126439 ms] 
[126557 ms] Start: Run in container: (dd iflag=fullblock bs=8192 count=6547 2>/dev/null; dd iflag=fullblock bs=706 count=1 2>/dev/null) | tar --no-same-owner -xz --strip-components 1 -C /root/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247_1639046730842

@niklasvm
Copy link

niklasvm commented Dec 9, 2021

Another update: The process completed after 26 minutes which seems to be a very long for the last command above to run.

@chrmarti
Copy link
Contributor Author

#6023 should be fixed with Remote-Containers 0.209.4. Can you give that a try? (Connecting with SSH has changed a lot between 0.205.2 and now, but I'm not sure it will affect this issue.)

@github-actions
Copy link

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@lainisourgod
Copy link

I can report this behaviour too

@chrmarti
Copy link
Contributor Author

@meandmymind Could you open a new issue including the Remote-Containers version you are seeing this with and the container log? (F1 > Remote-Containers: Show Container Log)

@lainisourgod
Copy link

@chrmarti unfortunately no because it somehow resolved. maybe other containers version got out, maybe restarting container helped

@github-actions github-actions bot locked and limited conversation to collaborators Feb 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants