[06:43:09]
<khrys> rodinux, ça me dit :Info : Le fichier de configuration '/etc/apt/sources.list.d/yarn.list' a été supprimé manuellement et ne sera pas créé
apt:
applied:
pending:
/etc/apt/sources.list.d/yarn.list:
diff: @@ -0,0 +1 @@
+deb [signed-by=/etc/apt/trusted.gpg.d/yarn.gpg] https://dl.yarnpkg.com/debian/ stable main
status: removed
[07:25:21]
<Moté> Massinissa: ejabberd isn't in the catalogue anymore. Or I dreamed it was there, and it never has been?
[07:26:04]
<Moté> khrys: tu peux le rajouter avec regen conf, tu as dû le supprimer quand il créait des problèmes de signature
[07:28:13]
<khrys> ok merci :-)
[07:33:03]
<artlog> > Hello, Toujours avec ma restauration assez complexe. Je suis en train de restaurer Transmission. Cela fait deux fois que la restauration échoue (à partir d’une sauvegarde Borg), cette fois avec cette erreur : https://paste.yunohost.org/raw/ifatigepux
026-06-21 00:39:41,865: DEBUG - Jun 21 00:39:41 transmission-daemon[77524]: [2026-06-21 00:39:41.841] Couldn'\''t read "/var/lib/transmission-daemon/.config/transmission-daemon/settings.json": Permission denied
[07:35:41]
<artlog> Voir s'il est possible de restaurer sans echec, c'est le lancement du service après restauration qui échoue. Soit le fichier est manquant soit il n'a pas pas les bons droits... ( je répond d'un smartphone je n'ai pas cherché plus loin )
[07:39:16]
<tituspijean> khrys: tu peux lancer la commande `yunohost tools regen-conf apt --force` sans trop de risque.
(fil similaire sur le forum: https://forum.yunohost.org/t/yarn-and-sury-apt-keys-issues/41617)
(cela fait quelques "incidents" avec les clés de yarn, on gère ça mal j'ai l'impression, mais heureusement ça fait juste grogner apt avec une résolution facile)
[07:49:03]
<tituspijean> Can you try restoring the app with the `--no-remove-on-failure` flag?
The app will be restored, but will be kept despite the service failing.
Then, can you share the output of `ls -la /var/lib/transmission-daemon/.config/transmission-daemon/settings.json` (should be a symlink to another file) and `ls -la /etc/transmission-daemon/settings.json` (should belong to `debian-transmission:debian-transmission`
[08:06:26]
<khrys> tituspijean : merci, c'est ce que j'ai fait suite à la réponse de Moté, le diagnostic est à présent au vert :-)
[08:18:44]
<tituspijean> 🎉
[11:05:52]
<Melchisedech[m]> Thank you! I didn’t think such a flag existed. I should have tried `--help`.
Output of `ls -la /var/lib/transmission-daemon/.config/transmission-daemon/settings.json`:
`lrwxrwxrwx 1 root root 38 Jun 21 12:32 /var/lib/transmission-daemon/.config/transmission-daemon/settings.json -> /etc/transmission-daemon/settings.json`
Output of `ls -la /etc/transmission-daemon/settings.json`:
`-rw------- 1 root root 2497 Jun 15 01:57 /etc/transmission-daemon/settings.json`
I guess I should just `chown debian-transmission:debian-transmission` on both, right?
[12:14:23]
<Melchisedech[m]> Ok, I did that, started the daemon and got a 404 errot when trying to open transmission page. So I restarted the server, and now everything is fine. Thank you!
[15:15:03]
<tituspijean> A simple restart of the NGINX service would have been enough after the `chown`.
Glad you fixed it, enjoy!
[20:00:47]
<Melchisedech[m]> Ok, so now, everything is restored, including Borg Backup. I only have two minor problems left (and the second one was already there before):
1. Although diagnosis don’t report anything about that, twice and hour (hh:00 and hh:50) I receive a mail with the object:
Cron <root@xxxxxx> /usr/bin/yunohost firewall upnp status >>/dev/null
and as content: ERROR Could not open port via UPnP
2. With every of these mails (as some other mails from the system, such as backup reports), I get a mail with object:
Undelivered Mail Returned to Sender
And the standard content you get in such cases. It’s worth noting I initially installed the system in 2020 and the problem occurred after a major migration (maybe Yunohost 4 to Yunohost 11, if such a migration ever existed).