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.
linux.cs.uchicago.edu is actually a collection of several servers, so when you access that address your computer will pick a login server to use.
host, or another DNS lookup tool, you can see that
linux.cs.uchicago.edu expands to
linux2.cs.uchicago.edu, and other servers up to
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 you from connecting. Additionally, this can often result in the directory
~/.vscode-server in your home directory on the server becoming corrupted in some way. Since VS Code will automatically recreate that directory when you reconnect, it's safe to delete it.
To try to clear this up you can try to run the script
cleanup-vscode after sshing into one of the linux servers using Terminal.app, the WSL command line, or a linux terminal.
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
pkill -u <CNETID> node, which will stop any running vscode-server processes. After you've stopped the processes on all the login servers, it is also recommend to remove the
~/.vscode-server directory to ensure that it's recreated when you connect next. (Otherwise, the contents of this directory can cause problems for later reconnect attempts.) To do this, just run
rm -r ~/.vscode-server on any of the linux.cs servers. (Since your home directory is shared, you only need to do this once.)
To help ensure that this doesn't happen again, you will want to configure VS Code to connect to one login server in particular instead of the group. That will ensure that you always reconnect to the same system you used previously. This means it'll be less likely that you'll accidentally end up trying to run this on two or more servers at the same time. We also recommend ensuring that VS Code is completely closed and no longer running on one computer before attempting to start it on a second computer.
results.logis the culprit. You can find the file or set of files using up your quota by using the command
du -csh * .??*.
results.logyou probably don't want to delete it just yet as there is probably a process that still has it open and is still writing to it. Proceed and delete this file at the very end.
Nis a number 1-5.
pkill -u <CNETID> nodeVS Code server.
cleanup-vscodewill walk you through sshing to all nodes and killing the right processes. Feel free to look at the script to see what it is doing.
results.logwas using all of your quota you'll want to delete this now.