Pb Install Yunohost package metronome

Dear all,

I am currently struggling installing Yunohost packages for the first time on a Raspberry Pi 2.

I have done so far the following:

https://yunohost.org/#/copy_image_fr

(2015-11-21-raspbian-jessie)

Then

https://yunohost.org/#/install_manually_fr

It crashed a first time, so as indicated I started over and first ran

sudo apt-get autoremove apache2.2

I was finally welcomed with:

The following error was caught during YunoHost installation :
Installation of Yunohost packages failed
Installation logs are located in /var/log/yunohost-installation.log

yunohost-installation.log gives me the following:

Errors were encountered while processing:
metronome
yunohost-config-metronome
yunohost-config
yunohost
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any help regarding the above would be extremely appreciated :slight_smile:

I’ve just faced the same problem, using the official Raspian image from the Pi foundation (“2016-02-09 full desktop image”). Using the yunohost installation script fails with the installation of metronome.

Here is the output in yunohost-installation.log:

Paramétrage de metronome (3.6-6) ...
Ajout de l'utilisateur metronome au groupe ssl-cert
Job for metronome.service failed. See 'systemctl status metronome.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript metronome, action "start" failed.
dpkg: erreur de traitement du paquet metronome (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

and here is the output of systemctl:

$ sudo systemctl status metronome.service
● metronome.service - LSB: Metronome XMPP Server
Loaded: loaded (/etc/init.d/metronome)
Active: failed (Result: exit-code) since mer. 2016-02-17 20:34:21 UTC; 1min 34s ago
Process: 1918 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)
févr. 17 20:34:21 raspberrypi metronome[1918]: Starting Metronome XMPP Server: metronomeIllegal instruction
févr. 17 20:34:21 raspberrypi metronome[1918]: failed!
févr. 17 20:34:21 raspberrypi systemd[1]: metronome.service: control process exited, code=exited status=1
févr. 17 20:34:21 raspberrypi systemd[1]: Failed to start LSB: Metronome XMPP Server.
févr. 17 20:34:21 raspberrypi systemd[1]: Unit metronome.service entered failed state.

it’s not clear from that what is the problem with metronome installation.

there is a bugreport on Metronome repository, but it has been closed because the developper blames the version packaged by yunohost (https://github.com/maranda/metronome/issues/229)

Maybe version 3.6 should be updated to 3.7.9, according to the changelogs

All previous releases before 3.7 aren’t shown, a lot of bugs have been
fixed from then and perhaps I strongly discourage using anything beyond
the latest minor release 3.7.9 which is very stable.

This seems to be halting all Yunohost installs on RPi:s/ARM devices currently. Very sad.

I’m experiencing the exact same problem here … Please correct this or update the website to advice the user before they try to install it on a raspberry !
Thanks

Hi @Kwignaman @pierreh @yusf @procraste ,

The installation seems to be OK on Raspi 2 & Raspi 3.
The metronome problem persist on Raspi 1 et 1B+.
I’ve made an experimental tutorial here : http://avignu.wiki.tuxfamily.org/doku.php?id=documentation:yunohost-jessie from Installation de Yunohost 2.4 sur raspbian jessie minimal sur un Raspberry Pi 3.

And @heyyounow have made an image for Raspi here : https://mega.nz/#!ik1lgbDJ!tR21crUmfDvIP5J3Y5eyZFd9eCovfCQhp-NsfW42r0A from New updated Raspberry Pi image / Nouvelle image Raspberry Pi.

Hope it could helps you and sorry for my froggy english :stuck_out_tongue_winking_eye:

ppr

2 Likes

je reprends ce post car ce sont les problèmes actuels présents sur une fresh install de yunohost 3.1 image de RaspberryPi.
J’ai upgrader mon serveur en 3.2 .
je sèche …

Bonsoir,

Je déterre le topic, mais j’ai un souci avec la MAJ de metronome sur mon Raspberry Pi 1B et 3B.

J’ai voulu via le panel web de YunoHost faire la MAJ, y compris celle mineure de YunoHost 3.8.x.x sur mon Raspberry Pi 3B, malheureusement, ça a planté et je me suis retrouvé avec un erreur 500 et avec seulement un accès SSH.
J’ai donc rebooté la framboise et les services sont revenus … mais les MAJ de metronome et yunohost toujours présentes et toujours à faire.
Détail : je NAT tous les ports que j’utilise sur ma box … et je ne NAT pas ceux d’XMPP que je n’utilise pas.

Du coup je me suis connecté à mon Raspberry Pi 1B qui sert pour le CI Package Check et dont seul le port SSH est NATé.
Même problème : impossible de mettre à jour metronome qui du coup empêche la MAJ de YunoHost et potentiellement d’autres paquets.

Voilà ce que ça raconte dans le Terminal :

Résumé Raspberry Pi 1

root@raspberrypi:~# apt update && apt dist-upgrade && apt autoremove && apt autoclean
Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:2 http://forge.yunohost.org/debian stretch InRelease
Get:3 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Fetched 40.3 kB in 5s (7,504 B/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
1 package can be upgraded. Run ‘apt list --upgradable’ to see it.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages will be upgraded:
yunohost
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/824 kB of archives.
After this operation, 44.0 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs… Done
Setting up metronome (3.14.1+ynh9-1) …
Job for metronome.service failed because the control process exited with error code.
See “systemctl status metronome.service” and “journalctl -xe” for details.
invoke-rc.d: initscript metronome, action “start” failed.
● metronome.service - LSB: Metronome XMPP Server
Loaded: loaded (/etc/init.d/metronome; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-05-28 18:12:16 CEST; 223ms ago
Docs: man:systemd-sysv-generator(8)
Process: 10390 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)
CPU: 316ms

May 28 18:12:15 raspberrypi systemd[1]: Starting LSB: Metronome XMPP Server…
May 28 18:12:16 raspberrypi metronome[10390]: Starting Metronome XMPP Server: metronomeIllegal instruction
May 28 18:12:16 raspberrypi metronome[10390]: failed!
May 28 18:12:16 raspberrypi systemd[1]: metronome.service: Control process exited, code=exited status=1
May 28 18:12:16 raspberrypi systemd[1]: Failed to start LSB: Metronome XMPP Server.
May 28 18:12:16 raspberrypi systemd[1]: metronome.service: Unit entered failed state.
May 28 18:12:16 raspberrypi systemd[1]: metronome.service: Failed with result ‘exit-code’.
dpkg: error processing package metronome (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
metronome
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@raspberrypi:~#

Si vous avez une idée de ce qui peut faire boguer le truc ou une solution je suis preneur :wink:

Edit :
J’ai essayé dpkg --configure

Résumé dpkg --configure -a

root@raspberrypi:~# dpkg --configure -a
Setting up metronome (3.14.1+ynh9-1) …
Job for metronome.service failed because the control process exited with error code.
See “systemctl status metronome.service” and “journalctl -xe” for details.
invoke-rc.d: initscript metronome, action “start” failed.
● metronome.service - LSB: Metronome XMPP Server
Loaded: loaded (/etc/init.d/metronome; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-05-28 18:14:19 CEST; 189ms ago
Docs: man:systemd-sysv-generator(8)
Process: 10861 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)
CPU: 307ms

May 28 18:14:18 raspberrypi systemd[1]: Starting LSB: Metronome XMPP Server…
May 28 18:14:19 raspberrypi metronome[10861]: Starting Metronome XMPP Server: metronomeIllegal instruction
May 28 18:14:19 raspberrypi metronome[10861]: failed!
May 28 18:14:19 raspberrypi systemd[1]: metronome.service: Control process exited, code=exited status=1
May 28 18:14:19 raspberrypi systemd[1]: Failed to start LSB: Metronome XMPP Server.
May 28 18:14:19 raspberrypi systemd[1]: metronome.service: Unit entered failed state.
May 28 18:14:19 raspberrypi systemd[1]: metronome.service: Failed with result ‘exit-code’.
dpkg: error processing package metronome (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
metronome
root@raspberrypi:~#

J’ai aussi essayé pour mettre à jour puis configurer metronome de le passer en apt hold et d’arrêter le service mais sans succès.

J’ai également essayé de apt remove metronome mais je me suis arrêté car sinon j’avais tous les paquets YunoHost qui allait être remove aussi.

Résumé apt remove metronome

root@raspberrypi:~# apt remove metronome
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
bind9utils dnsmasq dnsutils dovecot-antispam galera-3 ldap-utils libaio1 libconfig-inifiles-perl libhiredis0.13 libjemalloc1 liblua5.1-0
libluajit-5.1-2 libmail-spf-perl libmemcached11 libmemcachedutil2 libnet-dns-perl libnet-ip-perl libnetaddr-ip-perl libnginx-mod-http-auth-pam
libnginx-mod-http-cache-purge libnginx-mod-http-dav-ext libnginx-mod-http-echo libnginx-mod-http-fancyindex libnginx-mod-http-geoip
libnginx-mod-http-headers-more-filter libnginx-mod-http-image-filter libnginx-mod-http-lua libnginx-mod-http-ndk libnginx-mod-http-perl
libnginx-mod-http-subs-filter libnginx-mod-http-uploadprogress libnginx-mod-http-upstream-fair libnginx-mod-http-xslt-filter libnginx-mod-mail
libnginx-mod-nchan libnginx-mod-stream libnss-ldapd libnss-myhostname libodbc1 libopendbx1 libopendkim11 libpam-ldapd librbl1 libunbound2
libunwind8 libvbr2 libyaml-0-2 lua-event lua-expat lua-filesystem lua-json lua-ldap lua-lpeg lua-rex-pcre lua-sec lua-socket mariadb-client-10.1
mariadb-client-core-10.1 mariadb-common mariadb-server mariadb-server-10.1 mariadb-server-core-10.1 moulinette nginx-common nginx-extras nslcd
opendkim-tools php-fpm php-intl php-ldap php-mysql php7.0-fpm php7.0-intl php7.0-ldap php7.0-mysql postfix-policyd-spf-perl postsrsd
python-argcomplete python-bottle python-chardet python-dnspython python-gevent python-gevent-websocket python-greenlet python-jinja2 python-ldap
python-markupsafe python-miniupnpc python-openssl python-packaging python-psutil python-pyparsing python-requests python-toml python-tz
python-urllib3 python-yaml redis-server redis-tools rspamd slapd socat ssowat sudo-ldap unscd
Use ‘apt autoremove’ to remove them.
The following packages will be REMOVED:
metronome yunohost
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
yunohost metronome (due to yunohost)
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 5,094 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase ‘Yes, do as I say!’
?] n
Abort.
You have new mail in /var/mail/root
root@raspberrypi:~#

ppr

Uh pas compris pourquoi tu passes du 3 au 1 …

Sur le 1 il y a ce soucis connu qui explique vaguement le pourquoi du Illegal instruction et un hack pas beau pour contourner le soucis … https://github.com/YunoHost/issues/issues/1423#issuecomment-536207506

Par contre sur RPi3 ça devrait marcher (ça tourne sur mon Rpi2) donc je demande à voir les logs sur RPi3 … Tu peux faire un journalctl -u metronome --no-pager --no-hostname -n 100

1 Like

Merci Aleks :slight_smile:

Je ne sais pas ce qui s’était passé avec le Raspberry Pi 3B mais les MAJ sont passées (metronome et yunohost).
Je vois demain pour passer la commande du journalctl.

Edit :

Résumé journalctl

root@:~# journalctl -u metronome --no-pager --no-hostname -n 100
– Logs begin at Thu 2016-11-03 18:16:43 CET, end at Thu 2020-05-28 23:09:02 CEST. –
May 27 20:17:15 systemd[1]: Starting LSB: Metronome XMPP Server…
May 27 20:17:19 metronome[525]: Starting Metronome XMPP Server: metronome.
May 27 20:17:19 systemd[1]: Started LSB: Metronome XMPP Server.
May 28 06:25:02 systemd[1]: Reloading LSB: Metronome XMPP Server.
May 28 06:25:02 metronome[12982]: Reloading Metronome XMPP Server: metronome.
May 28 06:25:02 systemd[1]: Reloaded LSB: Metronome XMPP Server.
May 28 20:40:01 systemd[1]: Stopping LSB: Metronome XMPP Server…
May 28 20:40:02 metronome[1606]: Stopping Metronome XMPP Server: metronome.
May 28 20:40:02 systemd[1]: Stopped LSB: Metronome XMPP Server.
May 28 20:40:10 systemd[1]: Starting LSB: Metronome XMPP Server…
May 28 20:40:11 metronome[1715]: Starting Metronome XMPP Server: metronome.
May 28 20:40:11 systemd[1]: Started LSB: Metronome XMPP Server.
May 28 20:42:48 systemd[1]: Stopping LSB: Metronome XMPP Server…
May 28 20:42:48 metronome[2482]: Stopping Metronome XMPP Server: metronome.
May 28 20:42:48 systemd[1]: Stopped LSB: Metronome XMPP Server.
May 28 20:42:48 systemd[1]: Starting LSB: Metronome XMPP Server…
May 28 20:42:48 metronome[2489]: Starting Metronome XMPP Server: metronome.
May 28 20:42:48 systemd[1]: Started LSB: Metronome XMPP Server.
root@
:~#

Je ne sais pas si ça a un rapport mais lorsque la MAJ a planté s’était avec la version mineure précédente de la 3.8.

Pour le Raspberry Pi 1B je verrais pour utiliser le dirty hack demain également.

ppr

Marf ben du coup le soucis n’a pas vraiment l’air lié a metronome pour le RPi3 …

Sinon tu peux aussi aller cherche le log de l’upgrade qui a échoué dans Outils > Log

Bonsoir,

Le dirty hack a fonctionné :slight_smile:

Résumé

root@raspberrypi:~# mv /usr/bin/metronome /usr/bin/metronome.bak
root@raspberrypi:~# mv /usr/bin/metronomectl /usr/bin/metronomectl.bak
root@raspberrypi:~# ln -s /usr/bin/true /usr/bin/metronome
root@raspberrypi:~# ln -s /usr/bin/true /usr/bin/metronomectl
root@raspberrypi:~# dpkg --configure -a
Setting up metronome (3.14.1+ynh9-1) …
You have new mail in /var/mail/root
root@raspberrypi:~# apt update && apt dist-upgrade && apt autoremove && apt autoclean
Hit:1 http://forge.yunohost.org/debian stretch InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Get:3 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Fetched 40.3 kB in 5s (7,358 B/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
1 package can be upgraded. Run ‘apt list --upgradable’ to see it.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages will be upgraded:
yunohost
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/824 kB of archives.
After this operation, 44.0 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs… Done
(Reading database … 49560 files and directories currently installed.)
Preparing to unpack …/yunohost_3.8.4.6_all.deb …
Unpacking yunohost (3.8.4.6) over (3.8.4.4) …
Setting up yunohost (3.8.4.6) …
Initializing a local SSL certification authority …
(logs available in /tmp/yunohost-ssl-init)
usermod: nscd did not terminate normally (signal 11)
usermod: nscd did not terminate normally (signal 11)
config file testing succeeded
Warning: slapd.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
Processing triggers for systemd (232-25+deb9u12) …
Processing triggers for man-db (2.7.6.1-2) …
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Del yunohost 3.8.4.5 [822 kB]
Del metronome 3.14.0+ynh9-1 [394 kB]
Del yunohost-admin 3.8.3.2 [8,586 kB]
Del yunohost 3.8.4.4 [821 kB]
root@raspberrypi:~# systemctl daemon-reload
root@raspberrypi:~#

Merci,
ppr

Mais le dirty hack c’était pour Rpi 0 et 1 …

Comme dit, est-ce que tu peux retrouver le log de la mise à jour échouée dans Outils > Log sur le RPi3

Oui-oui, je l’ai bien utilisé sur le Raspberry 1B.
Je suis en train d’essayer de retrouver le log d’il y a 3-4 jours de l’install.

ppr

C’est chelou …

nano /var/log/yunohost/categories/operation/20200526-174927-tools_upgrade.log
2020-05-26 19:49:27,304: INFO - Mise à jour des paquets du système (non liés a YunoHost)… ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$

ppr

Il y a aussi un fichier yml :

/var/log/yunohost/categories/operation# cat 20200526-174927-tools_upgrade.yml
args:
apps: null
system: true
operation: tools_upgrade
related_to: []
started_at: 2020-05-26 17:49:27.291663
root@***:/var/log/yunohost/categories/operation#

ppr

Depuis le panel j’avais cliqué sur YunoPaste :

Le journal est désormais disponible via https://paste.yunohost.org/raw/capukipove

ppr

Mokay bon c’est chelou, on dirait qu’il s’est passé un truc particulier juste après le lancement de la maj, genre process qui se fait tuer ou machine qui s’éteint …

Si tu relances un yunohost tools upgrade --system, ça fait pareil ou bien ?

Comme tu m’as dit que théoriquement ça devait passer sur Raspberry 3B, du coup j’ai envoyé les commandes suivantes et c’est effectivement passé, la mise à jour a pu se faire :

apt update && apt dist-upgrade && apt autoremove && apt autoclean && yunohost tools update
yunohost tools upgrade --system

ppr