Unable to upgrade from 23/stable to 24/stable. Mysql won't start. #2597
Comments
|
your log so one or more of the installed apps may be causing problems. its not obvious within your logs which apps are causing your issue. so you'll have to do a little research. considering you're on 23/stable you've got several upgrades to do before you reach 27/stable. that might take a while on your try upgrading apps in OCC. you can upgrade or disable apps in OCC. also see FAQ. afterwards try refresh again. |
|
The apps are upgraded at least in 23/stable. And I believe the The problem is with Mysql. It is failing to start and it is not easy to get a handle on why that is happening in 24/stable and not 23/stable From the journalctl log it is clear it is falling over for a reason What is most confusing is the actual log from |
|
is your |
|
I guess so. It is a RPi 3 and has been using Ubuntu core. It's never been a problem before, but I know Ubuntu core officially supports RPi3 |
|
okay, so its a @Pilzinsel64 do you know if 32Bit mysql is still supported? maybe you can assist? |
|
Well, the question is how do you upgrade Ubuntu core to 64 bit if it was 32 bit ? And is this the actual problem. Can a developer chime in on what happened between the mysql version in 23/stable to 24/stable ? FWIW this is the pi3 info |
that is not possible. you'll need to export your data, reinstall nextcloud snap on 64Bit core and reimport your data... but wait until your mysql issue is confirmed by one of the devs. |
|
To be honest, if I have to reinstall anyway, I am tempted just to put Debian and Docker on and be done with it. I thought ubuntu-core and snaps were to isolate the applications from the OS and, hence, would make maintenance easy. For sure, I don't see what changed between 23 & 24, but something must have. |
I'm not sure this matters, does it? We have published armhf snaps from the beginning, and still do. This is supported.
You can actually find that out for yourself with a quick glance at the CHANGELOG. I'm assuming you're updating from 23.0.5snap1 to 24.0.7snap1, which covers two mysql updates, one to 8.0.30, and another to 8.0.31. It's possible that you're being bitten by a bug in one of those, but it's also possible you simply ran out of RAM during the upgrade process and it corrupted the database. Given your use of the pi3, that seems like the most likely scenario. I suggest removing the failed upgrade revision and trying the refresh again, keeping a careful eye on your RAM.
That's true, and as far as I can tell isn't invalidated by what you and @scubamuc were discussing: if you need to reinstall your OS, no level of separation between your apps and your OS will save you from needing to backup and reinstall the apps on the OS. Even HA systems like Kubernetes work that way, by migrating the apps off the OS to another one before taking the node down. |
If that were the case why would reverting it back to 23/stable fix it? It is the same DB obviously so I don't think it is corrupted, but the new mysql barfs anyway. |
Because of the way this snap utilizes snapd features. When you upgrade from revision A to revision B, snapd makes a copy of revision A's data (which includes the database), then fires up revision B on that data. Revision B has a new mysql in it, upgrades the database, and chokes for whatever reason in the middle, corrupting it. So you revert back to revision A, which fires up on the exact same data right before the copy was made, i.e. before B garbled the database. For completeness, note that the snap does not by default do this for Nextcloud's data directory. It's just too large to make it feasible for most installations, so there's only ever one copy of that. |
|
Fairy nuff, but how does that really help me to debug the issue? Mysql seems unable to start before it is accessing databases else that would be shown in the stack trace. As it is there is just the weird ? over a libc error causing a segfault, which seems to indicate the underlying system is not compatible. In which case how are the snaps isolated from the host system dependencies then ? |
|
@develroo so I've had another look at your logs, especially possible issues with 3rd party apps that have been deprecated or are not upgradeable... you have a fairly long list:
The only app I can't relate to is |
|
Ooops... I err... sorry about that! here is a working app list from my testing instance for comparisson: |
|
Well, I can try and disable all plugins I guess. I'll let you know. |
|
So FWIW I disabled as many apps as I could and re-ran the refresh. And now the mysql snap seems to start ok However, there is no web interface and you cannot configure it from the command line any more. This is because the php service is still waiting to connect to mysql So still broken, alas. |
|
This issue is stale because it has been without activity for 60 days. It will be closed after 7 more days of inactivity. |
Describe the bug
When trying to refresh/upgrade 23/stable to 24/stable refresh is fine but
nextcloud.mysqlfails to start after. Reverting will go back to a working nextcloud and mysql.Expected behavior
mysql should start as normal as it works on 23/stable
OS/snapd/snap version
Logs
.NB Because this is ubutu core the
php-fmcommand it not availible to the system.nextcloud-log.debug.txt
The text was updated successfully, but these errors were encountered: