Can't migrate to bookworm / issue with libc-dev

Hello,

Thank you very much for the official migration to Yunohost 12. I have 2 yunohost servers in production. To be able to install the upgrade, on one of them, I have to update some blocking packages upstream: anacron and libc6. However, on both, the migration explodes the sso portal. Impossible to get the portal with tiles on both servers. Impossible to access the vaultwarden administration web page…
As both my servers are in production, I can’t have fun migrating them and then reverting to the backup, as the migrations are wobbly. Data is written by users in the meantime… And every time I restore, I lose data by overwriting it with the backup.
Thank you for your advice.

That’s a bold migration plan. Stop restoring the apps, I am almost sure we can fix them after migration.

Do not be vague. Show errors and logs, and what’s actually displayed on screen. Asking for help efficiently | Yunohost Documentation

Logs? Do not rephrase what it on screen, please.

For packages to be reinstalled before migration, here are the logs for libc6: https://paste.yunohost.org/raw/abuhiribav.

For anacron, the upgrade stops at 66% and never restarts, so no logs.

For sso, I have no logs. I simply can’t access the sso portal anymore. When I click on the “portal” icon on my yunohost administration web page, which takes me to the https://monsite.fr/yunohost/sso?r=aHR0cHM6Ly9wYXNzLnN0dC1sb2dpc3RpcXVlLm page. The web page doesn’t work. My browser responds:

This site is inaccessible

Check if the address monsite.fr is correct.

  • If there is no error, try a Windows network diagnostic.

DNS_PROBE_FINISHED_NXDOMAIN

Same error with the vaultwarden administration page, which is monsite.fr\vaultwarden\admin.

I’ve already posted this problem when testing the beta version of yunohost 12. And I dropped the fix thinking that it would be fixed at the official release.

Is it SSOwat or nginx crashing, or something else, I have no way of knowing.

What is the output of the following command?

sudo aptitude why libc-dev-bin libc6-dev unscd apticron

Sorry, you tried to hide your domain, but it is encoded in the gibberish after r=, and its base64 decode shows that it does not include the “fr” at the end.

Can you try with this? aHR0cHM6Ly9wYXNzLnN0dC1sb2dpc3RpcXVlLmZy

It is a DNS issue, so that is not NGINX’s fault. Do you use a VPN or something that might alter your DNS like Adguard? Is your domain correctly registered in the Domains menu of the webadmin?

sudo aptitude why libc-dev-bin libc6-dev unscd apticron
[sudo] password for admin:
Automatically installed, current version 1.2.5, priority optional
The candidate version 1.2.5+nmu1 has priority optional
No dependencies require to install apticron

Oh sorry I thought I was smart by merging the commands into one, but that does not help me.

sudo aptitude why libc-dev-bin
sudo aptitude why libc6-dev 
sudo aptitude why unscd

But now we know you do not need apticron, so let’s remove it: sudo aptitude remove apticron

I don’t have a VPN, adguard or anything. I reach my server on the web as usual.
Everything works perfectly at SSO or DNS level in yunohost 11. Once I upgrade to version 12, I don’t know what breaks. But my configuration no longer works because I can’t reach the SSO portal.

sudo aptitude why libc-dev-bin
sudo aptitude why libc6-dev
sudo aptitude why unscd
i protection-agent-dkms Depends libc6-dev
i A libc6-dev Depends libc-dev-bin (= 2.31-13+deb11u11)
i protection-agent-dkms Depends libc6-dev
ih yunohost Depends unscd

sudo aptitude why protection-agent-dkms

Do you have some kind of virus or malware protection installed?

Yes, I have virus and malware protection on my yunohost servers.

Please refer to their documentation to see if they are compatible with Bookworm. You may need to uninstall them for the migration to be successful.

There are no compatibility issues with Bookworm. This product runs on all my .deb servers, either Debian or Ubuntu, and has never prevented me from upgrading these servers.

(splitted from the original thread to avoid flooding the announcement thread with debugging stuff)

1 Like

Thanks a lot for the help. I found out about Yunohost 12 SSO portal access: it was indeed the DNS configuration of my server working in Yunohost 11 but not in version 12. With the right modifications, I’m back in business. I also had to repair my fail2ban. Everything seems ok for this first server…
I’ll see about the other one later…

1 Like

Hello,

I have just migrated my second server. Just by correcting the DNS of my Yunohost server, the migration went through without even reinstalling anacron or libc6. (I had set myself the challenge of attempting the upgrade without touching anything upstream).
Everything worked perfectly. I now have access to the SSO portal and the Vaultwarden admin web page. I had to reconfigure Vaultwarden’s smtp, following the migration. My server is up and running, no incidents to report.
Thanks for your support.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.