je suis sur un vps OVH.
j’ai lancé la migration yuno 2.7 debian 8 vers yuno 3.1 debian 9 (oui, je suis kamikaze)
yunohost version OK : 3.1.0
lsb_release -a OK : 9.5
A priori, tout semble OK (bravo pour le travail accompli), sauf redis-server un apt-upgrade me donne ceci,
Paramétrage de redis-server (3:3.2.6-3+deb9u2) ...
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
invoke-rc.d: initscript redis-server, action "start" failed.
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-08-16 17:08:04 CEST; 15ms ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 19007 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=226/NAMESPACE)
Process: 19003 ExecStartPre=/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d (code=exited, status=226/NAMESPACE)
août 16 17:08:04 vps156227.ovh.net systemd[1]: Failed to start Advanced key-value store.
août 16 17:08:04 vps156227.ovh.net systemd[1]: redis-server.service: Unit entered failed state.
août 16 17:08:04 vps156227.ovh.net systemd[1]: redis-server.service: Failed with result 'exit-code'.
dpkg: erreur de traitement du paquet redis-server (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
dpkg: des problèmes de dépendances empêchent la configuration de yunohost :
yunohost dépend de redis-server ; cependant :
Le paquet redis-server n'est pas encore configuré.
dpkg: erreur de traitement du paquet yunohost (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de yunohost-admin :
yunohost-admin dépend de yunohost (>= 2.7.6) ; cependant :
Le paquet yunohost n'est pas encore configuré.
dpkg: erreur de traitement du paquet yunohost-admin (--configure) :
problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
redis-server
yunohost
yunohost-admin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Effet de bord, j’ai roundcube qui me demande un identifiant/mot de passe.
Hmmm alors il faudrait comprendre pourquoi redis n’est pas content …
Est-ce que si tu tentes un systemctl restart redis ca améliore la situation ? Si ce n’est pas le cas, est-ce que tu peux donner la sortie de tail -n 50 /var/log/daemon.log (en espérant qu’on puisse y trouver des infos sur redis)
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Aug 17 12:00:20 vps156227 systemd[1]: proc-sys-fs-binfmt_misc.automount: Cannot add dependency job, ignoring: Unit proc-sys-fs-binfmt_misc.automount is masked.
Aug 17 12:00:20 vps156227 systemd[1]: Stopped Advanced key-value store.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Aug 17 12:00:20 vps156227 systemd[1]: Starting Advanced key-value store...
Aug 17 12:00:20 vps156227 systemd[5840]: redis-server.service: Failed at step NAMESPACE spawning /bin/run-parts: Too many levels of symbolic links
Aug 17 12:00:20 vps156227 systemd[5843]: redis-server.service: Failed at step NAMESPACE spawning /usr/bin/redis-server: Too many levels of symbolic links
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Control process exited, code=exited status=226
Aug 17 12:00:20 vps156227 systemd[1]: Failed to start Advanced key-value store.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Unit entered failed state.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Aug 17 12:00:20 vps156227 systemd[1]: proc-sys-fs-binfmt_misc.automount: Cannot add dependency job, ignoring: Unit proc-sys-fs-binfmt_misc.automount is masked.
Aug 17 12:00:20 vps156227 systemd[1]: Stopped Advanced key-value store.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Aug 17 12:00:20 vps156227 systemd[1]: Starting Advanced key-value store...
Aug 17 12:00:20 vps156227 systemd[5847]: redis-server.service: Failed at step NAMESPACE spawning /bin/run-parts: Too many levels of symbolic links
Aug 17 12:00:20 vps156227 systemd[5850]: redis-server.service: Failed at step NAMESPACE spawning /usr/bin/redis-server: Too many levels of symbolic links
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Control process exited, code=exited status=226
Aug 17 12:00:20 vps156227 systemd[1]: Failed to start Advanced key-value store.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Unit entered failed state.
Aug 17 12:00:20 vps156227 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Aug 17 12:00:21 vps156227 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Aug 17 12:00:21 vps156227 systemd[1]: proc-sys-fs-binfmt_misc.automount: Cannot add dependency job, ignoring: Unit proc-sys-fs-binfmt_misc.automount is masked.
Aug 17 12:00:21 vps156227 systemd[1]: Stopped Advanced key-value store.
Aug 17 12:00:21 vps156227 systemd[1]: redis-server.service: Start request repeated too quickly.
Aug 17 12:00:21 vps156227 systemd[1]: Failed to start Advanced key-value store.
Aug 17 12:00:21 vps156227 systemd[1]: redis-server.service: Unit entered failed state.
Aug 17 12:00:21 vps156227 systemd[1]: redis-server.service: Failed with result 'exit-code'.
on peut clore, j’ai finalement upgrader mon VPS chez OVH, restaurer mon backup post install vers 3.1.0
j’ai d’ailleurs lancé 2 fois la resto, car au premier coup, l’appli agendav ne voulait pas s’installer
Warning: You must install Baïkal or Radicale before
Error: Unable to restore the app ‘agendav’
mais voilà mon serveur repartit sur une nouvelle config matériel, ça roule du tonnerre, j’ai récupéré mon roundcube, ttrss et wallabag
Bravo pour le travail réalisé sur la partie backup/resto.
Hey,
I had exactly the same error with redis server after the migration to stretch.
I fixed this changing the service config in /etc/systemd/system/redis.service:
Changing the line: ReadWriteDirectories=-/var/run/redis
to : ReadWriteDirectories=-/run/redis
un apt-upgrade me donne ceci,