Differences

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

--- techstaff:vscode [2021/03/11 10:15] – [Troubleshooting] kauffman
+++ techstaff:vscode [2021/03/11 14:09] – kauffman
@@ Line 24: / Line 24: @@
 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.
+==== Step by Step ====
+  - Open a terminal emulator. On Windows we suggest installing the [[windows:subsystemforlinux|Windows Subsystem for Linux]]. On MacOS open Terminal.app.
+  - You need to ssh into one of our linux servers.<code>
+ssh cnetid@linux.cs.uchicago.edu
+</code>
+  - Ensure your 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.
+  - Kill all the VS Code server processes on all linux.cs servers. Remember these were caused by using the round robin DNS name of ''%%linux.cs.uchicago.edu%%''.
+    - If you haven't changed the entry in your VS Code client you should do so now such that you specify a specific server. e.g. ''%%linuxN.cs.uchicago.edu%%'' where ''%%N%%'' is a number 1-5.
+    - The general idea is to ssh into every linux.cs server and kill any VS Code server process you have running. This command will ''%%pkill -u <CNETID> node%%'' VS Code server.
+    - The techstaff script ''%%cleanup-vscode%%'' will 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.
+  - Now you'll want to remove the ''%% ~/.vscode-server%%'' directory.
+  - IFF you found that ''%%results.log%%'' was using all of your quota you'll want to delete this now.
+  - You should be able to reconnect with VS Code client now.
+https://code.visualstudio.com/docs/remote/troubleshooting#_improving-security-on-multi-user-servers
+https://code.visualstudio.com/docs/remote/ssh