Impossible mettre a jour yunohost sur raspberry pi

,

**Matériel: Raspberry Pi à la maison
Version de YunoHost: 3.4.2
J’ai accès à mon serveur : En SSH | Par la webadmin | En direct avec un clavier/écran | …
Êtes-vous dans un contexte particulier ou avez-vous effectué des modifications particulières sur votre instance ? : non
bonjour,je viens d’installer yunohost sur mon raspberry pi 3b+,l’installation c bien passée mais il m’est impossible de mettre a jour yunohost.Voici les logs .https://paste.yunohost.org/acezisomal
Merci beaucoup de m’avoir lu.

**Equipment: Raspberry Pi at home.
YunoHost version: 3.4.2
I have access to my server : By SSH | Through the webadmin | Live with a keyboard/screen | …
**Are you in a particular context or have you made particular modifications on your instance : no
Hi, I just installed yunohost on my raspberry pi 3b+, the installation went well but I can’t update yunohost.Here are the logs .https://paste.yunohost.org/acezisomal
Thank you very much for reading me.
the english translation was done with deepl.com

Salut,

est-ce que exceptionellement tu peux tenter la mise à jour en ligne de commande avec :

sudo apt update
sudo apt dist-upgrade

@Aleks je me permets de rebondir sur cette info.
Je fais depuis toujours les mises à jour de mon serveur yunohost via apt (et je n’ai jamais eu de souci majeur jusque là). Mais peut-être n’est pas la pratique recommandée? Vaut-il mieux faire les mises à jour avec la commande yunohost ou via apt?
Quelles sont les différences entre les deux?
Merci d’avance pour tes lumières.

Plutot via yunohost que via apt, même si dans l’absolu avec apt ça marche aussi.

Là où ça peut jouer, c’est que yunohost va lancer la commande apt avec toutes les options qui vont bien pour qu’il n’y ai pas de questions … par exemple des fois apt peut te demander si tu veux la nouvelle ou ancienne version d’un fichier de conf et c’est vite déroutant et on sais pas ce que ça peut avoir comme impact … Si tu passes pas yunohost c’est pas censé arriver car par défaut il y a l’option qui va bien pour répondre ce qu’il faut automatiquement.

coucou,mercide de ta reponse,cela ne marche pas,cela me met
sudo apt dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages were automatically installed and are no longer required:
etckeeper fonts-lyx glances hddtemp iproute javascript-common libblas-common
libblas3 libgfortran3 libjs-angularjs libjs-jquery libjs-jquery-ui
libjs-lodash liblapack3 liblcms2-2 libsensors4 libwebpdemux2 libwebpmux2
lm-sensors python-gnupg python-matplotlib-data python3-bottle python3-crypto
python3-cycler python3-dateutil python3-docker python3-influxdb
python3-matplotlib python3-netifaces python3-numpy python3-pil
python3-psutil python3-pyasn1 python3-pyparsing python3-pysnmp4
python3-pystache python3-tz python3-websocket
Use ‘sudo apt autoremove’ to remove them.
The following NEW packages will be installed:
publicsuffix python-packaging python-publicsuffix python-pyparsing
python-toml
The following packages will be upgraded:
apt-transport-https dns-root-data libasound2 libasound2-data
libdns-export162 libglib2.0-data libisc-export160 libjs-jquery
libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0
libsasl2-modules metronome moulinette php7.0-cli php7.0-common php7.0-curl
php7.0-fpm php7.0-gd php7.0-intl php7.0-json php7.0-ldap php7.0-mbstring
php7.0-mcrypt php7.0-mysql php7.0-opcache php7.0-readline php7.0-xml postfix
postfix-ldap postfix-pcre postfix-sqlite python-cryptography python-six
python3-pil python3-six raspberrypi-bootloader raspberrypi-kernel
raspi-config raspi-copies-and-fills redis-server redis-tools ssowat
sudo-ldap unzip usbutils vim-common vim-tiny wireless-regdb wpasupplicant
xxd yunohost yunohost-admin
54 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
13 not fully installed or removed.
Need to get 0 B/97.5 MB of archives.
After this operation, 10.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs… Done
Extracting templates from packages: 100%
Preconfiguring packages …
Setting up mariadb-server-10.1 (10.1.44-0+deb9u1) …
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.44-0+deb9u1); however:
Package mariadb-server-10.1 is not configured yet.

dpkg: error processing package mariadb-server (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mariadb-server-10.1
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Erf …

alors est-ce qu’on peut faire un :

journalctl --no-pager --no-hostname -n 50 -u mariadb

Bonjour @Aleks,merci bcp de ton aide.Cela me retourne
journalctl --no-pager --no-hostname -n 50 -u mariadb
– Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Tue 2020-07-07 09:44:05 BST. –
Jul 03 21:17:09 systemd[1]: Starting MariaDB 10.1.37 database server…
Jul 03 21:17:17 mysqld[890]: 2020-07-03 21:17:17 1989078832 [Note] /usr/sbin/mysqld (mysqld 10.1.37-MariaDB-0+deb9u1) starting as process 890 …
Jul 03 21:17:36 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 21:17:36 systemd[1]: Failed to start MariaDB 10.1.37 database server.
Jul 03 21:17:36 systemd[1]: mariadb.service: Unit entered failed state.
Jul 03 21:17:36 systemd[1]: mariadb.service: Failed with result ‘exit-code’.
Jul 06 09:59:45 systemd[1]: Starting MariaDB 10.1.37 database server…
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Warning] option ‘table_open_cache’: unsigned value 4 adjusted to 10
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] /usr/sbin/mysqld (mysqld 10.1.37-MariaDB-0+deb9u1) starting as process 4894 …
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: The InnoDB memory heap is disabled
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Compressed tables use zlib 1.2.8
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Using Linux native AIO
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Using generic crc32 instructions
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Completed initialization of buffer pool
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Highest supported file format is Barracuda.
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: 128 rollback segment(s) are active.
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Waiting for purge to start
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 1616737
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1421865792 [Note] InnoDB: Dumping buffer pool(s) not yet started
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] Plugin ‘FEEDBACK’ is disabled.
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [Note] Recovering after a crash using tc.log
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [ERROR] Can’t init tc log
Jul 06 09:59:47 mysqld[4894]: 2020-07-06 9:59:47 1988276016 [ERROR] Aborting
Jul 06 09:59:50 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 06 09:59:50 systemd[1]: Failed to start MariaDB 10.1.37 database server.
Jul 06 09:59:50 systemd[1]: mariadb.service: Unit entered failed state.
Jul 06 09:59:50 systemd[1]: mariadb.service: Failed with result ‘exit-code’.

Hmpf c’est un probleme stupide de mysql/mariadb …

Normalement tu peux faire un

rm /var/lib/mysql/tc.log

puis redemarrer le service avec

systemctl restart mariadb

puis la mise à jour devrait fonctionner …

merci,ca marche.Une derniere question : comment installer ynh-dev ?

Uuuh, ben c’est expliqué ici et ici mais pas sur de comprendre le rapport o.O

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