Differences

This shows you the differences between two versions of the page.

--- techstaff:vscode [2021/04/25 00:50] – depersonalized the "troubleshooting" section ctopper
+++ techstaff:vscode [2025/01/13 13:58] (current) – amcguire
@@ Line 8: / Line 8: @@
 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.
+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.  The ''%%linux.cs.uchicago.edu%%'' name maps to a collection of several servers, so when you access that address your computer will pick a login server to use.
-Using ''%%nslookup%%'', ''%%dig%%'', ''%%host%%'', or another DNS lookup tool, you can see that ''%%linux.cs.uchicago.edu%%'' expands to ''%%linux1.cs.uchicago.edu%%'', ''%%linux2.cs.uchicago.edu%%'', and other servers up to ''%%linux7%%''.
+Using ''%%nslookup%%'', ''%%dig%%'', ''%%host%%'', or another DNS lookup tool, you can see that ''%%linux.cs.uchicago.edu%%'' expands to ''%%focal0.cs.uchicago.edu%%'', ''%%focal1.cs.uchicago.edu%%'', and other servers up to ''%%focal7%%''.
 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.
@@ Line 17: / Line 17: @@
 <code>
-ssh cnetid@linuxN.cs.uchicago.edu
+ssh cnetid@focalN.cs.uchicago.edu
 </code>
@@ Line 32: / Line 32: @@
 ssh cnetid@linux.cs.uchicago.edu
 </code>
-  - Ensure your are below your quota. Check your quota by running ''%%csquota%%''.
+  - Ensure you are below your quota. Check your quota by running ''%%csquota%%''.
     - If you are using all of your quota we usually see that ''%%results.log%%'' is the culprit. You can find the file or set of files using up your quota by using the command ''%%du -csh * .??*%%''.
     - Assuming it is ''%%results.log%%'' you 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.