Hello!
Pour ceux qui ont leur Yunohost hébergé chez SW, qui sont bloqués lors de l’installation de la dernière mise à jour de yunohost et de mariadb-server, et qui ont comme message d’erreur suivant :
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mariadb-server-10.1 (10.1.37-0+deb9u1) ...
logger: socket /dev/log: Connection refused
logger: socket /dev/log: Connection refused
dpkg: error processing package mariadb-server-10.1 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server:
mariadb-server depends on mariadb-server-10.1 (>= 10.1.37-0+deb9u1); however:
Package mariadb-server-10.1 is not configured yet.
dpkg: error processing package mariadb-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of yunohost:
yunohost depends on mariadb-server; however:
Package mariadb-server is not configured yet.
dpkg: error processing package yunohost (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of yunohost-admin:
yunohost-admin depends on yunohost (>= 2.7.6); however:
Package yunohost is not configured yet.
dpkg: error processing package yunohost-admin (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mariadb-server-10.1
mariadb-server
yunohost
yunohost-admin
Il semblerait que Scaleway modifie le machine-id sur leurs kernels, et que ça crée des problèmes avec le logger systemd.
Par exemple, j’avais le machine-id suivant :
root@lovelace:~# cat /etc/machine-id
26da2c29c6a545fd9af95d29ca9b5a5a
9a5
Après avoir cherché pendant des heures, j’ai enfin trouvé la solution (ici), il suffit de supprimer la deuxième ligne pour n’avoir plus que :
root@lovelace:~# cat /etc/machine-id
26da2c29c6a545fd9af95d29ca9b5a5a
Après un petit nettoyage des logs systemd :
SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create --clean --remove
Et enfin un redémarrage du service de log systemd :
systemctl restart systemd-journald.service
systemctl restart systemd-journald.socket
Et zou, l’upgrade est possible et fonctionne sans aucun soucis
root@lovelace:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up mariadb-server-10.1 (10.1.37-0+deb9u1) ...
Setting up mariadb-server (10.1.37-0+deb9u1) ...
Setting up yunohost (3.3.1) ...
Regenerating configuration, this might take a while...
Success! The configuration has been updated for service 'metronome'
Warning: The configuration file '/etc/nginx/conf.d/mydomain.com.conf' has been manually modified and will not be updated
Warning: The configuration file '/etc/nginx/conf.d/yunohost_admin.conf' has been manually modified and will not be updated
Success! The configuration has been updated for service 'dnsmasq'
Warning: The configuration file '/etc/fail2ban/jail.conf' has been manually modified and will not be updated
Success! The configuration has been updated for service 'slapd'
Launching migrations..
Warning: Migration 6 sync_admin_and_root_passwords has to be ran manually. Please go to Tools >
Migrations on the webadmin, or run `yunohost tools migrations migrate`.
Restarting YunoHost firewall...
Setting up yunohost-admin (3.3.1) ...
W: APT had planned for dpkg to do more than it reported back (9 vs 13).
Affected packages: mariadb-server-10.1:amd64
Je dois pas être le seul à avoir eu ce soucis, donc je profite pour partager