Can't update apps / migrate / share logs

Bonjour ! C’est la mouise.

:uk: My YunoHost server

Hardware: Odroid board with included hard drive
YunoHost version:
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes
If yes, please explain: I’ve used apt-get upgrade before to try solving older issues

Description of my issue

I can’t upgrade / migrate my Yunohost instance, it seems to have issues with packages. Since I can’t share logs either because I’m getting an error too, here is a screenshot (below french post).

:fr: Mon serveur YunoHost

Matériel: Carte ARM Odroid avec disque dur
Version de YunoHost:
J’ai accès à mon serveur : En SSH | Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : oui
Si oui, expliquer: Pour essayer de résoudre d’autres problèmes, j’ai effectué un apt-get update puis apt-get upgrade

Description du problème

Je ne peux plus mettre à jour ou migrer mon instance. Je ne peux pas partager les logs non plus à cause d’une autre erreur, voici donc une capture d’écran.

Merci beaucoup !

PS : J’ai un autre serveur Yunohost à la maison, et tout se passe bien dessus :wink:

Apparement il s’agit d’un problème de résolution DNS

Est-ce que tu arrives à faire tourner le diagnostique pour voir si ça donne + de détails / piste sur le soucis ?

De suite,

Hmoké, pas d’ipv4 c’est un problème :thinking:

Si tu as un accès terminal, que raconte ping -c3, et ip -br a ?

ping -c3 :
PING ( 56(84) bytes of data. 64 bytes from icmp_seq=1 ttl=119 time=3.94 ms 64 bytes from icmp_seq=2 ttl=119 time=3.94 ms 64 bytes from icmp_seq=3 ttl=119 time=3.89 ms

ip -br a :
lo UNKNOWN ::1/128 eth0 UP 2a00:5881:8114:500::2/128 fe80::21e:6ff:fe37:64ed/64

Oké du coup tentons:

ping -c3

et regardons

cat /etc/resolv.conf

ping -c3

ping: Temporary failure in name resolution

cat /etc/resolv.conf

Generated by NetworkManager

There should be a nameserver-line there. Usually it is provided by dnsmasq or resolvconf, but as a quick hack, you can add a nameserver yourself:

$ sudo echo 'nameserver' >> /etc/resolv.conf 

The value will probable be overwritten later on, but at least you can continue the migration.

This is what I got when trying to upgrade, not migrate.

Edit : Migration doesn’t work either, here is the log :

The errors are similar when apt is not able to find

Did you add the nameserver to \etc\resolv.conf?

My Yunohost does not have the source entry ( that gives problems for the script. Do you know why it is there?

I added the nameserver in \etc\resolv.conf is for hd-idle, a script to spin-down disk after a period of idle time. But it don’t seems to work. How can I remove it ?

EDIT : I rebooted, still have access to everything but still can’t do anything. What’s new ? I’m getting a mail saying :

Failed to resolve IPv4/IPv6 for ['', ''] ?

Every 10 minutes :sweat_smile:

Usually you would run apt remove adelolmo. If you already started the migration to 11, it could be that it hangs a bit in limbo. Give it a try, and if it does not work, post the output that apt gives you.
When you removed it successfully, you can remove the adelolmo-source. You’ll find it as a separate file in /etc/apt/sources.list.d/, or as a line in the main apt-sources file at /etc/apt/sources.list.

As long as things are not repaired, you have to add a nameserver manually after rebooting. (Have a look at /etc/resolv.conf, I think it does not have the IP you added before anymore: the file got regenerated on boot).

Thanks for your time :slight_smile:

I’ve removed adelolmo from /etc/apt/sources.list.d/ with success and managed to check if there was upgrades available. But there are failing :roll_eyes:
This is the logs I get :

The nameserver is still present in \etc\resolv.conf file thought.

I am not quite sure which process is trying to reach the Yunohost-nameservers.

I’d speculate it is dnsmasq, checking that the DNS for your Yunohost still matches the IP address from your ISP (do you use a or address?). Whichever process is sending those emails probably lives a level deeper in the structure and is responsible for setting the nameserver in resolv.conf in the first place.

For now it is annoying, but more a symptom of your problem than the cause.

You also apt remove adelolmo’d first, didn’t you?

2022-09-25 22:23:44,445: INFO - + The following packages have unmet dependencies:
2022-09-25 22:23:44,861: INFO - +  ssowat : Depends: nginx-extras (>= 1.6.2) but it is not going to be installed
2022-09-25 22:23:44,916: WARNING - E: Unable to correct problems, you have held broken packages.


$ sudo apt update 
$ sudo apt install --fix-broken
$ sudo apt-mark showhold

On my Yunohost the last command has no output: no packages are being held. It could be that the result is the same for you (I got the error once while nothing was being held).

Let’s have a look at the held packages, and continue from there!

Adelolmo isn’t a package, but I removed Hd-idle, who was the package related to the adelolmo sources.

So, this is what I got :roll_eyes:

sudo apt update

Hit:1 bullseye InRelease
Hit:2 bullseye InRelease
Hit:3 bullseye-security InRelease
Hit:4 bullseye-updates InRelease
Hit:5 bullseye InRelease
Hit:6 bullseye InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
215 packages can be upgraded. Run 'apt list --upgradable' to see them.

sudo apt install --fix-broken

Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 215 not upgraded.

sudo apt-mark showhold


Hi Optogram,

It has been a couple of days, sorry for not replying any sooner.

I managed to get my server upgraded and repaired after losing Yunohost due to conflicts while apt-get dist-upgrade.

All four held packages are Yunohost-related. In my case none of those were held.

Do you have backups?

What I would do:

  • unhold the four Yunohost-packages (with apt-mark unhold ...)
  • apt update to get the last package info
  • Your /etc/apt/sources.list (and .d) are already on Bullseye, so the migration has started. There is ‘no way back’ → we go forward
  • apt-get dist-upgrade will now upgrade most (if not all) packages

If there is a conflict, lets have a look then. With no conflicts, you can continue the migrations.

  • first just run migrations in general, yunohost migrations run, read the message, and run it again with the disclaimer
  • most probably Yunohost will tell that a migration is in limbo. I skipped 0021_…, and ran migrations again.

My server was in much worse condition than yours, I’m confident you’ll get it done! :slight_smile:


No problem, thanks for your time.

Well, the apt-get dist-upgrade went well, but migrations won’t work, it seems that my system is in-between two upgrades or couldn’t properly execute migration.

This is what I got :

That is a good start! :slight_smile:

and that is a bit as expected after it ran into problems the first time. Now it wants to pick up the upgrade, but you already did it.

What I did was

$ sudo yunohost tools migrations run 0021_migrate_to_bullseye --skip

After that, Yunohost will pick up migrations at 0022.

1 Like

Okay ! I executed the last command, tried to do the migration, 3/4 of the remaining tasks passed :smiley:

I’m left with that : Php 7.3 to 7.4, although I have php 7.4 listed with dpkg --list | grep postgresql13 command.

But I still can’t update apps, but it seems to be linked with the above issue.

Since the buster/bullseye migration was probably bruteforced using apt instead of finishing “properly” the migration, you’ll need to manually sudo apt install php7.4-fpm

and you may encounter other issues related to missing php7.4-fpm dependencies

1 Like