Dnsmasq ne fonctionne plus suite à une tentative de mise à jour yunohost

Mon serveur YunoHost

Matériel: Brique internet Olimex
Version de YunoHost: 4.4.2
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : oui
Si oui, expliquer: tentative de mise à jour de Yunohost

Description du problème

Depuis la tentative de mise à jour je n’ai plus de connexion internet, le service “dnsmasq” ne fonctionne plus :

Erreur: "500" Internal Server Error

Action: "PUT" /yunohost/api/services/dnsmasq/start

Message d’erreur :

Impossible de démarrer le service ‘dnsmasq’
Journaux historisés récents : e[0;1;38;5;185mJournal file /var/log/journal/37960f62790a4cceb15bd21e91795cb5/user-9170@0005e5f75a3e7a12-5909f3ae36dcf7d7.journal~ is truncated, ignoring file.e[0m – Journal begins at Thu 2022-08-11 00:47:49 CEST, ends at Fri 2022-08-12 07:07:35 CEST. – Aug 11 01:13:32 dnsmasq[644]: reading /etc/resolv.dnsmasq.conf Aug 11 01:13:32 dnsmasq[644]: using nameserver 2001:910:800::40#53 Aug 11 01:13:32 dnsmasq[644]: using nameserver 80.67.169.12#53 Aug 11 01:37:20 systemd[1]: Stopping dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 01:37:21 dnsmasq[16544]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Aug 11 01:37:21 dnsmasq[644]: exiting on receipt of SIGTERM Aug 11 01:37:21 systemd[1]: dnsmasq.service: Succeeded. Aug 11 01:37:21 systemd[1]: Stopped dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 01:37:21 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 01:37:21 dnsmasq[16557]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 01:37:21 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 01:37:21 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 01:37:21 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. – Boot 70dbe664f8554980bb3a91aca9846869 – Aug 11 07:12:55 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 07:12:57 dnsmasq[508]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 07:12:57 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 07:12:57 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 07:12:57 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 07:22:30 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 07:22:30 dnsmasq[2842]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 07:22:30 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 07:22:30 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 07:22:30 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 07:27:27 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 07:27:28 dnsmasq[3415]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 07:27:28 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 07:27:28 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 07:27:28 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 07:27:53 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 07:27:53 dnsmasq[3480]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 07:27:54 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 07:27:54 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 07:27:54 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. – Boot efc0a3e529ca4f3bb62ba8dc365db8ec – Aug 11 07:30:01 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 07:30:03 dnsmasq[507]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 07:30:03 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 07:30:03 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 07:30:03 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 08:08:23 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 08:08:23 dnsmasq[5640]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 08:08:23 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 08:08:23 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 08:08:23 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 08:14:28 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 08:14:28 dnsmasq[6897]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 08:14:28 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 08:14:28 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 08:14:29 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 08:23:29 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 08:23:29 dnsmasq[8157]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 08:23:29 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 08:23:29 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 08:23:29 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 08:35:52 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 08:35:52 dnsmasq[9481]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 08:35:52 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 08:35:52 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 08:35:52 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 08:39:34 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 08:39:35 dnsmasq[10007]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 08:39:35 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 08:39:35 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 08:39:35 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 10:08:46 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 10:09:26 dnsmasq[20017]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 10:09:26 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 10:09:26 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 10:09:26 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 10:19:09 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 10:19:28 dnsmasq[21053]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 10:19:28 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 10:19:28 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 10:19:28 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. – Boot d78e51c18f284d24843da70ce64495e7 – Aug 11 14:18:04 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 14:18:07 dnsmasq[511]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 14:18:07 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 14:18:07 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 14:18:07 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 11 14:34:18 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 11 14:34:18 dnsmasq[3464]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 11 14:34:18 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 11 14:34:18 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 11 14:34:18 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. – Boot 3b1367d844e742aa8ab8436c8e4b7af3 – Aug 12 06:56:28 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 12 06:56:28 dnsmasq[3615]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 12 06:56:28 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 12 06:56:28 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 12 06:56:28 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 12 06:57:26 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 12 06:57:26 dnsmasq[4084]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 12 06:57:26 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 12 06:57:26 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 12 06:57:26 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 12 07:01:18 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 12 07:01:18 dnsmasq[4471]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 12 07:01:18 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 12 07:01:18 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 12 07:01:18 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 12 07:03:53 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 12 07:03:53 dnsmasq[5123]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 12 07:03:53 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 12 07:03:53 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 12 07:03:53 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Aug 12 07:07:35 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server… Aug 12 07:07:35 dnsmasq[6131]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status} Aug 12 07:07:35 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED Aug 12 07:07:35 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’. Aug 12 07:07:35 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

Pendant le traitement de l’action, le serveur a dit :

Impossible d’exécuter la commande ‘systemctl start dnsmasq’

voici mon fichier /etc/dnsmasq.conf :

domain-needed
expand-hosts
localise-queries

interface=lo

interface=wlan0

interface=eth0

resolv-file=/etc/resolv.dnsmasq.conf
cache-size=256

(j’ai ajouté interface=eth0 manuellement)

Résultats des commandes suivantes :
ls /sys/class/net et ls -m /sys/class/net | sed s/,//g

eth0 lo wlan0

mon /etc/resolv.conf ne contenait que la ligne
nameserver 127.0.0.1

j’ai ajouté une ligne nameserver avec l’adresse d’un serveur dns et la connexion refonctionne. Je teste un upgrade systeme.

J’ai l’erreur suivant pendant l’exécution de la mise à jour :

Erreur: "500" Internal Server Error

Action: "PUT" /yunohost/api/update/all

Message d’erreur :

Erreur serveur inattendue

Retraçage

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/moulinette/interfaces/api.py", line 494, in process
    ret = self.actionsmap.process(arguments, timeout=30, route=_route)
  File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 599, in process
    return func(**arguments)
  File "/usr/lib/moulinette/yunohost/tools.py", line 406, in tools_update
    upgradable_apps = list(_list_upgradable_apps())
  File "/usr/lib/moulinette/yunohost/tools.py", line 419, in _list_upgradable_apps
    app_dict = app_info(app_id, full=True)
  File "/usr/lib/moulinette/yunohost/app.py", line 143, in app_info
    permissions = user_permission_list(full=True, absolute_urls=True, apps=[app])[
  File "/usr/lib/moulinette/yunohost/permission.py", line 80, in user_permission_list
    apps_base_path = {
  File "/usr/lib/moulinette/yunohost/permission.py", line 84, in <dictcomp>
    and app_setting(app, "domain")
  File "/usr/lib/moulinette/yunohost/app.py", line 1199, in app_setting
    app_settings = _get_app_settings(app) or {}
  File "/usr/lib/moulinette/yunohost/app.py", line 1773, in _get_app_settings
    settings = {k: v for k, v in settings.items()}
AttributeError: 'NoneType' object has no attribute 'items'

Pendant le traitement de l’action, le serveur a dit :

Récupération des mises à jour disponibles pour les paquets du système…

Mise à jour du catalogue d’applications…

Le catalogue des applications a été mis à jour !

Si je comprend bien, tu as tenté de mettre à jour mais tu es toujours en 4.4.2 ?

Ça résous pas vraiment le soucis avec dnsmasq.

Que disent les logs de DNSmasq ?

journalctl -u dnsmasq -n50

Pour le 2nd soucis, est-ce que tu peux lancer un yunohost app info APP sur chaque app que tu as installé ?

Oui je suis toujours en 4.4.2, quand via l’interface d’admin je tente un “mettre à jour le système”, ça mouline et j’ai une erreur 500 (voir ci-dessus) puis ça me dirige vers la page d’accueil.

Là je suis connecté en ssh et j’ai lancé un

apt update && apt upgrade 

(pas sur que ce soit une bonne idée mais bon …)

puis j’ai lancé :

yunohost tools regen-conf dnsmasq -f
yunohost tools update
yunohost tools upgrade system
yunohost tools upgrade apps

Tout ça s’est bien passé.

un bref résultat de la commande :

journalctl -u dnsmasq -n50
août 16 08:46:28 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
août 16 08:46:28 dnsmasq[10127]: Usage: /etc/init.d/dnsmasq {start|stop|restart|force-reload|dump-stats|status}
août 16 08:46:28 [1]: dnsmasq.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
août 16 08:46:28 [1]: dnsmasq.service: Failed with result 'exit-code'.
août 16 08:46:28 [1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

j’ai relancé un diagnostic :

La résolution DNS semble fonctionner, mais il semble que vous utilisez un /etc/resolv.conf personnalisé.
Le service dnsmasq est failed :frowning:
Le service php7.0-fpm est dead :frowning:

J’arrive à présent à cliquer sur “mettre à jour le système” il me signale que la migration n’est pas terminée, quand je clique sur le lien j’ai :

Migrations en attente

  1. Réparer l’application Python après la migration Bullseye

  2. Migration des bases de données de PostgreSQL 11 vers 13

  3. Migration des fichiers de configuration php7.3-fpm ‘pool’ vers php7.4

  4. Mise à niveau du système vers Debian Bullseye et YunoHost 11.x

Quand je clique sur “Executer” ça se lance et ça se referme aussitôt.


Erreur : Failed to read info for vpnclient : 'NoneType' object has no attribute 'items'
apps: 
  0: 
    description: Agrégateur de flux RSS avec une interface adaptée au mobile
    id: freshrss
    name: FreshRSS
    version: 1.19.2~ynh1
  1: 
    description: Créer et configurer des réseaux wifi, partager l'accès a Internet et utiliser les applications Yunohost via wifi
    id: hotspot
    name: Wifi Hotspot
    version: 2.0~ynh3
  2: 
    description: Gestionnaire de mots de passe compatible avec KeePass
    id: keeweb
    name: Keeweb
    version: 1.18.8~ynh1
  3: 
    description: Application Web personnalisée avec accès SFTP pour servir des fichiers statiques (HTML, CSS, JS) et PHP
    id: my_webapp
    name: Mon coin Webapp
    version: 1.0~ynh9
  4: 
    description: Stockage en ligne, plateforme de partage de fichiers et diverses autres applications
    id: nextcloud
    name: Nextcloud
    version: 22.2.10~ynh1
  5: 
    description: Émulateur de terminal web
    id: shellinabox
    name: Terminal
    version: 2.21~ynh3
ended_at: 2022-08-16 08:23:24.700615
error: "La migration 0021_migrate_to_bullseye a \xE9chou\xE9 avec l'exception La distribution\
  \ Debian actuelle n'est pas Buster ! : annulation"
interface: cli
operation: tools_migrations_migrate_forward
parent: null
started_at: 2022-08-16 08:23:24.470638
success: false
yunohost_version: 11.0.9.5

============

2022-08-16 10:23:24,515: INFO - Exécution de la migration 0021_migrate_to_bullseye...
2022-08-16 10:23:24,607: ERROR - La migration 0021_migrate_to_bullseye a échoué avec l'exception La distribution Debian actuelle n'est pas Buster ! : annulation
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/yunohost/tools.py", line 782, in tools_migrations_run
    migration.run()
  File "/usr/lib/python3/dist-packages/yunohost/migrations/0021_migrate_to_bullseye.py", line 80, in run
    self.check_assertions()
  File "/usr/lib/python3/dist-packages/yunohost/migrations/0021_migrate_to_bullseye.py", line 376, in check_assertions
    raise YunohostError("migration_0021_not_buster")
yunohost.utils.error.YunohostError: La distribution Debian actuelle n'est pas Buster !

J’ai tenté de forcer la mise à jour des applications
avec
yunohost app upgrade nextcloud -F

mais j’ai l’erreur suivante : https://paste.yunohost.org/raw/ixatedotop

j’ai tenté :

root@home:~/REPARATIONS# NO_BACKUP_UPGRADE=1 yunohost app upgrade nextcloud
Info : Mise à jour de nextcloud...
Succès ! nextcloud est déjà à jour
Traceback (most recent call last):
  File "/usr/bin/yunohost", line 71, in <module>
    yunohost.cli(
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 25, in cli
    ret = moulinette.cli(
  File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 111, in cli
    Cli(
  File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 505, in run
    ret = self.actionsmap.process(args, timeout=timeout)
  File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 586, in process
    return func(**arguments)
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 690, in app_upgrade
    permission_sync_to_user()
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 657, in permission_sync_to_user
    permissions = user_permission_list(full=True)["permissions"]
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 80, in user_permission_list
    apps_base_path = {
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 84, in <dictcomp>
    and app_setting(app, "domain")
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1131, in app_setting
    app_settings = _get_app_settings(app) or {}
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1719, in _get_app_settings
    settings = {k: v for k, v in settings.items()}
AttributeError: 'NoneType' object has no attribute 'items'

et quand je fais :

# NO_BACKUP_UPGRADE=1 yunohost app upgrade nextcloud
Info : Mise à jour de nextcloud...
Succès ! nextcloud est déjà à jour
Traceback (most recent call last):
  File "/usr/bin/yunohost", line 71, in <module>
    yunohost.cli(
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 25, in cli
    ret = moulinette.cli(
  File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 111, in cli
    Cli(
  File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 505, in run
    ret = self.actionsmap.process(args, timeout=timeout)
  File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 586, in process
    return func(**arguments)
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 690, in app_upgrade
    permission_sync_to_user()
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 657, in permission_sync_to_user
    permissions = user_permission_list(full=True)["permissions"]
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 80, in user_permission_list
    apps_base_path = {
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 84, in <dictcomp>
    and app_setting(app, "domain")
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1131, in app_setting
    app_settings = _get_app_settings(app) or {}
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1719, in _get_app_settings
    settings = {k: v for k, v in settings.items()}
AttributeError: 'NoneType' object has no attribute 'items'

donc nextcloud n’est pas désinstallé (mais impossible de le mettre à jour)

j’ai supprimé nextcloud (pour tenter de le réinstaller)
mais quand je veux le réinstaller :

Choisissez le chemin d'URL (après le domaine) où cette application doit être installée: /nextcloud
Traceback (most recent call last):
  File "/usr/bin/yunohost", line 71, in <module>
    yunohost.cli(
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 25, in cli
    ret = moulinette.cli(
  File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 111, in cli
    Cli(
  File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 505, in run
    ret = self.actionsmap.process(args, timeout=timeout)
  File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 586, in process
    return func(**arguments)
  File "/usr/lib/python3/dist-packages/yunohost/log.py", line 419, in func_wrapper
    result = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 805, in app_install
    questions = ask_questions_and_parse_answers(raw_questions, prefilled_answers=args)
  File "/usr/lib/python3/dist-packages/yunohost/utils/config.py", line 1399, in ask_questions_and_parse_answers
    question = question_class(raw_question, context=context, hooks=hooks)
  File "/usr/lib/python3/dist-packages/yunohost/utils/config.py", line 1189, in __init__
    if root_mail in user_info(user).get("mail-aliases", []):
  File "/usr/lib/python3/dist-packages/yunohost/user.py", line 582, in user_info
    elif username not in user_permission_info("mail.main")["corresponding_users"]:
  File "/usr/lib/python3/dist-packages/yunohost/user.py", line 1301, in user_permission_info
    return user_permission_info(permission)
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 343, in user_permission_info
    existing_permission = user_permission_list(full=True)["permissions"].get(
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 80, in user_permission_list
    apps_base_path = {
  File "/usr/lib/python3/dist-packages/yunohost/permission.py", line 84, in <dictcomp>
    and app_setting(app, "domain")
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1131, in app_setting
    app_settings = _get_app_settings(app) or {}
  File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1719, in _get_app_settings
    settings = {k: v for k, v in settings.items()}
AttributeError: 'NoneType' object has no attribute 'items'

Mokay ben regardons :

ls -l /etc/yunohost/apps/*/settings.yml
ls -l /etc/yunohost/apps/*/settings.yml
ls -l /etc/yunohost/apps/*/settings.yml
-r-------- 1 root root  840 16 août  11:40 /etc/yunohost/apps/freshrss/settings.yml
-r-------- 1 root root 1211 16 août  14:45 /etc/yunohost/apps/hotspot/settings.yml
-r-------- 1 root root  347 16 août  11:36 /etc/yunohost/apps/keeweb/settings.yml
-r-------- 1 root root  842 24 mai   07:42 /etc/yunohost/apps/my_webapp/settings.yml
-r-------- 1 root root 1353 16 août  14:24 /etc/yunohost/apps/nextcloud/settings.yml
-r-------- 1 root root  380 24 juil. 16:47 /etc/yunohost/apps/shellinabox/settings.yml
-r-------- 1 root root    0 11 août  11:06 /etc/yunohost/apps/vpnclient/settings.yml

Visiblement les settings de vpnclient ont disparu … Est-ce que tu as fait une manipulation particulière par rapport à cette app récemment ? (en particulier le 11 août à 11:06)

j’ai fait un :
yunohost app remove nextcloud

 497  yunohost app list
  498  yunohost app remove nextcloud
  499  yunohost app install nextcloud
  500  NO_BACKUP_UPGRADE=1 yunohost app upgrade nextcloud

je peux redescendre la dernière sauvegarde si c’est trop compliqué de réparer nextcloud

Je veux bien croire qu’il y ait des problèmes qui surviennent lorsque tu essayes d’installer ou faire n’importe quelle manip avec n’importe quelle app (donc par exemple nextcloud) mais le problème viens du fait que les settings de vpnclient ont disparu le 11 aout à 11:06 (+/- 1 ou 2 heure car des fois l’affichage est en UTC et ne prends pas en compte l’heure d’été/hiver)

ha ! Alors là un grand merci, je n’avais pas vu ça ! je redescend la sauvegarde du 10 aout ?

Non … La question c’est de comprendre pourquoi ils ont disparu … Est-ce que tu sais ce qu’il se passait sur ton serveur à ce moment précis …