Hardware: VPS bought online & Intel NUC YunoHost version: 11.2.3 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 ? : no
Description of my issue
Trying to get the update on my two yunohost instance (1 on a VPS, one on a comuter at home) result in error :
getting on SSH and tryed sudo apt install --fix-broken, sudo dpkg --configure -a but metronome is failing to start in the two cases.
I don’t use XMPP at all on those instance and I don’t have change configuration files.
As I do have the error in two separated instance, I think that this does not come from my configuration. (I tend to minimize any modification of conf file to be foward compatible)
sudo apt install --fix-broken
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages were automatically installed and are no longer required:
expat lua5.1 php7.3-mysql php7.3-sqlite3 php8.0 php8.0-curl php8.0-fpm php8.0-intl php8.0-mysql
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 68 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up metronome (4.0.3.1+ynh11) …
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 “restart” failed.
● metronome.service - LSB: Metronome XMPP Server
Loaded: loaded (/etc/init.d/metronome; generated)
Active: failed (Result: exit-code) since Wed 2023-08-16 10:15:44 CEST; 6ms ago
Docs: man:systemd-sysv-generator(8)
Process: 2419977 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)
CPU: 20ms
Aug 16 10:15:44 mydomain.fr systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 10:15:44 mydomain.fr metronome[2419977]: Starting Metronome XMPP Server: metronome
Aug 16 10:15:44 mydomain.fr metronome[2419993]: failed!
Aug 16 10:15:44 mydomain.fr systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 10:15:44 mydomain.fr systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 10:15:44 mydomain.fr systemd[1]: Failed to start LSB: Metronome XMPP Server.
sudo dpkg --configure -a
Setting up metronome (4.0.3.1+ynh11) …
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 “restart” failed.
● metronome.service - LSB: Metronome XMPP Server
Loaded: loaded (/etc/init.d/metronome; generated)
Active: failed (Result: exit-code) since Wed 2023-08-16 10:16:04 CEST; 20ms ago
Docs: man:systemd-sysv-generator(8)
Process: 2420126 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)
CPU: 17ms
sudo dpkg --configure -a
Setting up metronome (4.0.3.1+ynh11) …
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 “restart” failed.
● metronome.service - LSB: Metronome XMPP Server
Loaded: loaded (/etc/init.d/metronome; generated)
Active: failed (Result: exit-code) since Wed 2023-08-16 10:16:04 CEST; 20ms ago
Docs: man:systemd-sysv-generator(8)
Process: 2420126 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)
CPU: 17ms
Aug 16 10:16:04 mydomain.fr systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 10:16:04 mydomain.fr metronome[2420126]: Starting Metronome XMPP Server: metronome
Aug 16 10:16:04 mydomain.fr metronome[2420135]: failed!
Aug 16 10:16:04 mydomain.fr systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 10:16:04 mydomain.fr systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 10:16:04 mydomain.fr systemd[1]: Failed to start LSB: Metronome XMPP Server.
dpkg: error processing package metronome (–configure):
installed metronome package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
metronome
sudo dpkg --audit
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure or the configure menu option in dselect:
metronome Lightweight XMPP server with advanced microblogging featu
Hmmmokay unfortunately we’ll have to dig deeper because this doesnt contain any actual error … Let’s try journalctl -u metronome -n 20 --no-pager --no-hostname
And maybe we can also try to run metronome directly (or is it metronomectl ?)
admin@mydomain:~$ journalctl -u metronome -n 20 --no-pager --no-hostname
Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’ can see all messages.
Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions. admin@mydomain:~$ sudo !!
sudo journalctl -u metronome -n 20 --no-pager --no-hostname
– Journal begins at Wed 2023-05-10 13:33:51 CEST, ends at Wed 2023-08-16 14:41:16 CEST. –
Aug 16 10:15:44 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 10:15:44 systemd[1]: Failed to start LSB: Metronome XMPP Server.
Aug 16 10:16:04 systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 10:16:04 metronome[2420126]: Starting Metronome XMPP Server: metronome
Aug 16 10:16:04 metronome[2420135]: failed!
Aug 16 10:16:04 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 10:16:04 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 10:16:04 systemd[1]: Failed to start LSB: Metronome XMPP Server.
Aug 16 10:50:32 systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 10:50:32 metronome[2423666]: Starting Metronome XMPP Server: metronome
Aug 16 10:50:32 metronome[2423675]: failed!
Aug 16 10:50:32 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 10:50:32 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 10:50:32 systemd[1]: Failed to start LSB: Metronome XMPP Server.
– Boot e6244e6db90e4aa1ac0cd686c61aa745 –
Aug 16 11:07:32 systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 11:07:32 metronome[1811]: Starting Metronome XMPP Server: metronome
Aug 16 11:07:32 metronome[1821]: failed!
Aug 16 11:07:32 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 11:07:32 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 11:07:32 systemd[1]: Failed to start LSB: Metronome XMPP Server.
And after that same result as above when trying dpkg --configure metronome
I do remember that i deactivated XMPP in the domain part of the webadmin (so that there is probably no DNS and no letencrypt associated to it
admin@mydomain:~$ sudo metronomectl start --debug
Still waiting…
Metronome is still not running. Please give it some time or check your log files for errors. admin@mydomain:~$ sudo journalctl -u metronome -n 20 --no-pager --no-hostname
– Journal begins at Wed 2023-05-10 13:33:51 CEST, ends at Wed 2023-08-16 14:49:46 CEST. –
Aug 16 10:50:32 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 10:50:32 systemd[1]: Failed to start LSB: Metronome XMPP Server.
– Boot e6244e6db90e4aa1ac0cd686c61aa745 –
Aug 16 11:07:32 systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 11:07:32 metronome[1811]: Starting Metronome XMPP Server: metronome
Aug 16 11:07:32 metronome[1821]: failed!
Aug 16 11:07:32 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 11:07:32 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 11:07:32 systemd[1]: Failed to start LSB: Metronome XMPP Server.
Aug 16 14:43:12 systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 14:43:12 metronome[7830]: Starting Metronome XMPP Server: metronome
Aug 16 14:43:12 metronome[7840]: failed!
Aug 16 14:43:12 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 14:43:12 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 14:43:12 systemd[1]: Failed to start LSB: Metronome XMPP Server.
Aug 16 14:47:07 systemd[1]: Starting LSB: Metronome XMPP Server…
Aug 16 14:47:07 metronome[8761]: Starting Metronome XMPP Server: metronome
Aug 16 14:47:07 metronome[8770]: failed!
Aug 16 14:47:07 systemd[1]: metronome.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 14:47:07 systemd[1]: metronome.service: Failed with result ‘exit-code’.
Aug 16 14:47:07 systemd[1]: Failed to start LSB: Metronome XMPP Server.
I’ve tryied reactivating the XMPP in domain, regenerating the letencrypt certificate, restarting the server, but same effect.
tail /var/log/metronome/metronome.err
Aug 16 15:04:44 general error No enabled VirtualHost entries found in the config file.
Aug 16 15:04:44 general error At least one active host is required for Metronome to function. Exiting…
Aug 16 15:06:01 general error No enabled VirtualHost entries found in the config file.
Aug 16 15:06:01 general error At least one active host is required for Metronome to function. Exiting…
Aug 16 15:10:10 general error No enabled VirtualHost entries found in the config file.
Aug 16 15:10:10 general error At least one active host is required for Metronome to function. Exiting…
Aug 16 15:10:16 general error No enabled VirtualHost entries found in the config file.
Aug 16 15:10:16 general error At least one active host is required for Metronome to function. Exiting…
Aug 16 15:47:58 general error No enabled VirtualHost entries found in the config file.
Aug 16 15:47:58 general error At least one active host is required for Metronome to function. Exiting…
Sorry, i have the same mistake on my yunohost system. During upgrading the system i got the same error message in english: Then i did the sudo apt install etc. and teh errors come from the metronome! Today i do not get into my nextcloud via firefox, google, etc because there is now an security problem :Websites bestätigen ihre Identität mittels Zertifikaten, welche für einen bestimmten Zeitraum gültig sind. Das Zertifikat für learn4joy.de ist am 22.8.2023 abgelaufen.
Fehlercode: SEC_ERROR_EXPIRED_CERTIFICATE
so i cant use yunohost with nextcloud anymore. sorry.
Welcher Weg ist zur Deinstallation der sicherste Weg?
Ich hatte schon einmal ein ähnliches Problem, und nach der Deinstallation war das System beschädigt.