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/03/11 10:14] – [Troubleshooting] kauffman | techstaff:vscode [2025/01/13 13:58] (current) – amcguire | ||
---|---|---|---|
Line 6: | Line 6: | ||
====== Troubleshooting ====== | ====== Troubleshooting ====== | ||
- | Techstaff are not experts on VS Code or its proprietary SSH extension, but we can guess what's happening based on what we've seen with other students. | + | 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. |
- | 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. | + | 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. |
- | Using '' | + | Using '' |
- | In this case, VS Code has started its server process for you on three of our login servers concurrently: '' | + | If VS Code has started its server process for you on more than one of our login servers concurrently, |
To try to clear this up you can try to run the script '' | To try to clear this up you can try to run the script '' | ||
< | < | ||
- | ssh cnetid@linuxN.cs.uchicago.edu | + | ssh cnetid@focalN.cs.uchicago.edu |
</ | </ | ||
- | To fix this on your own, you could simply log into each of the linux.cs servers (using SSH), then the command '' | + | 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' | + | 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 you have running. This command will '' | ||
+ | - 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.1615479297.txt.gz · Last modified: 2021/03/11 10:14 by kauffman