Snapd service not running / snap install not working

snapd
1

Having some trouble with snap for installing Heroku. Never used it before, usually use pip. Here’s what happens:

(legal_subs_3.6) (xenial)amessios@localhost:~$ sudo snap install heroku --classic
error: cannot communicate with server: Post http://localhost/v2/snaps/heroku: dial unix /run/snapd.socket: connect: no such file or directory


(legal_subs_3.6) (xenial)amessios@localhost:~$ snap find heroku
error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/find?q=heroku&scope=wide: dial unix /run/snapd.socket: connect: no such file or directory

I’ve been through the fixes/checks I can find so far online to no avail:

(legal_subs_3.6) (xenial)amessios@localhost:~$ snap --version
snap    2.39.2ubuntu0.2
snapd   unavailable
series  -


(legal_subs_3.6) (xenial)amessios@localhost:~$ sudo service snapd start
snapd: unrecognized service


(legal_subs_3.6) (xenial)amessios@localhost:~$ sudo service snap start
snap: unrecognized service


(legal_subs_3.6) (xenial)amessios@localhost:~$ systemctl status snapd
Failed to get properties: Launch helper exited with unknown return code 1


(legal_subs_3.6) (xenial)amessios@localhost:~/code/test_projects/lawyer_bios/lawyer_bios$ systemctl start snapd.service
Failed to add /run/systemd/ask-password to directory watch: No such file or directory
Failed to start snapd.service: Launch helper exited with unknown return code 1
See system logs and 'systemctl status snapd.service' for details.


(legal_subs_3.6) (xenial)amessios@localhost:~/code/test_projects/lawyer_bios/lawyer_bios$ systemctl status snapd.service
    Failed to get properties: Launch helper exited with unknown return code 1

I’ve also tried re-installing snap using:

$ sudo apt autoremove --purge snapd

$ sudo apt install snapd

But it didn’t help unfortunately. Any ideas?

2

What’s the output of journalctl -u snapd?

3

Hi Chipaca. Forgot to add that one! It’s:

(legal_subs_3.6) (xenial)amessios@localhost:~/code/test_projects/lawyer_bios/lawyer_bios$ journalctl -u snapd
No journal files were found.
-- No entries --
4

I had a problem with this recently as well.

You will need to run either service snapd start or systemctl start snapd.service to start the service.

I see you tried that already and it didn’t work. Hopefully the below works.

To auto-enable you’d run systemctl enable snapd

That should most likely work for you.

snapd didn’t get added to my services on install either for…some reason.

5

Hi tn I tried those commands. Didn’t work unfortunately. Really stumped on this one!

6

What happens if, from a terminal, you run

sudo SNAPD_DEBUG=1 /usr/lib/snapd/snapd
7

Nothing Worked does anyone have any more ideas. My outputs were the same exept:

(base) grayson@gsb:~$ systemctl start snapd.service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
8

@SixRocket you cannot use snapd without systemd as your init system