Adding new SSH keys in Metadata doesn't work anymore

[sta...@gmail.com]

Hey there, I've used a compute engine instance for a long time and added new ssh keys with no problem.

Sometime this last 3 months, every and each key i'm adding doesn't deploy into the instance, actually when I try to SSH through the Console by pressing SSH it just hangs and constantly says

"Transferring SSH keys to the VM.The key transfer to project metadata is taking an unusually long time. Transferring instead to instance metadata may be faster, but will transfer the keys only to this VM"

When I disable CSF the SSH windows just closes.

I generate keys with puttygen and it worked before. Now it doesn't.

In the Serial I saw this:

Dec 25 00:21:26 vangus-c1-vm kernel: Set bl_STOPFORUMSPAM_180D is full, maxelem 65536 reached

Dec 25 00:21:34 vangus-c1-vm kernel: Set bl_STOPFORUMSPAM_365D is full, maxelem 65536 reached

I can't figure out if it related some how or not. We are trying to give SSH access to one of our support teams and it terminates immediately.

Help anyone?

[Yui (Google Cloud Support)]

Hi

If previous users can SSH but not new ones, I suspect a memory capacity issue. This can also be checked by going to

Compute engine>VM instances>VM name>Serial port 1(console)

Errors such as “no space left”, “out of disk space” or “out of memory” could be seen there if your VM is indeed affected by a capacity issue. Alternately, you can also SSH with an old user and run a df command in order to check disk space.

If you need to resize your disk, you may perform the following

1.Stop your instance.

2.Go to your instance, Edit, click on the name of your boot disk. From there, click on Edit again. You will be able to resize your disk size.

3.Start your instance and try to SSH.