|
|
|
|
|
|
ecombox.log (596 bytes)
Configuration d'e-comBox le Mon 15 Mar 2021 10:55:39 AM UTC
mv: 'licenceCeCILL.txt' and '/opt/e-comBox/licenceCeCILL.txt' are the same file
L'adresse IP ou le nom de domaine utilisé est ecombox.gnaritas.fr
Aucun proxy configuré sur le système
Le réseau [1;33m192.168.97.0/24[0;36m est utilisé.
Portainer existe et va être remplacé.
Portainer a été lancé.
Le reverse proxy existe et va être remplacé.
Le reverse proxy a été lancé.
e-comBox existe et va être remplacée.
e-comBox a été lancée.
L'URL llb.ac-corse.fr:11251 est remplacée par ecombox.gnaritas.fr:8880.
ecombox-error.log (5,121 bytes)
Cloning into 'e-comBox_portainer'...
Creating volume "e-combox_portainer_portainer-data" with default driver
Pulling proxy (reseaucerta/portainer-proxy:2.1)...
Pulling portainer (portainer/portainer:1.22.0)...
Creating portainer-proxy ...
Creating portainer-app ...
[2A[2K
Creating portainer-proxy ... [32mdone[0m
[2B[1A[2K
Creating portainer-app ... [32mdone[0m
[1BCloning into 'e-comBox_reverseproxy'...
Creating volume "e-combox_reverseproxy_nginx-conf" with default driver
Creating volume "e-combox_reverseproxy_nginx-html" with default driver
Creating volume "e-combox_reverseproxy_nginx-docker-gen-templates" with default driver
Pulling nginx (nginx:)...
Pulling nginx-docker_gen (reseaucerta/docker-gen:2.1)...
Creating nginx ...
[1A[2K
Creating nginx ... [32mdone[0m
[1BCreating docker-gen ...
[1A[2K
Creating docker-gen ... [32mdone[0m
[1BError response from daemon: conflict: unable to delete 6084105296a9 (cannot be forced) - image is being used by running container f9ece4afdba9
Error response from daemon: conflict: unable to delete 69e2263a2fde (cannot be forced) - image is being used by running container 9bc07a728919
Error response from daemon: conflict: unable to delete a9cce9abd107 (cannot be forced) - image is being used by running container e6611c497087
Error response from daemon: conflict: unable to delete 8ea4ff29042d (cannot be forced) - image is being used by running container d3c67910f423
Error response from daemon: conflict: unable to delete 2b4ddf654e1c (cannot be forced) - image is being used by running container a1154f102284
Cloning into 'e-comBox_portainer'...
Creating portainer-proxy ...
Creating portainer-app ...
[1A[2K
Creating portainer-app ... [32mdone[0m
[1B[2A[2K
Creating portainer-proxy ... [32mdone[0m
[2Be-combox_reverseproxy_nginx-html
e-combox_reverseproxy_nginx-docker-gen-templates
Cloning into 'e-comBox_reverseproxy'...
Creating volume "e-combox_reverseproxy_nginx-html" with default driver
Creating volume "e-combox_reverseproxy_nginx-docker-gen-templates" with default driver
Pulling nginx-docker_gen (reseaucerta/docker-gen:2.1)...
Creating nginx ...
[1A[2K
Creating nginx ... [32mdone[0m
[1BCreating docker-gen ...
[1A[2K
Creating docker-gen ... [32mdone[0m
[1BError response from daemon: conflict: unable to delete 64e7f999b155 (must be forced) - image is being used by stopped container ffb01e049a9c
Error response from daemon: conflict: unable to delete 6084105296a9 (cannot be forced) - image is being used by running container 921de75beb60
Error response from daemon: conflict: unable to delete 040c5cbfb26e (cannot be forced) - image is being used by running container 92e5070632f9
Error response from daemon: conflict: unable to delete 09d61673c2f6 (cannot be forced) - image is being used by running container ac18d8fa3738
Error response from daemon: conflict: unable to delete 69e2263a2fde (cannot be forced) - image is being used by running container 22e123080d75
Error response from daemon: conflict: unable to delete 145cf2be0465 (must be forced) - image is being used by stopped container 47e52bedfa7f
Error response from daemon: conflict: unable to delete 273e7daab513 (must be forced) - image is being used by stopped container 98214aed5cd8
Error response from daemon: conflict: unable to delete 9b6f29eb1a11 (must be forced) - image is being used by stopped container ec658c74d015
Error response from daemon: conflict: unable to delete a9cce9abd107 (cannot be forced) - image is being used by running container 3c1b9a325c98
Error response from daemon: conflict: unable to delete bee294c12b44 (must be forced) - image is being used by stopped container 9d0ab0faafe0
Error response from daemon: conflict: unable to delete 15cc4e88e78f (must be forced) - image is being used by stopped container d8168c604259
Error response from daemon: conflict: unable to delete 22e2ff883936 (must be forced) - image is being used by stopped container 60f3bff332fd
Error response from daemon: conflict: unable to delete bf737491ef10 (must be forced) - image is being used by stopped container 1fed056b0aa2
Error response from daemon: conflict: unable to delete f7a77e93a423 (must be forced) - image is being used by stopped container 3ce2b45555a3
Error response from daemon: conflict: unable to delete b0be064d60cf (must be forced) - image is being used by stopped container f82d7af440d4
Error response from daemon: conflict: unable to delete ad76aeb7d9e2 (must be forced) - image is being used by stopped container a6f2abc96a68
Error response from daemon: conflict: unable to delete 8ea4ff29042d (cannot be forced) - image is being used by running container 55472269df65
Error response from daemon: conflict: unable to delete 3b59c7a4a0a6 (must be forced) - image is being used by stopped container c9115b81f087
Error response from daemon: conflict: unable to delete 2b4ddf654e1c (cannot be forced) - image is being used by running container acac36c9c793
Error response from daemon: conflict: unable to delete 67b305f99b77 (must be forced) - image is being used by stopped container b91be76db97f
|
|
|
|
Bonjour,
Pouvez-vous nous donner plus de détails sur les actions réalisées (et dans quel ordre) ?
Ces erreurs sont venues à quel moment ? Des sites étaient déjà créés et étaient fonctionnels ?
Plus rien n'a fonctionné après la création d'un nouveau site ?
Les messages d'erreurs postés ne concernent pas les mêmes sites, vous avez tenté plusieurs actions simultanément ?
Cordialement, |
|
|
|
Il s'agit de tests fait par des enseignants à distance, donc je ne connais pas l'ordre exact, mais en gros
- un utilisateur a tenté de créer des sites
- à partir d'un moment, plus aucune création de sites n'a fonctionné (message "erreur réseau")
- j'ai rebooté le serveur : les sites déjà créés sont fonctionnels, les sites créés lors du message d'erreur apparaissent, mais ne fonctionnent pas et ne sont pas supprimables
|
|
|
|
Bonsoir,
Les professeurs ont peut-être alors sans le vouloir créé des sites en même temps et Docker gère cela très mal.
Pour les supprimer il faut passer par Portainer via la gestion avancée de l'e-combox (accès admin). Il faut supprimer les conteneurs qui ont un soucis (normalement 2 conteneurs par site mais, compte tenu du problème, il se peut qu'il y en ait un seul). Vous pouvez y accéder en cliquant sur le nom du stack (un stack par site créé) ou directement via le menu conteneurs.
Cordialement, |
|
|
|
Merci, c'est exactement ce que je voulais savoir :) |
|
