...
If Visual Studio Code has left some related processes running on the login nodes, these may use CPU and prevent you from logging in to Setonix via Visual Studio Code. If you are unable to login to Setonix with Visual Studio Code, instead use a different command line interface such as Terminal to ssh into Setonix. From there you can you can identify any leftover Visual Studio Code processes using the 'ps' command. Leftover Visual Studio Code processed will take the form shown below, where the 40-character hex-string is randomly created for each process.complicate you and other users to log into Setonix. The current solution for this is a bit painful and requires the use of manual investigation/cleaning by users.
To identify Visual Studio Code leftovers, users should execute the ps command together with the grep command acting repeatedly on the output to narrow it down to only those processes owned by the user and related to "vscode":
| Column |
|---|
|
| Code Block |
|---|
| language | bash |
|---|
| theme | DJango |
|---|
| title | Terminal 2. Finding and killing unexpected VS Code processes |
|---|
| $ ps
PID TTY TIME CMD
162952 pts/150 00:00:00 /home/<username> -fea | grep ${USER} | grep -i "vscode" | grep -v "grep"
matilda 236771 1 0 11:55 ? 00:00:00 sh /home/matilda/.vscode-server/bin/fdb98833154679dbaa7af67a5a29fe19e55c2b73/bin/code-server --start-server --host=127.0.0.1 --accept-server-license-terms --enable-remote-auto-shutdown --port=0 --telemetry-level all --connection-token-file /home/matilda/.vscode-server/.fdb98833154679dbaa7af67a5a29fe19e55c2b73.token
matilda 236784 236771 0 11:55 ? 00:00:02 /home/matilda/.vscode-server/bin/fdb98833154679dbaa7af67a5a29fe19e55c2b73/node /home/matilda/.vscode-server/bin/fdb98833154679dbaa7af67a5a29fe19e55c2b73/out/server-main.js --start-server --host=127.0.0.1 --accept-server-license-terms --enable-remote-auto-shutdown --port=0 --telemetry-level all --connection-token-file /home/matilda/.vscode-server/.fdb98833154679dbaa7af67a5a29fe19e55c2b73.token
matilda 237900 236784 99 11:55 ? 02:37:53 /home/matilda/.vscode-server/bin/fdb98833154679dbaa7af67a5a29fe19e55c2b73/node --dns-result-order=ipv4first /home/matilda/.vscode-server/bin/fdb98833154679dbaa7af67a5a29fe19e55c2b73/out/bootstrap-fork --type=extensionHost --transformURIs --useHostProxy=false
matilda 237945 236784 0 11:55 ? 00:00:00 /home/matilda/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06fdb98833154679dbaa7af67a5a29fe19e55c2b73/node
## To kill the process, use
$ node /home/matilda/.vscode-server/bin/fdb98833154679dbaa7af67a5a29fe19e55c2b73/out/bootstrap-fork --type=ptyHost --logsPath /home/matilda/.vscode-server/data/logs/20231003T115510 |
|
Once users confirm that those are indeed only the orphan processes of interest, then they can proceed to kill them by extending the command to select the process ID numbers and pass them to the kill command:
| Column |
|---|
|
| Code Block |
|---|
| language | bash |
|---|
| theme | DJango |
|---|
| title | Terminal 2. Finding and killing unexpected VS Code processes |
|---|
| $ ps -fea | grep ${USER} | grep -i "vscode" | grep -v "grep" | awk '{print $2}' | xargs kill -9
<PID> |
|
We suggest that our users regularly check what processes they have running, and clean up any leftover processes that they know are no longer in use. If you find this still doesn't resolve the issue, you may need to purge the Visual Studio Code directory on Setonix using the following:
...