Public bug reported:

It was working Friday, tried some snap commands this afternoon and snapd
is not running. The system was up last three days without interaction,
but it could have updated itself - I see an update Sunday

$ ls -lt /snap
total 20
drwxr-xr-x 5 root root 4096 Oct  9 17:33 ubuntu-core


This is on a Dragonboard.

Starting it fails as follows:

pat-mcgowan@localhost:~$ sudo systemctl status snapd
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) (Result: exit-code) since Tue 2016-10-11 19:34:19 
UTC; 30s ago
  Process: 3434 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
 Main PID: 3434 (code=exited, status=1/FAILURE)

Oct 11 19:34:18 localhost.localdomain systemd[1]: snapd.service: Unit entered 
failed state.
Oct 11 19:34:18 localhost.localdomain systemd[1]: snapd.service: Failed with 
result 'exit-code'.
Oct 11 19:34:19 localhost.localdomain systemd[1]: snapd.service: Service 
hold-off time over, scheduling restart.
Oct 11 19:34:19 localhost.localdomain systemd[1]: Stopped Snappy daemon.
Oct 11 19:34:19 localhost.localdomain systemd[1]: snapd.service: Start request 
repeated too quickly.
Oct 11 19:34:19 localhost.localdomain systemd[1]: Failed to start Snappy daemon.

>From syslog:
Oct 11 19:39:38 localhost systemd[1]: snapd.service: Main process exited, 
code=exited, status=1/FAILURE
Oct 11 19:39:38 localhost systemd[1]: snapd.service: Unit entered failed state.
Oct 11 19:39:38 localhost systemd[1]: snapd.service: Failed with result 
'exit-code'.
Oct 11 19:39:39 localhost systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
Oct 11 19:39:39 localhost systemd[1]: Stopped Snappy daemon.
Oct 11 19:39:39 localhost systemd[1]: Started Snappy daemon.
Oct 11 19:39:39 localhost snapd[3538]: error: cannot downgrade: snapd is too 
old for the current system state (patch level 4)
Oct 11 19:39:39 localhost systemd[1]: snapd.service: Main process exited, 
code=exited, status=1/FAILURE
Oct 11 19:39:39 localhost systemd[1]: snapd.service: Unit entered failed state.
Oct 11 19:39:39 localhost systemd[1]: snapd.service: Failed with result 
'exit-code'.
Oct 11 19:39:39 localhost systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
Oct 11 19:39:39 localhost systemd[1]: Stopped Snappy daemon.
Oct 11 19:39:39 localhost systemd[1]: snapd.service: Start request repeated too 
quickly.
Oct 11 19:39:39 localhost systemd[1]: Failed to start Snappy daemon.
Oct 11 19:39:39 localhost systemd[1]: snapd.socket: Unit entered failed state.
Oct 11 19:41:37 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Tue Oct 11 19:43:07 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

** Affects: snapd (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  It was working Friday, tried some snap commands this afternoon and snapd
  is not running. The system was up last three days without interaction,
- but it could have updated itself?
+ but it could have updated itself - I see an update Sunday
+ 
+ $ ls -lt /snap
+ total 20
+ drwxr-xr-x 5 root root 4096 Oct  9 17:33 ubuntu-core
+ 
  
  This is on a Dragonboard.
  
  Starting it fails as follows:
  
  pat-mcgowan@localhost:~$ sudo systemctl status snapd
  ● snapd.service - Snappy daemon
-    Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: 
enabled)
-    Active: inactive (dead) (Result: exit-code) since Tue 2016-10-11 19:34:19 
UTC; 30s ago
-   Process: 3434 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
-  Main PID: 3434 (code=exited, status=1/FAILURE)
+    Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: 
enabled)
+    Active: inactive (dead) (Result: exit-code) since Tue 2016-10-11 19:34:19 
UTC; 30s ago
+   Process: 3434 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)
+  Main PID: 3434 (code=exited, status=1/FAILURE)
  
  Oct 11 19:34:18 localhost.localdomain systemd[1]: snapd.service: Unit entered 
failed state.
  Oct 11 19:34:18 localhost.localdomain systemd[1]: snapd.service: Failed with 
result 'exit-code'.
  Oct 11 19:34:19 localhost.localdomain systemd[1]: snapd.service: Service 
hold-off time over, scheduling restart.
  Oct 11 19:34:19 localhost.localdomain systemd[1]: Stopped Snappy daemon.
  Oct 11 19:34:19 localhost.localdomain systemd[1]: snapd.service: Start 
request repeated too quickly.
  Oct 11 19:34:19 localhost.localdomain systemd[1]: Failed to start Snappy 
daemon.
  
  From syslog:
  Oct 11 19:39:38 localhost systemd[1]: snapd.service: Main process exited, 
code=exited, status=1/FAILURE
  Oct 11 19:39:38 localhost systemd[1]: snapd.service: Unit entered failed 
state.
  Oct 11 19:39:38 localhost systemd[1]: snapd.service: Failed with result 
'exit-code'.
  Oct 11 19:39:39 localhost systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
  Oct 11 19:39:39 localhost systemd[1]: Stopped Snappy daemon.
  Oct 11 19:39:39 localhost systemd[1]: Started Snappy daemon.
  Oct 11 19:39:39 localhost snapd[3538]: error: cannot downgrade: snapd is too 
old for the current system state (patch level 4)
  Oct 11 19:39:39 localhost systemd[1]: snapd.service: Main process exited, 
code=exited, status=1/FAILURE
  Oct 11 19:39:39 localhost systemd[1]: snapd.service: Unit entered failed 
state.
  Oct 11 19:39:39 localhost systemd[1]: snapd.service: Failed with result 
'exit-code'.
  Oct 11 19:39:39 localhost systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
  Oct 11 19:39:39 localhost systemd[1]: Stopped Snappy daemon.
  Oct 11 19:39:39 localhost systemd[1]: snapd.service: Start request repeated 
too quickly.
  Oct 11 19:39:39 localhost systemd[1]: Failed to start Snappy daemon.
  Oct 11 19:39:39 localhost systemd[1]: snapd.socket: Unit entered failed state.
  Oct 11 19:41:37 localhost rsyslogd-2007: action 'action 11' suspended, next 
retry is Tue Oct 11 19:43:07 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632453

Title:
  snapd won't start on dragonboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632453/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to