Snap cannot communicate with server

@chipaca I have sent the system logs to the manufacturere and waiting for a response.

I will give you a follow up as soon as I get a reply.

Thank you for the help.

hola a mi se me soluciono ese problema con esto comandos:

systemctl enable snapd.service

systemctl start snapd.service

espero que te sirva

5 Likes

if anything does not work after all of above steps then just restart snap service using the following command

systemctl restart snapd

2 Likes

I think there was a bug. I fixed it by installing a newer version of snapd.

$ sudo dpkg -i https://launchpad.net/ubuntu/+archive/primary/+files/snapd_2.37.1_amd64.deb
$ sudo apt-get install -f

$snap version
worked correctly after this.

I got the release info from https://launchpad.net/ubuntu/+source/snapd
I am running Ubuntu 16.04 LTS.

Hi;

Just for the record, I had a similar problem and it turned out to be lack of space for the root directory:

$ df -kh
Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           378M  8.9M  369M   3% /run
/dev/mmcblk0p3  350M  343M     0 100% /writable
/dev/loop0       92M   92M     0 100% /
/dev/loop1      155M  155M     0 100% /lib/modules
tmpfs           1.9G  4.0K  1.9G   1% /etc/fstab
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G     0  1.9G   0% /media
tmpfs           1.9G     0  1.9G   0% /tmp
tmpfs           1.9G     0  1.9G   0% /mnt
tmpfs           1.9G     0  1.9G   0% /var/lib/sudo
/dev/loop2       92M   92M     0 100% /snap/core/6531
/dev/mmcblk0p2   50M  2.3M   47M   5% /boot/efi
cgmfs           100K     0  100K   0% /run/cgmanager/fs
tmpfs           378M     0  378M   0% /run/user/1000

Don’t forget to extend the partition to use all the space on the sd-card/hard-drive.

Bests,
Vahid

11 posts were split to a new topic: Snapd errors when init isn’t systemd

A post was merged into an existing topic: Snapd errors when init isn’t systemd

A post was split to a new topic: EOF from api.snapcraft.io

I had the exact same error on Ubuntu Core.
I fixed it by flashing the SD card again with sudo dd if=myimage.img of=/dev/mydisk as said in the documentation, but without bs=32M.
I don’t know if removing the bs=32M part is useful or if I’m just lucky, but after several installations I think this one is good.

the blocksize option just tells dd to cache 32MB in RAM before flushing it to disk, it does not have any effect on the actual written data (indeed, if you had less than 32MB of RAM that would have some impact, beyond this it is only speeding up the write process, nothing more … )

You’re right @ogra. I just explained what steps I followed to make it working. I think the thing was only to reburn the SD card, again.

1 Like

systemctl restart snapd does the trick for me. I had snapd inactive (dead)

1 Like

Me funciono a mi también. Gracias.

Thank you! Nr. 2 helped me out.

After installing snapd (whatever your linux distro), you should reboot your pc/laptop to let the snapd integrate with your linux system correctly.

If not, most likely you’ll end up with that kind of message.

it works for me, thanks a lot bro

This worked perfectly! Thanks so much

gracias !

for additional info :

thank you ,it is working !!!

How to get this list information?