Snap - Unable to mount

Issues & Assistance
21

The lines are still truncated… use

sudo journalctl -xe --no-pager

instead.

3 Likes
22

Error:
Body is limited to 32000 characters; you entered 177719.

23

Yes, so don't try to paste the whole thing.

Are you giving this any more thought than copy and pasting the commands? You have to work with me here.

2 Likes
24

Oct 02 21:08:58 study-travelmatep243 snapd[119249]: taskrunner.go:271: [change 17 "Mount snap "core" (9993)" task] failed: [start snap-core-9993.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details.
Oct 02 21:08:59 study-travelmatep243 snapd[119249]: handlers.go:495: Reported install problem for "core" as already-reported
Oct 02 21:08:59 study-travelmatep243 audit[119210]: USER_END pid=119210 uid=0 auid=1001 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:08:59 study-travelmatep243 audit[119210]: CRED_DISP pid=119210 uid=0 auid=1001 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:08:59 study-travelmatep243 sudo[119210]: pam_unix(sudo:session): ses

1 Like
25

OK, so those two lines actually end up telling us nothing about what’s wrong with snap. :sweat_smile:

So… what next… :thinking:

3 Likes
26 
ct 02 21:16:19 study-travelmatep243 systemd[1]: /usr/lib/systemd/system/gdm.service:28: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 02 21:16:19 study-travelmatep243 systemd[1]: /usr/lib/systemd/system/fancontrol.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fancontrol.pid → /run/fancontrol.pid; please update the unit file accordingly.
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=162 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=163 op=LOAD
Oct 02 21:16:19 study-travelmatep243 kernel: audit: type=1334 audit(1601653579.394:534): prog-id=162 op=LOAD
Oct 02 21:16:19 study-travelmatep243 kernel: audit: type=1334 audit(1601653579.394:535): prog-id=163 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=164 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=165 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=166 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=167 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=168 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=169 op=LOAD
Oct 02 21:16:19 study-travelmatep243 systemd[1]: snap-core-9993.mount: Mount path /snap/core/9993 is not canonical (contains a symlink).
░░ Subject: Mount point is not empty
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The directory /snap/core/9993 is specified as the mount point (second field in
░░ /etc/fstab or Where= field in systemd unit file) and is not empty.
░░ This does not interfere with mounting, but the pre-exisiting files in
░░ this directory become inaccessible. To see those over-mounted files,
░░ please manually mount the underlying file system to a secondary
░░ location.
Oct 02 21:16:19 study-travelmatep243 systemd[1]: snap-core-9993.mount: Failed to run 'mount' task: Too many levels of symbolic links
Oct 02 21:16:19 study-travelmatep243 systemd[1]: snap-core-9993.mount: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit snap-core-9993.mount has entered the 'failed' state with result 'resources'.
Oct 02 21:16:19 study-travelmatep243 systemd[1]: Failed to mount Mount unit for core, revision 9993.
░░ Subject: A start job for unit snap-core-9993.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit snap-core-9993.mount has finished with a failure.
░░ 
░░ The job identifier is 3234 and the job result is failed.
Oct 02 21:16:19 study-travelmatep243 systemd[1]: snapd.service: Got notification message from PID 136273, but reception only permitted for main PID 119249
Oct 02 21:16:19 study-travelmatep243 systemd[1]: Reloading.
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=169 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=168 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=167 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=166 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=165 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=164 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=163 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=162 op=UNLOAD
Oct 02 21:16:19 study-travelmatep243 systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Oct 02 21:16:19 study-travelmatep243 systemd[1]: /usr/lib/systemd/system/gdm.service:28: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 02 21:16:19 study-travelmatep243 systemd[1]: /usr/lib/systemd/system/fancontrol.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fancontrol.pid → /run/fancontrol.pid; please update the unit file accordingly.
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=170 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=171 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=172 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=173 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=174 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=175 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=176 op=LOAD
Oct 02 21:16:19 study-travelmatep243 audit: BPF prog-id=177 op=LOAD
Oct 02 21:16:19 study-travelmatep243 snapd[119249]: taskrunner.go:271: [change 19 "Mount snap \"core\" (9993)" task] failed: [start snap-core-9993.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details.
Oct 02 21:16:20 study-travelmatep243 snapd[119249]: handlers.go:495: Reported install problem for "core" as already-reported
Oct 02 21:16:20 study-travelmatep243 audit[135534]: USER_END pid=135534 uid=0 auid=1001 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:20 study-travelmatep243 audit[135534]: CRED_DISP pid=135534 uid=0 auid=1001 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:20 study-travelmatep243 sudo[135534]: pam_unix(sudo:session): session closed for user root
Oct 02 21:16:28 study-travelmatep243 dbus-daemon[378]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.420' (uid=0 pid=136371 comm="sudo journalctl -xe --no-pager ")
Oct 02 21:16:28 study-travelmatep243 dbus-daemon[378]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 02 21:16:28 study-travelmatep243 sudo[136371]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 02 21:16:28 study-travelmatep243 audit[136371]: USER_ACCT pid=136371 uid=1001 auid=1001 ses=2 msg='op=PAM:accounting grantors=pam_permit,pam_time acct="study" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:28 study-travelmatep243 kernel: kauditd_printk_skb: 24 callbacks suppressed
Oct 02 21:16:28 study-travelmatep243 kernel: audit: type=1101 audit(1601653588.857:560): pid=136371 uid=1001 auid=1001 ses=2 msg='op=PAM:accounting grantors=pam_permit,pam_time acct="study" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:28 study-travelmatep243 kernel: audit: type=1110 audit(1601653588.857:561): pid=136371 uid=0 auid=1001 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:28 study-travelmatep243 audit[136371]: CRED_REFR pid=136371 uid=0 auid=1001 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:28 study-travelmatep243 sudo[136371]:    study : TTY=pts/0 ; PWD=/home/study ; USER=root ; COMMAND=/usr/bin/journalctl -xe --no-pager
Oct 02 21:16:28 study-travelmatep243 audit[136371]: USER_START pid=136371 uid=0 auid=1001 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Oct 02 21:16:28 study-travelmatep243 sudo[136371]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Oct 02 21:16:28 study-travelmatep243 kernel: audit: type=1105 audit(1601653588.860:562): pid=136371 uid=0 auid=1001 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
27

Ah! This looks useful!

I remember seeing this before - I think it’s just down to a permissions issue on /var/lib/snapd .

1 Like
28

Is there anything left from myside then plzz suggest....

29

Web search results for this error:

So:

What is /snap on your system? e.g. output of ls -ld /snap .

30

lrwxrwxrwx 1 root root 19 Sep 28 17:05 /snap -> /var/lib/snapd/snap

31

sudo rm /snap then try again.

If that doesn't help, recreate the symlink.

1 Like
32 
❯ sudo rm /snap
[sudo] password for study:             
❯ sudo snap install hello-world
2020-10-02T22:01:36+05:30 INFO Waiting for automatic snapd restart...
Warning: /snap/bin was not found in your $PATH. If you've not restarted your
         session since you installed snapd, try doing that. Please see
         https://forum.snapcraft.io/t/9469 for more details.

hello-world 6.4 from Canonical* installed
33

ls -l /snap ?

1 Like
34

❯ ls -l /snap
total 4
drwxr-xr-x 1 root root 112 Oct 2 22:01 bin
drwxr-xr-x 1 root root 22 Oct 2 22:01 core
drwxr-xr-x 1 root root 18 Oct 2 22:01 hello-world
-r–r–r-- 1 root root 548 Oct 2 22:01 README

35

Ah, OK, so it re-created the directory structure under /snap rather than using the /var/lib/snapd/snap directory.

This seems like a bug, either in the upstream configuration (i.e. where it expects the files to exist) or in the package (i.e. where it places the files).

2 Likes
36

Now i m trying to install keepass from pamac.

1 Like
37

To enable classic snap support, enter the following to create a symbolic link between /var/lib/snapd/snap and /snap

sudo ln -s /var/lib/snapd/snap /snap

Is this the cause ?

2 Likes
38

Yes, that symlink seems to break something - maybe the Apparmor rule?

2 Likes
39

I did this in post-install script for pamac-all package

But no one complained until now

So i think it isnt related ?

1 Like
40

Maybe noone found it until now? :sweat_smile:

3 Likes