How do I?

User Tools

Site Tools

You are here: start » techstaff » vscode
techstaff:vscode

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
techstaff:vscode [2021/03/11 11:22] – kauffmantechstaff: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.  ''%%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 ''%%linux5%%''.+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%%''.
  
-In this case, VS Code has started its server process for you on three of our login servers concurrently: ''%%linux1%%'', ''%%linux4%%'', and ''%%linux5%%''. This can cause problems with VS Code, including a situation in which it just repeatedly prompts for a password, preventing you from connecting.  (This appears to be what you're experiencing.)  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.+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 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.
  
 <code> <code>
-ssh cnetid@linuxN.cs.uchicago.edu+ssh cnetid@focalN.cs.uchicago.edu
 </code> </code>
  
-To fix this on your own, 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, I'd also recommend removing 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.) We've also recently created a script called ''%%cleanup-vscode%%'' which you can run on any of the servers (when connected directly using SSH) which will walk you through this process.+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, which means it'll be less likely that you'll accidentally end up trying to run this on two servers at the same time. I'd 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.+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.
  
  
Line 32: Line 32:
 ssh cnetid@linux.cs.uchicago.edu ssh cnetid@linux.cs.uchicago.edu
 </code> </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 * .??*%%''.     - 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.     - 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.
Line 44: Line 44:
  
  
 +https://code.visualstudio.com/docs/remote/troubleshooting#_improving-security-on-multi-user-servers 
 +https://code.visualstudio.com/docs/remote/ssh
/var/lib/dokuwiki/data/attic/techstaff/vscode.1615483361.txt.gz · Last modified: 2021/03/11 11:22 by kauffman
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki