Snap refresh or new install stuck at 'Run configure hook of "core" snap if present'
Selene Scriven
selene.scriven at canonical.com
Thu Mar 2 08:15:52 UTC 2017
* Joseph Rushton Wakeling <joseph.wakeling at webdrake.net> wrote:
> On 24/02/17 14:08, Martin Winter wrote:
> >Curious if anyone has seen the same. All my Ubuntu 16.04
> >Servers have this issue. (Approx 10 Servers which are part of
> >my CI system)
>
> Saw the same on a Debian Sid install that I was using to test
> my ldc2 snap package a couple of days ago. However, it didn't
> persist -- a few minutes ago I was able to successfully install
> the core and ldc2 snaps.
I'm not sure if it's the same thing, but one of my devices got
stuck for a while yesterday. Every snap command got stuck for
about 8 minutes, and I found this in the syslog right before that
started:
Mar 1 05:55:33 localhost /usr/lib/snapd/snapd[1371]: taskrunner.go:353: DEBUG: Running task 29 on Do: Generate device key
After that finished, snapd started responding again and other
snap commands were able to complete. Not sure what was on the
console at the time.
I noticed this because my automated tests froze while trying to
get in contact with a fresh-flashed device... ssh was already
confirmed to work, and it stopped while attempting to run "snap
version".
-- Selene
More information about the Snapcraft
mailing list