Seems bad, can you still login using the DCUI or local shell instead of SSH?
Maybe you shouldn't restart the management agents yet, there's a chance this will fail starting the agents again as well, leaving you with disconnected, completely unmanageable host too.
If you can still login through the local shell then check if it's really ramdisk space or ESXi inodes filling up the host:
If you can't login then you might still be able to run these esxcli commands from a remote host with the vCLI installed (like the vMA):
# esxcli --server $server system visorfs ramdisk list
Ramdisk Name System Reserved Maximum Used Peak Used Free Reserved Free Maximum Inodes Allocated Inodes Used Inodes Mount Point
------------ ------ --------- ---------- -------- --------- ---- ------------- -------------- ---------------- ----------- ---------------------------
root true 32768 KiB 32768 KiB 3856 KiB 3864 KiB 88 % 88 % 8192 4096 2711 /
etc true 28672 KiB 28672 KiB 316 KiB 356 KiB 98 % 98 % 4096 1024 458 /etc
tmp false 2048 KiB 196608 KiB 6888 KiB 8508 KiB 96 % 0 % 8192 256 75 /tmp
hostdstats false 0 KiB 654336 KiB 3340 KiB 3340 KiB 99 % 0 % 8192 32 4 /var/lib/vmware/hostd/stats
# esxcli --server $server system visorfs get
Total Inodes: 524288
Used Inodes: 3247
Unlinked Inodes: 0
Reserved Inodes: 0
Peak Used Inodes: 3338
Peak Unlinked Inodes: 2
Peak Reserved Inodes: 2
Free Inode Percent: 99
Lowest Free Inode Percent: 99