Core fails to update, core 16 on RPi3 (Nextcloud Box)


#1

Hi,

my Nextcloud Box on RPi3 is giving messages:

reboot scheduled to update the system
With at time in like 10 minutes from now.

So I went and checked snap status core: I have 16-2.39, while stable would be 16-2.40
Makes sense it tries to run this update, but somehow fails. After new login the situation is the same.

snap changes reports Status: error

Any hints where I should start investigating?
snap list:

Name Version Rev Tracking Publisher Notes
core 16-2.39 6961 stable canonical✓ core
nextcloud 15.0.8snap3 13975 stable nextcloud✓ -
pi2-kernel 4.4.0-1111.120 90 stable canonical✓ kernel
rsync 1.0.0 11 stable cachio -
snapweb 0.26-11 323 stable canonical✓ -
wdl-nextcloud 16.04-0.5-6 9 stable canonical✓ gadget

Many thanks!


#2

What do you see with snap changes and then use snap change (changenumber) to see the details of the one in status “error” assuming one is.


#3

the highest ID from snap changes is 229, so here is the output from snap change 229

Status Spawn Ready Summary
Done today at 18:05 CEST today at 18:06 CEST Ensure prerequisites for “core” are available
Undone today at 18:05 CEST today at 18:06 CEST Download snap “core” (7398) from channel “stable”
Done today at 18:05 CEST today at 18:06 CEST Fetch and check assertions for snap “core” (7398)
Undone today at 18:05 CEST today at 18:06 CEST Mount snap “core” (7398)
Undone today at 18:05 CEST today at 18:06 CEST Run pre-refresh hook of “core” snap if present
Undone today at 18:05 CEST today at 18:06 CEST Stop snap “core” services
Undone today at 18:05 CEST today at 18:06 CEST Remove aliases for snap “core”
Undone today at 18:05 CEST today at 18:06 CEST Make current revision for snap “core” unavailable
Undone today at 18:05 CEST today at 18:06 CEST Copy snap “core” data
Undone today at 18:05 CEST today at 18:06 CEST Setup snap “core” (7398) security profiles
Undone today at 18:05 CEST today at 18:06 CEST Make snap “core” (7398) available to the system
Error today at 18:05 CEST today at 18:06 CEST Automatically connect eligible plugs and slots of snap “core”
Hold today at 18:05 CEST today at 18:06 CEST Set automatic aliases for snap “core”
Hold today at 18:05 CEST today at 18:06 CEST Setup snap “core” aliases
Hold today at 18:05 CEST today at 18:06 CEST Run post-refresh hook of “core” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Start snap “core” (7398) services
Hold today at 18:05 CEST today at 18:06 CEST Remove data for snap “core” (6676)
Hold today at 18:05 CEST today at 18:06 CEST Remove snap “core” (6676) from the system
Hold today at 18:05 CEST today at 18:06 CEST Clean up “core” (7398) install
Hold today at 18:05 CEST today at 18:06 CEST Run configure hook of “core” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Ensure prerequisites for “pi2-kernel” are available
Hold today at 18:05 CEST today at 18:06 CEST Download snap “pi2-kernel” (97) from channel “stable”
Hold today at 18:05 CEST today at 18:06 CEST Fetch and check assertions for snap “pi2-kernel” (97)
Hold today at 18:05 CEST today at 18:06 CEST Mount snap “pi2-kernel” (97)
Hold today at 18:05 CEST today at 18:06 CEST Run pre-refresh hook of “pi2-kernel” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Stop snap “pi2-kernel” services
Hold today at 18:05 CEST today at 18:06 CEST Remove aliases for snap “pi2-kernel”
Hold today at 18:05 CEST today at 18:06 CEST Make current revision for snap “pi2-kernel” unavailable
Hold today at 18:05 CEST today at 18:06 CEST Copy snap “pi2-kernel” data
Hold today at 18:05 CEST today at 18:06 CEST Setup snap “pi2-kernel” (97) security profiles
Hold today at 18:05 CEST today at 18:06 CEST Make snap “pi2-kernel” (97) available to the system
Hold today at 18:05 CEST today at 18:06 CEST Automatically connect eligible plugs and slots of snap “pi2-kernel”
Hold today at 18:05 CEST today at 18:06 CEST Set automatic aliases for snap “pi2-kernel”
Hold today at 18:05 CEST today at 18:06 CEST Setup snap “pi2-kernel” aliases
Hold today at 18:05 CEST today at 18:06 CEST Run post-refresh hook of “pi2-kernel” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Start snap “pi2-kernel” (97) services
Hold today at 18:05 CEST today at 18:06 CEST Remove data for snap “pi2-kernel” (82)
Hold today at 18:05 CEST today at 18:06 CEST Remove snap “pi2-kernel” (82) from the system
Hold today at 18:05 CEST today at 18:06 CEST Clean up “pi2-kernel” (97) install
Hold today at 18:05 CEST today at 18:06 CEST Run configure hook of “pi2-kernel” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Ensure prerequisites for “nextcloud” are available
Hold today at 18:05 CEST today at 18:06 CEST Download snap “nextcloud” (15125) from channel “stable”
Hold today at 18:05 CEST today at 18:06 CEST Fetch and check assertions for snap “nextcloud” (15125)
Hold today at 18:05 CEST today at 18:06 CEST Mount snap “nextcloud” (15125)
Hold today at 18:05 CEST today at 18:06 CEST Run pre-refresh hook of “nextcloud” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Stop snap “nextcloud” services
Hold today at 18:05 CEST today at 18:06 CEST Remove aliases for snap “nextcloud”
Hold today at 18:05 CEST today at 18:06 CEST Make current revision for snap “nextcloud” unavailable
Hold today at 18:05 CEST today at 18:06 CEST Copy snap “nextcloud” data
Hold today at 18:05 CEST today at 18:06 CEST Setup snap “nextcloud” (15125) security profiles
Hold today at 18:05 CEST today at 18:06 CEST Make snap “nextcloud” (15125) available to the system
Hold today at 18:05 CEST today at 18:06 CEST Automatically connect eligible plugs and slots of snap “nextcloud”
Hold today at 18:05 CEST today at 18:06 CEST Set automatic aliases for snap “nextcloud”
Hold today at 18:05 CEST today at 18:06 CEST Setup snap “nextcloud” aliases
Hold today at 18:05 CEST today at 18:06 CEST Run post-refresh hook of “nextcloud” snap if present
Hold today at 18:05 CEST today at 18:06 CEST Start snap “nextcloud” (15125) services
Hold today at 18:05 CEST today at 18:06 CEST Remove data for snap “nextcloud” (13448)
Hold today at 18:05 CEST today at 18:06 CEST Remove snap “nextcloud” (13448) from the system
Hold today at 18:05 CEST today at 18:06 CEST Clean up “nextcloud” (15125) install
Hold today at 18:05 CEST today at 18:06 CEST Run configure hook of “nextcloud” snap if present
Done today at 18:05 CEST today at 18:06 CEST Consider re-refresh of “core”, “pi2-kernel”, “nextcloud”


Make snap “core” (7398) available to the system

2019-08-18T18:06:21+02:00 INFO Requested system restart.


Automatically connect eligible plugs and slots of snap “core”

2019-08-18T18:06:27+02:00 INFO Waiting for restart…
2019-08-18T18:06:27+02:00 INFO Waiting for restart…
2019-08-18T18:06:28+02:00 INFO Waiting for restart…
2019-08-18T18:06:28+02:00 INFO Waiting for restart…
2019-08-18T18:06:28+02:00 INFO Waiting for restart…
2019-08-18T18:06:29+02:00 INFO Waiting for restart…
2019-08-18T18:06:29+02:00 INFO Waiting for restart…
2019-08-18T18:06:29+02:00 INFO Waiting for restart…
2019-08-18T18:06:30+02:00 INFO Waiting for restart…
2019-08-18T18:06:31+02:00 ERROR cannot finish core installation, there was a rollback across reboot

Not sure how to understand this… I’m afraid.
Dependencies between packages…?
My hardware is RPi3. With a PiDrive attached, as from the kit.

Most grateful for your time :slight_smile:


#4

After more reading here, changes category to snapd.
Version of snapd is 2.39


#5

What happens if you restart the machine?


#6

Just tried again. I then check snap refresh, shortly after it wants to reboot due to updates.

But then: Same thing as before… errors in the snap changes list and still the outdated versions.

I tried to test the connection, which seems OK.

user@host:~$ snap refresh --list
Name Version Rev Publisher Notes
core 16-2.40 7398 canonical✓ core
nextcloud 15.0.10snap3 15125 nextcloud✓ -
pi2-kernel 4.4.0-1118.127 97 canonical✓ kernel

Thanks!


#7

Tried a snap login
Then snap whoami shows my email.
Still, after a scheduled reboot due to updating (I’m waiting like 10minutes or so): Same situation.

Thanks for reading


#8

If I’m understanding correctly, when core is refreshed, your box reboots, tries the new core, and it fails, and then reboots again and falls back to the old core? If so, could we get logs of what happened during the attempt with the new core?


#9

This is my perception, yes.

Happy to help, but in need of assistance how to get hold of the right stuff…


#10

Sorry the delay, had to struggle with dyndns… to get my ssh back.

Looking at new attempts here, with same results.
As above…

Is there a mount problem?
Done <timestamp> Fetch and check assertions for snap "core" (7398)
But next lines only talk about Undone

What else in terms of logs would be usefull?

Many thanks indeed


#11

Looks like this has resolved, what I did:

  • Manually snap refresh pi2-kernel
  • Manually snap refresh core, before the reboot
  • then things looked good
  • now I even could get the nextcloud back to the latest stable :smile:

Still a bit puzzling to me: Is there/should I have some kind of pi3-kernel?

Even pi4-kernel? Then I might be out shopping soon :smiley:

Thanks and sorry for the noise


#12

AFAIK, no there is not a pi3-kernel specific for UC16. However there is for UC18 if you upgrade to that, but all the pi kernels are published under pi-kernel for UC18 are under various tracks for the different pi’s on UC18 (i.e. there’s a pi-kernel track for 18-pi3, 18-pi2, and 18-cm3).

Not yet unfortunately, when this happens I’m not sure if one will be published for use with UC16, I imagine it will probably only be available for UC18, but the closest we have yet is @ogra’s work at Support for Raspberry Pi 4 which is unofficial and for development/prototyping only.