VSCode Remote Server Connection Issue

Question

Hi,

I have an issue with my logging into a remote server on VSCode. It was all fine until last Friday, but on Sartuday, I could not log into the remote server even though I typed in the correct password. After I typed in the password, it said "Opening Remote Server..." at the bottom left corner, and a "Downloading VSCode Server..." message pops up; however, after a while, it will ask me to enter the password again. So, I checked on the pc terminal, but I can connect to remote server fine, and my password is correct. I went to piazza (Q&A community), and there were around two people who had the same issue as me, and they said that their disk quota was full, and that's why they couldn't login, but if you check the image I attached below, it is not full at all. (But, I still deleted some just in case.) I have a CS student, and I have programming assignment (pair project), labs and final coming up, so I really need this to be fixed, and there were also suggestions that I should try reinstalling VSCode, but then now, it shows an error message. I went to the help desk in the CS building today, but it was not helpful either... they said it might be due to plugin update or VSCode configuration issues... (I am not sure if I touched something while I was trying to fix this issue, but I am desperate to be able to login back to the remote.)Thank you so much for your help.

Answer 1

Thank you so much!! I sent them email about it, hope they will get back to us ASAP.

Answer 2

Fingers crossed here. Keep us posted!

Answer 3

I'm having the exact same issue as described above with the following info:

(base) [vsharma@d029 ~]$ free -h

              total        used        free      shared  buff/cache   available

Mem:          1.5Ti       123Gi       1.3Ti       117Mi        10Gi       1.3Ti

Swap:            0B          0B          0B

(base) [vsharma@d029 ~]$ unlimited -a

bash: unlimited: command not found...

(base) [vsharma@d029 ~]$ ulimit -a

core file size          (blocks, -c) unlimited

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 6187536

max locked memory       (kbytes, -l) unlimited

max memory size         (kbytes, -m) 419430400

open files                      (-n) 131072

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) unlimited

cpu time               (seconds, -t) unlimited

max user processes              (-u) 6187536

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

(base) [vsharma@d029 ~]$

My virtual memory seems unlimited so I'm confused on why would I be getting this same issue. For reference I have successfully logged into the compute node that I'm trying to run on with: "(base) Varuns-MacBook-Pro-584:~ varunsharma$ ssh slurm-job-cpu", but the remote ssh extension in VSCode gives me the WASM OOM error exactly as the other user reports.On my login node however there are limits:(base) [vsharma@d002 ~]$ ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 6187530

max locked memory       (kbytes, -l) unlimited

max memory size         (kbytes, -m) unlimited

open files                      (-n) 8192

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) unlimited

cpu time               (seconds, -t) unlimited

max user processes              (-u) 4096

virtual memory          (kbytes, -v) 8388608

file locks                      (-x) unlimited

(base) [vsharma@d002 ~]$ free -h

              total        used        free      shared  buff/cache   available

Mem:          1.5Ti       124Gi       1.2Ti       120Mi       118Gi       1.3Ti

Swap:          15Gi          0B        15Gi

(base) [vsharma@d002 ~]$

Things were working nicely last week, but for some reason things suddenly stopped working and I'm unclear why. Is perhaps this memory issue happening because it is trying to use all this RAM on the login node instead of the compute node?

For reference this is how I'm connecting to the compute node and my specific slurm job via a login node:

Host slurm-job-cpu

    HostName XX.XXX.XX.X #IP address for login node hidden

    User vsharma

    ForwardAgent yes

    RequestTTY force

    # Disable Undici WASM, raise V8 limits, and adopt the Slurm job on the compute node
    # --jobid=9962773 is my slurm job that is running currently on my compute node
    # I've tried setting these WASM memory options to prevent the OOM error but it hasn't helped
    RemoteCommand bash -lc "export UNDICI_DISABLE_WASM=1; export NODE_OPTIONS='--max-old-space-size=8192 --experimental-wasm-max-memory=4096'; srun --export=ALL --jobid=9962773 --pty bash -l"