techstaff:vscode
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
techstaff:vscode [2021/02/05 14:57] – [VSCode] kauffman | techstaff:vscode [2025/01/13 13:58] (current) – amcguire | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VSCode ====== | ====== VSCode ====== | ||
- | [[https:// | + | * [[https:// |
- | [[https:// | + | |
====== Troubleshooting ====== | ====== Troubleshooting ====== | ||
+ | Techstaff are not experts on VS Code or its proprietary SSH extension, but there are a couple of common problems that we find people encounter when trying to connect. | ||
- | **Techstaff are not experts on VS Code or its proprietary SSH extension, but I can guess what's happening based on what we've seen with other students.** | + | One thing that can prevent your ability to access the servers is if you've used VS Code and logged into more than one of our login servers simultaneously. |
- | This can occur if you've used VS Code and logged into more than one of our login servers. '' | + | Using '' |
- | Using nslookup, dig, host, or another DNS lookup tool, you can see that '' | + | If VS Code has started its server process for you on more than one of our login servers concurrently, this can cause problems, including a situation in which it just repeatedly prompts for a password, preventing |
- | + | ||
- | In this case, VS Code has started its server process for you on two of our login servers concurrently: linux1 and linux2. | + | To try to clear this up you can try to run the script '' |
- | result in the directory '' | + | |
- | + | < | |
- | To try to clear this up for you, I've stopped the VS Code server process which was running | + | ssh cnetid@focalN.cs.uchicago.edu |
- | + | </ | |
- | To help ensure that this doesn' | + | |
- | + | To fix this on your own (without using the script mentioned above), you could simply log into each of the linux.cs servers (using SSH), then the command '' | |
+ | |||
+ | |||
+ | To help ensure that this doesn' | ||
+ | |||
+ | |||
+ | ==== Step by Step ==== | ||
+ | |||
+ | - Open a terminal emulator. On Windows we suggest installing the [[windows: | ||
+ | - You need to ssh into one of our linux servers.< | ||
+ | ssh cnetid@linux.cs.uchicago.edu | ||
+ | </ | ||
+ | - Ensure you are below your quota. Check your quota by running '' | ||
+ | - If you are using all of your quota we usually see that '' | ||
+ | - Assuming it is '' | ||
+ | - Kill all the VS Code server processes on all linux.cs servers. Remember these were caused by using the round robin DNS name of '' | ||
+ | - If you haven' | ||
+ | - The general idea is to ssh into every linux.cs server and kill any VS Code server process | ||
+ | - The techstaff script '' | ||
+ | - Now you'll want to remove the '' | ||
+ | - IFF you found that '' | ||
+ | - You should be able to reconnect with VS Code client now. | ||
+ | |||
+ | |||
+ | https:// | ||
+ | https:// |
/var/lib/dokuwiki/data/attic/techstaff/vscode.1612558671.txt.gz · Last modified: 2021/02/05 14:57 by kauffman