I’m having this same issue on multiple servers. I managed to fixed one, but I’m unable to get that on others:
$ SNAPD_DEBUG=1 snap version
2021/12/21 07:10:40.154300 tool_linux.go:68: DEBUG: re-exec not supported on distro "almalinux" yet
snap 2.53.4-1.el8
snapd unavailable
series -
$ systemctl status snapd
● snapd.service - Snap Daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2021-12-21 07:06:54 CET; 4min 53s ago
Main PID: 87577 (snapd)
Tasks: 8 (limit: 4936)
Memory: 24.6M
CGroup: /system.slice/snapd.service
└─87577 /usr/libexec/snapd/snapd
Dec 21 07:06:54 - systemd[1]: Starting Snap Daemon...
Dec 21 07:06:54 - snapd[87577]: AppArmor status: apparmor not enabled
Dec 21 07:06:54 - snapd[87577]: daemon.go:242: started snapd/2.53.4-1.el8 (series 16; classic; devmode) almalinux/8.5 (amd64) linux/4.18.0-348.2.1.el8_5.x86_.
Dec 21 07:06:54 - snapd[87577]: daemon.go:335: adjusting startup timeout by 45s (pessimistic estimate of 30s plus 5s per snap)
Dec 21 07:06:54 - systemd[1]: Started Snap Daemon.
$ systemctl status snapd.socket
● snapd.socket - Socket activation for snappy daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.socket; enabled; vendor preset: disabled)
Active: active (running) since Tue 2021-12-21 07:06:54 CET; 4min 55s ago
Listen: /run/snapd.socket (Stream)
/run/snapd-snap.socket (Stream)
Tasks: 0 (limit: 4936)
Memory: 4.0K
CGroup: /system.slice/snapd.socket
Dec 21 07:06:54 - systemd[1]: Starting Socket activation for snappy daemon.
Dec 21 07:06:54 - systemd[1]: Listening on Socket activation for snappy daemon.
Restarting or reinstalling snapd does not change this
(note: this is AlmaLinux, but that’s similar to RHEL)