snap failed to run with '/usr/bin/snap wait system seed.loaded'

[Gene Sun]

I tried to enable livepatch without any success. ([Bug 1960689] )

support suggested me report a bug for snapd.

  root@plis231v:~# sudo ua enable livepatch
  One moment, checking your subscription first
  Unexpected error(s) occurred.
  For more details, see the log: /var/log/ubuntu-advantage.log
  To file a bug run: ubuntu-bug ubuntu-advantage-tools

  >> logs

  22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: /var/lib/ubuntu-advantage/notices.json
  2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: /var/lib/ubuntu-advantage/notices.json
  2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, please file a bug
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in wrapper
      return func(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main
      return args.action(args, cfg=cfg)
    File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f
      return f(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f
      return f(args, cfg=cfg, **kwargs)
    File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f
      retval = f(*args, cfg=cfg, **kwargs)
    File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in action_enable
      ent_ret, reason = entitlement.enable()
    File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 197, in enable
      ret = self._perform_enable(silent=silent)
    File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py", line 160, in _perform_ena
      [snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True
    File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp
      out, err = _subp(args, rcs, capture, timeout, env=env)
    File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp
      stderr=err.decode("utf-8"),
  uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap wait system seed.loaded' [sage: error: cannot communicate with server: Get http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: connect: no such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-advantage-tools 27.4.1~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-167-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.30+esm3
  Architecture: amd64
  Date: Fri Feb 11 23:01:08 2022
  InstallationDate: Installed on 2010-12-02 (4089 days ago)
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago)

[Alberto Mardegan (mardy)]

Hi Gene, thanks for reporting this!

I have no idea what the problem might be, but please try this:

1) Since you are already root, try not using sudo (though I'm almost sure that this is not causing any issues)
2) Please post the output of these commands (after re-trying to enable livepatch):

    systemctl status snapd
    systemctl status snapd.socket
    journalctl -b -u snapd

[Gene Sun (gsunipipeline)]

Hey Alberto Mardegan,

This issue is blocking us to enable livepatch.

root@plis231v:~# systemctl status snapd
Failed to get properties: No such interface ''
root@plis231v:~# systemctl status snapd.socket Failed to get properties: No such interface ''
root@plis231v:~# journalctl -b -u snapd
No journal files were found.
-- No entries --
root@plis231v:~#

[Ian Johnson (anonymouse67)]

Hi, can you share what version of snapd you have installed?

apt show snapd
snap version

Thanks

[Paulo Flabiano Smorigo (pfsmorigo)]

What snapd version are you using?

[Gene Sun (gsunipipeline)]

root@plis231v:~# apt show snapd
Package: snapd
Version: 2.54.3+16.04~esm2
Built-Using: apparmor (= 2.10.95-0ubuntu2.11), libcap2 (= 1:2.24-12), libseccomp (= 2.4.3-1ubuntu3.16.04.3)
Priority: optional
Section: devel
Maintainer: Ubuntu Developers <email address hidden>
Installed-Size: 146 MB
Depends: adduser, apparmor (>= 2.10.95-0ubuntu2.2), ca-certificates, openssh-client, squashfs-tools, systemd, udev, init-system-helpers (>= 1.18~), libc6 (>= 2.17), libfuse2 (>= 2.6), liblzma5 (>= 5.1.1alpha+20110809), liblzo2-2, libudev1 (>= 183), zlib1g (>= 1:1.1.4)
Recommends: gnupg
Suggests: zenity | kdialog
Conflicts: snap (<< 2013-11-29-1ubuntu1)
Breaks: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9)
Replaces: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9)
Download-Size: 33.3 MB
APT-Manual-Installed: yes
APT-Sources: https://esm.ubuntu.com/infra/ubuntu xenial-infra-security/main amd64 Packages
Description: Daemon and tooling that enable snap packages
 Install, configure, refresh and remove snap packages. Snaps are
 'universal' packages that work across many different Linux systems,
 enabling secure distribution of the latest apps and utilities for
 cloud, servers, desktops and the internet of things.
 .
 Start with 'snap list' to see installed snaps.

N: There are 2 additional records. Please use the '-a' switch to see them.
root@plis231v:~#
root@plis231v:~# snap version

snap 2.54.3+16.04~esm2
snapd unavailable
series -

[Maciej Borzecki (maciek-borzecki)]

Does running `systemctl status` work at all?

[Gene Sun (gsunipipeline)]

root@plis231v:~# systemctl status
Failed to read server status: Invalid argument
root@plis231v:~#

[Ian Johnson (anonymouse67)]

Is this system using systemd as it's init system? I see that it was originally installed with 10.04.1 which would not have been using systemd.

[Maciej Borzecki (maciek-borzecki)]

@gsunipipeline it looks like systemd does not operate correctly in your system. This is a prerequisite for even accessing the snapd daemon, since we rely on systemd to provide the socket, then activate snapd daemon, and the snapd daemon directly interacts with systemd to set up snaps.

[Gene Sun (gsunipipeline)]

any suggestion to fix this?

I had tried below command.
root@plis231v:~# sudo dpkg -l | grep systemd
ii libpam-systemd:amd64 229-4ubuntu21.31+esm1 amd64 system and service manager - PAM mod
ii libsystemd0:amd64 229-4ubuntu21.31+esm1 amd64 systemd utility library
ii python3-systemd 231-2build1 amd64 Python 3 bindings for systemd
ii systemd 229-4ubuntu21.31+esm1 amd64 system and service manager
rc systemd-services 204-5ubuntu20.31 amd64 systemd runtime services
ii systemd-shim 9-1bzr4ubuntu1 amd64 shim for systemd
root@plis231v:~#
root@plis231v:~#
root@plis231v:~#
root@plis231v:~# apt-get install --reinstall systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/3,659 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 77423 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu21.31+esm1_amd64.deb ...
Unpacking systemd (229-4ubuntu21.31+esm1) over (229-4ubuntu21.31+esm1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.6+esm1) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
ureadahead will be reprofiled on next reboot
Setting up systemd (229-4ubuntu21.31+esm1) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Operation failed: No such file or directory
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
root@plis231v:~# systemctl status
Failed to read server status: Invalid argument
root@plis231v:~#
root@plis231v:~#

[Ian Johnson (anonymouse67)]

What is the output of these commands:

ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline

[Gene Sun (gsunipipeline)]

root@plis231v:~# ps -o cmd fp 1
CMD
/sbin/init
root@plis231v:~# sudo ls -lah /proc/1/exe
lrwxrwxrwx 1 root root 0 Feb 11 22:51 /proc/1/exe -> /sbin/upstart
root@plis231v:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-167-generic root=/dev/mapper/plis231v-root ro quiet
root@plis231v:~#

[Ian Johnson (anonymouse67)]

So indeed your system is still using upstart, in order to use snapd you will need to switch your system over to use systemd instead. Likely one of the upgrade scripts from 10.04 to 16.04 did not transition from upstart to systemd the way a fresh install of 16.04 would default to.