What type of hardware are you using: VPS bought online
What YunoHost version are you running: 11.3.2
How are you able to access your server: SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no
Describe your issue
I am trying to update my yunohost server to Debian Bookworm and I have an issue similar to @dosch with updating to Yunohost 12 (see here: Updating to YNH 12 - Issues and questions).
The migration process took less than 15 minutes. I hope this is a helpful clue for someone. The docs say it should take hours.
Where I am stuck: I can’t update any of my app packages because I get an error saying they need Yunohost 12. And I can’t update to Yunohost 12 because there are no listed migrations to complete.
My migration/upgrade process so far
I have done the following:
- made a full backup via web admin
- updated packages via web admin ‘home/software update’ then ‘update all packages’
- run migration via command line using
yunohost tools migrations run - restarted the server using
yunohost tools reboot
I have followed the information-seeking suggested in @dosch’s post and got the following
Re-run migration, look for errors
When I run yunohost tools migrations run I get the result: Info: No migrations to run
Force migration
When I run apt update && apt full-upgrade as suggested by Aleks here (Updating to YNH 12 - Issues and questions - #9 by Aleks) I get this output:
Hit:1 https://packages.sury.org/php bullseye InRelease
Hit:2 https://forge.yunohost.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye InRelease
Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
Hit:5 http://deb.debian.org/debian bullseye-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Find version
When I run lsb_release -a I get the following output:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Confirm version
When I run cat /etc/debian_version I get the output:
11.11
Confirm version again
When I run yunohost --version I get the output:
yunohost:
repo: stable
version: 11.3.0.2
yunohost-admin:
repo: stable
version: 11.3.0
moulinette:
repo: stable
version: 11.3.0
ssowat:
repo: stable
version: 11.3.0
Try updating and look for errors
When I run apt full-upgrade I get the following output:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Look for errors in the debug
The yunohost webadmin logs don’t show a log for migration, but the webadmin lists the system as having no migrations to complete.
I can run yunohost tools migrations run --debug though, and get the following:
152 DEBUG initializing base actions map parser for cli
153 DEBUG loading actions map
157 DEBUG building parser...
163 DEBUG building parser took 0.006s
165 DEBUG acquiring lock...
179 DEBUG lock has been acquired
347 DEBUG loading python module yunohost.tools took 0.168s
350 DEBUG processing action [25382.1]: yunohost.tools.migrations.run with args={'targets': [], 'skip': False, 'force_rerun': False, 'auto': False, 'accept_disclaimer': False}
350 DEBUG Loading migration 0021_migrate_to_bullseye…
352 DEBUG Loading migration 0022_php73_to_php74_pools…
352 DEBUG Loading migration 0023_postgresql_11_to_13…
353 DEBUG Loading migration 0024_rebuild_python_venv…
353 DEBUG Loading migration 0025_global_settings_to_configpanel…
353 DEBUG Loading migration 0026_new_admins_group…
354 DEBUG Loading migration 0027_migrate_to_bookworm…
361 INFO No migrations to run
361 DEBUG action [25382.1] executed in 0.012s
362 DEBUG lock has been released
My deductions
Something is preventing the migration to Debian Bookwork from completing successfully AND is preventing Yunohost from recognising it as the issue.
What could this be?
I wonder if its to do with line 350 above. But I don’t have enough skills to know that that line is referring to, or how I might fix it.
Here are the other logs from the webadmin
I have shared the logs I have below. I can’t see anything helpful in them. If you see something useful there, please let me know! Thank you for reading. <3
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
