Have problem with SSH connection in Google Cloud Platform

893 views Asked by At

I can't connect to my VM instance. "default-allow-ssh" rule in Firewall is "Allow". I think maybe logs help:

Aug 30 09:23:24 my-vm google-accounts: ERROR Exception calling the response handler. [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/'].#012Traceback (most recent call last):#012  File "/usr/lib/python3/dist-packages/google_compute_engine/metadata_watcher.py", line 200, in WatchMetadata#012    handler(response)#012  File "/usr/lib/python3/dist-packages/google_compute_engine/accounts/accounts_daemon.py", line 285, in HandleAccounts#012    self.utils.SetConfiguredUsers(desired_users.keys())#012  File "/usr/lib/python3/dist-packages/google_compute_engine/accounts/accounts_utils.py", line 318, in SetConfiguredUsers#012    mode='w', prefix=prefix, delete=True) as updated_users:#012  File "/usr/lib/python3.6/tempfile.py", line 681, in NamedTemporaryFile#012    prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)#012  File "/usr/lib/python3.6/tempfile.py", line 269, in _sanitize_params#012    dir = gettempdir()#012  File "/usr/lib/python3.6/tempfile.py", line 437, in gettempdir#012    tempdir = _get_default_tempdir()#012  File "/usr/lib/python3.6/tempfile.py", line 372, in _get_default_tempdir#012    dirlist)#012FileNotFoundError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']
Aug 30 09:23:30 my-vm systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing.
Aug 30 09:23:30 my-vm systemd[1]: snapd.service: Killing process 15472 (snapd) with signal SIGKILL.
Aug 30 09:23:30 my-vm systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL
Aug 30 09:23:30 my-vm systemd[1]: snapd.service: Failed with result 'timeout'.
Aug 30 09:23:30 my-vm systemd[1]: Failed to start Snap Daemon.
Aug 30 09:23:31 my-vm systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
Aug 30 09:23:31 my-vm systemd[1]: snapd.service: Scheduled restart job, restart counter is at 939.
Aug 30 09:23:31 my-vm systemd[1]: Stopped Snap Daemon.
Aug 30 09:23:31 my-vm systemd[1]: Starting Snap Daemon...
Aug 30 09:23:31 my-vm snapd[15582]: AppArmor status: apparmor is enabled and all features are available
Aug 30 09:23:31 my-vm snapd[15582]: AppArmor status: apparmor is enabled and all features are available
1

There are 1 answers

6
Afshin On

Mostly this is happen because your disk storage is full. If you have other type of access to your VM like connect using Serial console, check your disk space allocated status through it and try to free up some space or add additional data storage if its full.