I’m trying to update (and upgrade) Jessie in order to migrate but i have problems with source
The path is unavailable
Err http://httpredir.debian.org jessie-backports/main amd64 Packages
404 Not Found [IP : 151.101.36.204 80]
Ign http://ftp.debian.org jessie-updates/contrib Translation-fr_FR
Ign http://ftp.debian.org jessie-updates/contrib Translation-fr
Ign http://ftp.debian.org jessie-updates/contrib Translation-en
Ign http://ftp.debian.org jessie-updates/main Translation-fr_FR
Ign http://ftp.debian.org jessie-updates/main Translation-fr
Ign http://ftp.debian.org jessie-updates/main Translation-en
Ign http://ftp.debian.org jessie-updates/non-free Translation-fr_FR
Ign http://ftp.debian.org jessie-updates/non-free Translation-fr
Ign http://ftp.debian.org jessie-updates/non-free Translation-en
Err http://ftp.debian.org jessie-updates/main amd64 Packages
404 Not Found [IP : 130.89.148.12 80]
Err http://ftp.debian.org jessie-updates/contrib amd64 Packages
404 Not Found [IP : 130.89.148.12 80]
Err http://ftp.debian.org jessie-updates/non-free amd64 Packages
404 Not Found [IP : 130.89.148.12 80]
1 044 ko réceptionnés en 3s (263 ko/s)
It’s true the path are not available on servers, i think the maintainers delete (or move) the folders
Anyone have an idea to solved this issue ?
Is it the right thing to do (forget the unavailable target) and proceed to upgrade ?
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/moulinette/interfaces/api.py", line 406, in process
ret = self.actionsmap.process(arguments, timeout=30, route=_route)
File "/usr/lib/python2.7/dist-packages/moulinette/actionsmap.py", line 498, in process
return func(**arguments)
File "/usr/lib/moulinette/yunohost/tools.py", line 426, in tools_update
if not cache.update():
File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 443, in update
raise FetchFailedException(e)
FetchFailedException: W:Impossible de récupérer http://ftp.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found [IP : 130.89.148.12 80]
, W:Impossible de récupérer http://httpredir.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages 404 Not Found [IP : 151.101.36.204 80]
, W:Impossible de récupérer http://ftp.debian.org/debian/dists/jessie-updates/contrib/binary-amd64/Packages 404 Not Found [IP : 130.89.148.12 80]
, W:Impossible de récupérer http://ftp.debian.org/debian/dists/jessie-updates/non-free/binary-amd64/Packages 404 Not Found [IP : 130.89.148.12 80]
, E:Le téléchargement de quelques fichiers d'index a échoué, ils ont été ignorés, ou les anciens ont été utilisés à la place.
Mar 31 23:13:35 totofr systemd[1]: avahi-daemon.service: Failed to reset devices.list: Operation not permitted
Mar 31 23:13:35 totofr systemd[1]: Starting Avahi mDNS/DNS-SD Stack…
Mar 31 23:13:35 totofr avahi-daemon[16761]: Found user ‘avahi’ (UID 989) and group ‘avahi’ (GID 989).
Mar 31 23:13:35 totofr avahi-daemon[16761]: Successfully dropped root privileges.
Mar 31 23:13:35 totofr avahi-daemon[16761]: chroot.c: fork() failed: Resource temporarily unavailable
Mar 31 23:13:35 totofr avahi-daemon[16761]: failed to start chroot() helper daemon.
Mar 31 23:13:35 totofr systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/n/a
Mar 31 23:13:35 totofr systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
Mar 31 23:13:35 totofr systemd[1]: avahi-daemon.service: Unit entered failed state.
Mar 31 23:13:35 totofr systemd[1]: avahi-daemon.service: Failed with result ‘exit-code’.
Mar 31 23:13:35 totofr yunohost-api[286]: Job for avahi-daemon.service failed because the control process exited with error code.
Mar 31 23:13:35 totofr yunohost-api[286]: See “systemctl status avahi-daemon.service” and “journalctl -xe” for details.
And i can’t update kanboard, roundcube, phpmyadmin… but no problem to update mattermost, mailman for example.
Hmokay ? Not sure why there’s an issue with the avahi-daemon … the message ’ fork() failed: Resource temporarily unavailable’ sounds related to a lack of RAM maybe…
We are not wizards who can magically guess what’s happening if you don’t explain why it doesn’t work or provide any log / error message …
Salut mon problème avec avahi s’est résolu après une série de dpkg-reconfigure pour les paquets yunohost, yunohost-admin , avahi-daemon et libnss-mdns:amd64 plus des apt update, apt upgrade aprés plusieurs essai tout est passé.
Il se trouve que j’ai 2 container Yunohost et j’ai eu un message d’erreur m’indiquant que le hostname yunohost.local était déjà pris il m’a donc renommé le hostname en yunohost-2.local
Aleks (que j’ai vu au JDLL2019) m’a dit que le service avahi s’occupé d’autoconf local (zeroconf peut être) bref c’est bon, j’ai sauvegardé mes container.
Et il me reste à tester les majs d’appli
Merci