Installation failure of snapd on an faux-Ubuntu machine with Plesk installed

I’m having problems with the install of snap. The following error occurs when executing sudo apt-get install snapd on Ubuntu:

Job for snapd.seeded.service failed because the control process exited with error code. See “systemctl status snapd.seeded.service” and “journalctl -xe” for details.
snapd.seeded.service couldn’t start.
Job for snapd.service failed because the control process exited with error code. See “systemctl status snapd.service” and “journalctl -xe” for details.
snapd.service couldn’t start.
snapd.snap-repair.service is a disabled or a static unit, not starting it.

snap version does that:

snap 2.34.2
snapd unavailable
series -

and systemctl status snapd.seeded.service reports:

Failed to connect to bus: No such file or directory

Ubuntu is freshly installed together with Plesk.

Thanks for the help

1 Like

Can you give a few more details about your setup ? Is this a native ubuntu install on actual hardware that you installed plesk on ? (if so, did you try installing snapd before plesk in case plesk mangles any OS security settings) …

Or is it some kind of container you run Ubuntu in ?

Ubuntu is running on a virtual server (8GB Ram/4 Cores). Plesk has been installed along with the OS by the vendor.

Could we see the output of journalctl -u snapd?

Of course.


error: cannot start snapd: cannot mount squashfs image using "fuse.snapfuse":
mount: wrong fs type, bad option, bad superblock on /tmp/selftest-squashfs-723260739,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so.

What’s the output of systemd-detect-virt?

Only says “openvz” …

and the output of uname -a ?

Linux 4.4.0-042stab131.1 #1 SMP Wed Jun 20 16:32:07 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux

1 Like

Are you able to manually mount a squashfs? For example this test one?

or even simpler … does the output of:

cat /proc/filesystems

list squashfs ?

unfortunately there are ways in which squashfs can be there without the kernel being able to mount a snap (e.g. no xz support), and viceversa (e.g. support via not-yet-loaded modules)…

1 Like

This is the output:

nodev cgroup
nodev devpts
nodev mqueue
nodev nfs
nodev nfs4
nodev delayfs
nodev devtmpfs
nodev sysfs
nodev proc
nodev tmpfs
nodev binfmt_misc
nodev fusectl
nodev fuse
nodev rpc_pipefs

Actually…no. I am not really into all of that, just started to learn about Linux/Servers.

Try this, one line at a time into a terminal

sudo mount -t squashfs test.squashfs /mnt

and show us the output :slight_smile:

Well, what you are using there is not ubuntu, it uses a kernel that was mangled by the hoster and due to that violates the Ubuntu trademark, can technically not even be called Ubuntu and might be missing important security features and system defaults (like squashfs support) … try out what @chipaca proposes here, but the fact that this is a provider-hacked kernel might make you run into various other problems.

It outputs “mount: /mnt: mount failed: Unknown error -1”

could you look at the last few lines of dmesg -H? They might have more info.

It does absolutely nothing. No error, no message…

Strange. Try without the -H?