I'm assuming snap changes would give you that information? Here is the
output of that command

ID   Status  Spawn                   Ready  Summary
4    Abort   yesterday at 19:52 EDT  -      Auto-refresh snap "core"

On Wed, Sep 11, 2019 at 12:21 PM Zygmunt Krynicki <
<email address hidden>> wrote:

> ** Changed in: snappy
>        Status: New => Triaged
>
> ** Changed in: snappy
>    Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1843589
>
> Title:
>   core snap stuck refreshing
>
> Status in Snappy:
>   Triaged
>
> Bug description:
>   All of our snaps stopped working overnight, attempting to run the snap
>   gives the following error:
>
>   cannot locate base snap core: No such file or directory
>
>   Running snap changes shows that 12 hours ago an auto-refresh started
>   for the core snap that is still in progress which seems like a really
>   long time.
>
>   output of "snap changes":
>
>   ID   Status  Spawn                   Ready                   Summary
>   1    Done    yesterday at 10:16 EDT  yesterday at 10:16 EDT  Initialize
> system state
>   2    Done    yesterday at 10:17 EDT  yesterday at 10:17 EDT  Install
> "ftptransfer" snap from file "ftptransfer_1.0_amd64.snap"
>   3    Done    yesterday at 10:17 EDT  yesterday at 10:17 EDT  Initialize
> device
>   4    Doing   yesterday at 19:52 EDT  -
>  Auto-refresh snap "core"
>
>   Running "snap tasks --last=auto-refresh" gives the following output:
>   Status  Spawn                   Ready                   Summary
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Ensure
> prerequisites for "core" are available
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Download snap
> "core" (7713) from channel "stable"
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Fetch and check
> assertions for snap "core" (7713)
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Mount snap
> "core" (7713)
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Run pre-refresh
> hook of "core" snap if present
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Stop snap "core"
> services
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Remove aliases
> for snap "core"
>   Done    yesterday at 19:52 EDT  yesterday at 19:52 EDT  Make current
> revision for snap "core" unavailable
>   Doing   yesterday at 19:52 EDT  -                       Copy snap "core"
> data
>   Do      yesterday at 19:52 EDT  -                       Setup snap
> "core" (7713) security profiles
>   Do      yesterday at 19:52 EDT  -                       Make snap "core"
> (7713) available to the system
>   Do      yesterday at 19:52 EDT  -                       Automatically
> connect eligible plugs and slots of snap "core"
>   Do      yesterday at 19:52 EDT  -                       Set automatic
> aliases for snap "core"
>   Do      yesterday at 19:52 EDT  -                       Setup snap
> "core" aliases
>   Do      yesterday at 19:52 EDT  -                       Run post-refresh
> hook of "core" snap if present
>   Do      yesterday at 19:52 EDT  -                       Start snap
> "core" (7713) services
>   Do      yesterday at 19:52 EDT  -                       Clean up "core"
> (7713) install
>   Do      yesterday at 19:52 EDT  -                       Run configure
> hook of "core" snap if present
>   Doing   yesterday at 19:52 EDT  -                       Consider
> re-refresh of "core"
>
>   I'm not low on space on the hard disk I have roughly 110GB free
>
>   This is a virtual machine running on hyperv
>
>   Here is the output from snap --version
>
>   snap    2.40
>   snapd   2.40
>   series  16
>   ubuntu  16.04
>   kernel  4.4.0-157-generic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1843589/+subscriptions
>