In this position I would recommend rebooting your droplet. The error your console is showing is more likely related to either high traffic or running out of memory on your droplet causing services to be killed to keep the kernel running (which is why it’s still responding to pings).

If you can log in via the console (press enter if you don’t see a login prompt) then run reboot and attempt to connect again once your droplet reboots. If you cannot do this from the console you can use the “power cycle” option in the control panel.

After rebooting you can check the logs in /var/log for indications to what occurred before the services stopped responding.