Error: cannot list snaps: cannot communicate with server: timeout exceeded while waiting for response

Good morning everybody,
once I try to use the command sudo snap refresh it keeps on processing for too long and then throws error: cannot list snaps: cannot communicate with server: timeout exceeded while waiting for response or error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/snaps: dial unix /run/snapd.socket: connect: connection refused when I use the command snap list

OS: Ubuntu 20.10

$ systemctl status snapd.service

● snapd.service - Snap Daemon
     Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
     Active: deactivating (stop-sigterm) (Result: timeout)
TriggeredBy: ● snapd.socket
   Main PID: 6908 (snapd)
      Tasks: 11 (limit: 6924)
     Memory: 13.8M
     CGroup: /system.slice/snapd.service
             └─6908 /usr/lib/snapd/snapd

May 07 01:57:52 Stack-Linux systemd[1]: Starting Snap Daemon...
May 07 01:57:52 Stack-Linux snapd[6908]: AppArmor status: apparmor is enabled and all features are available
May 07 01:57:52 Stack-Linux snapd[6908]: AppArmor status: apparmor is enabled and all features are available
May 07 01:59:23 Stack-Linux systemd[1]: snapd.service: start operation timed out. Terminating.

$ journalctl -xu snapd.service

-- Logs begin at Wed 2021-05-05 20:16:54 EET, end at Fri 2021-05-07 01:58:15 EET. --
May 05 20:41:38 Stack-Linux snapd[4870]: storehelpers.go:551: cannot refresh: snap has no updates available: "arduino", "blender", "canonical-livepatch", "core", "core18", "core20", "deezer-unofficial-player", "docker", "ffmpeg", "gifski", "gimp", "gnome-3-28-1804", "gnome-3-34-1804", "go", "gtk-common-themes", "heroku", "john-the-ripper", "kde-frameworks-5-core18", "kde-frameworks-5-qt-5-14-core18", "kde-frameworks-5-qt-5-15-core20", "kdenlive", "obs-studio", "okular", "photoscape", "postman", "skype", "snap-store", "snapd", "spotify", "task", "telegram-desktop", "thunderbird", "vlc", "wine-platform-5-stable", "wine-platform-runtime"
May 05 20:44:12 Stack-Linux snapd[4870]: store_download.go:169: Cannot download or apply deltas for android-studio: write /var/lib/snapd/snaps/android-studio_103.snap.xdelta3-101-to-103.partial: no space left on device
May 05 21:18:12 Stack-Linux systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing.
May 05 21:18:12 Stack-Linux systemd[1]: snapd.service: Killing process 20121 (snapd) with signal SIGKILL.
May 05 21:18:12 Stack-Linux systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit snapd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 9.
May 05 21:18:12 Stack-Linux systemd[1]: snapd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit snapd.service has entered the 'failed' state with result 'timeout'.
May 05 21:18:12 Stack-Linux systemd[1]: Failed to start Snap Daemon.
░░ Subject: A start job for unit snapd.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit snapd.service has finished with a failure.
░░ 
░░ The job identifier is 13409 and the job result is failed.
May 05 21:18:13 Stack-Linux systemd[1]: snapd.service: Scheduled restart job, restart counter is at 11.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ Automatic restarting of the unit snapd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 05 21:18:13 Stack-Linux systemd[1]: Stopped Snap Daemon.
░░ Subject: A stop job for unit snapd.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit snapd.service has finished.
░░ 
░░ The job identifier is 13657 and the job result is done.
May 05 21:18:13 Stack-Linux systemd[1]: Starting Snap Daemon...
░░ Subject: A start job for unit snapd.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit snapd.service has begun execution.
░░ 
░░ The job identifier is 13657.
May 05 21:18:13 Stack-Linux snapd[22427]: AppArmor status: apparmor is enabled and all features are available
May 05 21:18:13 Stack-Linux snapd[22427]: AppArmor status: apparmor is enabled and all features are available
-- Reboot --
May 07 01:56:22 Stack-Linux systemd[1]: snapd.service: start operation timed out. Terminating.
May 07 01:57:52 Stack-Linux systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing.
May 07 01:57:52 Stack-Linux systemd[1]: snapd.service: Killing process 6745 (snapd) with signal SIGKILL.
May 07 01:57:52 Stack-Linux systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit snapd.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 9.
May 07 01:57:52 Stack-Linux systemd[1]: snapd.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit snapd.service has entered the 'failed' state with result 'timeout'.
May 07 01:57:52 Stack-Linux systemd[1]: Failed to start Snap Daemon.
░░ Subject: A start job for unit snapd.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit snapd.service has finished with a failure.
░░ 
░░ The job identifier is 7431 and the job result is failed.
May 07 01:57:52 Stack-Linux systemd[1]: snapd.service: Scheduled restart job, restart counter is at 13.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ Automatic restarting of the unit snapd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 07 01:57:52 Stack-Linux systemd[1]: Stopped Snap Daemon.
░░ Subject: A stop job for unit snapd.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit snapd.service has finished.
░░ 
░░ The job identifier is 7555 and the job result is done.
May 07 01:57:52 Stack-Linux systemd[1]: Starting Snap Daemon...
░░ Subject: A start job for unit snapd.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit snapd.service has begun execution.
░░ 
░░ The job identifier is 7555.
May 07 01:57:52 Stack-Linux snapd[6908]: AppArmor status: apparmor is enabled and all features are available
May 07 01:57:52 Stack-Linux snapd[6908]: AppArmor status: apparmor is enabled and all features are available

You’ve run out of space in the partition that holds /var/lib/snapd/snaps/, perhaps that’s your rootfs?

Thanks dude…
it worked suddenly after reinstalling snapd (and by the way all snaps)