Paquet Yunohost non completement configuré suite à la dernière mise à jour

Bonsoir,
Je pense que la denière màj s’est mal passée sur mon rpi3, j’ai le paquet yunohost qui n’est pas totalement configuré.

Les manips que j’ai tenté pour le ramener à la vie:

sudo apt -f install
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up yunohost (3.6.5.2) …
Regenerating configuration, this might take a while…
Success! The configuration has been updated for category ‘dnsmasq’
Warning: Failed to retrieve unit: Connection timed out
Warning: Failed to restart dnsmasq.service: Connection timed out
Warning: See system logs and ‘systemctl status dnsmasq.service’ for details.
Error: Script execution failed: /usr/share/yunohost/hooks/conf_regen/43-dnsmasq
Launching migrations…
Info: No migrations to run
Failed to retrieve unit: Connection timed out
Failed to get properties: Failed to activate service ‘org.freedesktop.systemd1’: timed out
yunohost-firewall service is not running, you should consider to start it by doing ‘service yunohost-firewall start’.
Failed to enable unit: Connection timed out
dpkg: error processing package yunohost (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
yunohost
E: Sub-process /usr/bin/dpkg returned an error code (1)

puis

systemctl status dnsmasq.service
Failed to get properties: Failed to activate service ‘org.freedesktop.systemd1’: timed out

et pour finir:

systemctl start org.freedesktop.systemd1
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Could not watch jobs: Connection timed out

Si quelqu’un pouvait me filer à coup de main avant que je le casse encore plus…
Merci d’avance.

Sans oublier

sudo yunohost tools diagnosis
Traceback (most recent call last):
File “/usr/bin/yunohost”, line 214, in
timeout=opts.timeout,
File “/usr/lib/python2.7/dist-packages/moulinette/init.py”, line 136, in cli
moulinette.run(args, output_as=output_as, password=password, timeout=timeout)
File “/usr/lib/python2.7/dist-packages/moulinette/interfaces/cli.py”, line 425, in run
ret = self.actionsmap.process(args, timeout=timeout)
File “/usr/lib/python2.7/dist-packages/moulinette/actionsmap.py”, line 523, in process
return func(**arguments)
File “/usr/lib/moulinette/yunohost/tools.py”, line 802, in tools_diagnosis
services = service_status()
File “/usr/lib/moulinette/yunohost/service.py”, line 287, in service_status
status = _get_service_information_from_systemd(name)
File “/usr/lib/moulinette/yunohost/service.py”, line 348, in _get_service_information_from_systemd
systemd = d.get_object(‘org.freedesktop.systemd1’, ‘/org/freedesktop/systemd1’)
File “/usr/lib/python2.7/dist-packages/dbus/bus.py”, line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File “/usr/lib/python2.7/dist-packages/dbus/proxies.py”, line 248, in init
self._named_service = conn.activate_name_owner(bus_name)
File “/usr/lib/python2.7/dist-packages/dbus/bus.py”, line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File “/usr/lib/python2.7/dist-packages/dbus/bus.py”, line 278, in start_service_by_name
‘su’, (bus_name, flags)))
File “/usr/lib/python2.7/dist-packages/dbus/connection.py”, line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service ‘org.freedesktop.systemd1’: timed out

Hmokay on dirait que systemd est bien dans les choux … Est-ce qu’éventuellement tu pourrais tenter un reboot ?

C’est ce que je viens de me résoudre à faire il y a 10 min:

sudo reboot
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

J’ai ensuite tenté

sudo shutdown -r now
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

Puis

sudo reboot -f
Failed to read reboot parameter file: No such file or directory
Rebooting.
packet_write_wait: Connection to 192.168.x.xxx port 22: Broken pipe

J’ai attendu un peu, j’ai pu me reconnecter via ssh, et lancer un Yunohost tools upgrade qu’il semble avoir réussi a executé correctement.

Par contre j’ai un message dans la console d’admin:
Impossible de récupérer le flux : https://yunohost.org/security.rss. Il se peut qu’une extension empêche votre navigateur d’exécuter cette requête (ou que le site web soit hors service).
Je devrais vérifier autre chose?

C’est beaucoup moins important que systemd dans les choux :stuck_out_tongue_winking_eye: Mais du coup comme le message le suggère, tu as peut-être un plugin de navigateur qui bloque la requête vers “l’extérieur” du site

En effet Privacy Badger me bloquait Yunohost.org
Merci, sujet clos!

1 Like

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