Après docker pull sleede/fab-manager ?

ths · Septembre 19, 2019, 8:46

Salut !

Je me demandais … juste après la commande docker pull sleede/fab-manager je reprends où dans le guide d’installation ?
Quand j’executer la commande: docker run sleede/fab-manager
curl -i 127.0.0.1:3000 retourne rien et dans le navigateur c’est un beau time out.

Je découvre Docker… désolé c’est peut-être une question un peu bête.

Belle journée !

Sylvain · Septembre 19, 2019, 1:51

Salut,

Est-ce que tu t’es référé au guide d’installation https://github.com/sleede/fab-manager/blob/master/docker/README.md#install-fabmanager ?
Normalement après un pull, il faut configurer les bases de données, puis construire les assets puis up -d pour lancer le tout.
Dans tous les cas, utilise docker-compose pour gérer le logiciel, ce sera beaucoup plus simple !

Bonne journée à toi

ths · Septembre 19, 2019, 4:14

Salut, Merci de ta réponse !

Je réédire ma réponse car j’avais une difficulté que j’ai finalement résolue.
Maintenant, j’ai ça
En http: « We’re sorry, but something went wrong. »
dans le log error:
2019/09/19 17:21:43 [error] 6#6: *15 connect() failed (111: Connection refused) while connecting to upstream, client: 37.166.201.23, server: epn.MONSITE.fr, request: "GE$

J’ai mis la variable: server_name= epn.MONSITE.fr dans config/nginx/fabmanager.conf

J’ai mis ça dans mon /etc/hosts

Je vois pas quoi faire de plus… une petite idée ? Cela peut-il venir de UFW ?

’

Sylvain · Septembre 20, 2019, 7:11

Salut,
Je ne pense pas qu’il soit nécessaire de mettre ton ip dans le fichier hosts, normalement les serveur dns devraient faire la redirection tout seuls.
Sinon, pour déboguer ton installation, tu peux regarder ce qui se passe dans les logs serveur avec tail -f /apps/fabmanager/log/app-stdout.log

ths · Septembre 20, 2019, 9:09

Merci… voici les différents logs,
je note une erreur (WARN) de key que j’essaye de réduire avec le post ici : [RÉSOLU] Erreur db:migrate

app-stdout.log

=> Booting Puma
=> Rails 4.2.11.1 application starting in production on http://0.0.0.0:3000
=> Run rails server -h for more startup options
=> Ctrl-C to shutdown server
Exiting

/access.log

82.98.51.51 - - [20/Sep/2019:08:26:12 +0000] « GET / HTTP/1.1 » 502 1477 « - » « Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 » « - »

/app-stderr.log
> from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:337:in `wrapped_app’

from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:273:in `start'
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/server.rb:80:in `start'
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:80:in `block in server'
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in `tap'
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in `server'
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands.rb:17:in `<top (required)>'
from bin/rails:4:in `require'
from bin/rails:4:in `<main>'

[WARN] table ‹ Role › doesn’t exist. Did you run the migration ? Ignoring rolify config.
/usr/local/bundle/gems/devise-4.7.1/lib/devise/rails/routes.rb:500:in `raise_no_secret_key’: Devise.secret_key was not set. Please add the following to your Devise initializer: (RuntimeError)

config.secret_key = ‹ 3019cb24d52c188cc97c571f15943015c17ca926c0bff15d35109962826e425d0caf189e2bd9f4f8861f05a8d08b4e8712b5b878ec12f398f9aa982b5d0c199d ›

Please ensure you restarted your application after installing Devise or setting the key.

supervisord.log

2019-09-20 09:12:04,725 INFO exited: worker (exit status 1; not expected)
2019-09-20 09:12:05,727 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-20 09:12:05,729 INFO spawned: ‹ worker › with pid 3511
2019-09-20 09:12:06,731 INFO success: worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

log/worker-stderr.log

/usr/local/lib/ruby/site_ruby/2.3.0/bundler/cli.rb:463:in exec' /usr/local/lib/ruby/site_ruby/2.3.0/bundler/vendor/thor/lib/thor/command.rb:27:in run’
/usr/local/lib/ruby/site_ruby/2.3.0/bundler/vendor/thor/lib/thor/invocation.rb:126:in invoke_command' /usr/local/lib/ruby/site_ruby/2.3.0/bundler/vendor/thor/lib/thor.rb:387:in dispatch’
/usr/local/lib/ruby/site_ruby/2.3.0/bundler/cli.rb:27:in dispatch' /usr/local/lib/ruby/site_ruby/2.3.0/bundler/vendor/thor/lib/thor/base.rb:466:in start’
/usr/local/lib/ruby/site_ruby/2.3.0/bundler/cli.rb:18:in start' /usr/local/bin/bundle:30:in block in ’
/usr/local/lib/ruby/site_ruby/2.3.0/bundler/friendly_errors.rb:124:in with_friendly_errors' /usr/local/bin/bundle:22:in ’
[WARN] table ‹ Role › doesn’t exist. Did you run the migration ? Ignoring rolify config.
Devise.secret_key was not set. Please add the following to your Devise initializer:

config.secret_key = ‹ 3b83231da4d7dc222c269487debd01274f187c3bb8870462d292b17c301316acc6a9641d00080248b29f21cb74ad5a22470d218a91c6463a7bd513d44487a4d9 ›

Please ensure you restarted your application after installing Devise or setting the key.
/usr/local/bundle/gems/devise-4.7.1/lib/devise/rails/routes.rb:500:in raise_no_secret_key' /usr/local/bundle/gems/devise-4.7.1/lib/devise/rails/routes.rb:228:in devise_for’

ths · Septembre 20, 2019, 10:19

Je continue, je n’ai plus l’erreur de KEY ! cool.
Bon j’ai toujours un soucis:
2019/09/20 10:16:24 [error] 6#6: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 82.98.51.51, server: epn.monsite.fr, request: « GET / HTTP/1.1 », upstream: « http://172.18.0.5:3000/ », host: « epn.monsite.fr »

Sylvain · Septembre 20, 2019, 12:29

J’ai l’impression que tu n’a pas configuré le fichier env…
C’est un prérequis pour que l’application puisse démarrer ! Plus d’infos ici : fab-manager/environment.md at master · sleede/fab-manager · GitHub

ths · Septembre 21, 2019, 9:10

Effectivement, je n’y ai pas touché. Je suis pas sûr d’avoir compris… je vais essayer…

ths · Septembre 21, 2019, 9:39

Non décidement je n’y comprends rien. Je vois bien les trucs à remplir mais quand je suis la doc … j’ai l’impression d’un truc compliqué … et mon intuition me dit que je fais fausse route…
les hosts c’est localhost non ? ou l’ip du container ?
docker inspect -f "{{ .NetworkSettings.Networks.nat.IPAddress }}" fabmanager_fabmanager_1
renvoi : no value

Plus tout le reste mais je n’y connais rien… et je trouve ça bien bizarre de rentrer dans ces détails. . ici il est indiqué:

otherwise this is configured in config/database.yml.

Mais je n’ai aucun fichier de ce type pour prendre des hosts, des pass, des key…

Je me trompe où ?

Bonne soirée !

Sylvain · Septembre 23, 2019, 12:20

Tu m’as l’air bien perdu

En fait database.yml (et application.yml) sont des fichiers utilisés en mode développement. Si tu veux seulement installer fab-manager pour l’utiliser (et non pour développer), tu ne verras pas ces fichiers car ils sont « cachés » à l’intérieur du container docker.

Déjà, il y a un fichier env d’exemple fourni, je ne sais pas si tu l’as vu ? Tu peux partir de lui.

Les adresses de postgre sql, redis et elasticsearch devraient fonctionner avec les valeurs par défaut car docker-compose crée un sous-réseau pour toutes les images au sein d’un même fichier compose. Dans ce sous-réseau des noms d’hôtes sont automatiquement définis en fonction du nom des services (par exemple postgres).

Je vais peut-être compléter la doc sur ce point, c’est possible que ça ne soit pas très clair

Bonne journée

PetitPhoenix · Septembre 24, 2019, 9:54

Coucou,

Pour ma part, quand je fais une modif du fichier de paramètres (installation via docker-compose) :

1.Eteindre l’appli et modifier le fichier ENV
cd /apps/fabmanager docker-compose stop fabmanager nano config/env

2.Supprimer les assets et les refaire et relancer l’appli :
rm -Rf public/assets/ docker-compose run --rm fabmanager bundle exec rake assets:precompile docker-compose down docker-compose up -d

ths · Septembre 27, 2019, 12:39

salut !

Merci pour vos réponses. J’ai fais les manips avec le ENV d’exemple et ça ne change pas la situation. Bizarrement d’ailleurs au moment de faire docker-compose stop fabmanager il cherchait un fichier ENV dans config/config. Le ENV était dans config/ mais j’ai quand même crée un dossier config/ de plus dans le dossier /config et copier le ENV à l’intérieur. Cela a permis à la commande de s’exécuter.
Pour le reste j’ai toujours: We’re sorry, but something went wrong. Je ferai peut-être mieux de réinstaller ? Pour cela il suffit de supprimer le dossier /app/fabmanager ?

Quelques logs:

ths@vps731349:/apps/fabmanager$ tail -n 10 log/app-stderr.log
from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:337:in wrapped_app' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:273:in start’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/server.rb:80:in start' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:80:in block in server’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in tap' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in server’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:39:in run_command!' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands.rb:17:in <top (required)>’
from bin/rails:4:in require' from bin/rails:4:in ’

ths@vps731349:/apps/fabmanager$ tail -n 10 log/app-stdout.log
AuthProvider Load (0.5ms) SELECT « auth_providers ».* FROM « auth_providers » WHERE « auth_providers ».« status » = $1 LIMIT 1 [[« status », « active »]]
Exiting
=> Booting Puma
=> Rails 4.2.11.1 application starting in production on http://0.0.0.0:3000
=> Run rails server -h for more startup options
=> Ctrl-C to shutdown server
AuthProvider Load (0.5ms) SELECT « auth_providers ».* FROM « auth_providers » WHERE « auth_providers ».« status » = $1 LIMIT 1 [[« status », « active »]]
AuthProvider Load (3.9ms) SELECT « auth_providers ».* FROM « auth_providers » WHERE « auth_providers ».« status » = $1 LIMIT 1 [[« status », « active »]]
AuthProvider Load (0.4ms) SELECT « auth_providers ».* FROM « auth_providers » WHERE « auth_providers ».« status » = $1 LIMIT 1 [[« status », « active »]]
AuthProvider Load (5.4ms) SELECT « auth_providers ».* FROM « auth_providers » WHERE « auth_providers ».« status » = $1 LIMIT 1 [[« status », « active »]]

ici j’ai des erreurs notamment sur epn.siberry.fr, mais c’est normal mon adresse n’est pas configuré sur le DNS. C’est indispensable ? J’ai pour habitude de faire ça dans mon fichier en hosts en local quand je suis entrain de configurer un serveur…

2019/09/26 20:03:44 [error] 6#6: *1600 connect() failed (111: Connection refused) while connecting to upstream, client: 198.12.86.18, server: epn.siberry.fr, request: « GET /HNAP1/ HTTP/1.1 », upstream: « http://172.18.0.5:3000/HNAP1/ », host: « 51.77.210.51 », referrer: « http://51.77.210.51/ »
2019/09/26 21:13:36 [error] 6#6: *1602 connect() failed (111: Connection refused) while connecting to upstream, client: 95.78.170.10, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.18.0.5:3000/ », host: « 51.77.210.51:80 »
2019/09/26 23:55:45 [error] 6#6: *1604 connect() failed (111: Connection refused) while connecting to upstream, client: 201.76.120.222, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.18.0.5:3000/ », host: « 51.77.210.51:80 »
2019/09/26 23:55:51 [error] 6#6: *1606 connect() failed (111: Connection refused) while connecting to upstream, client: 200.112.228.126, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.18.0.5:3000/ », host: « 51.77.210.51:80 »
2019/09/27 00:22:53 [error] 6#6: *1608 connect() failed (111: Connection refused) while connecting to upstream, client: 54.68.55.144, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.18.0.5:3000/ », host: « telephone-pliable.tech »
2019/09/27 00:25:37 [error] 6#6: *1610 connect() failed (111: Connection refused) while connecting to upstream, client: 37.164.93.176, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.18.0.5:3000/ », host: « epn.siberry.fr »
2019/09/27 00:25:37 [error] 6#6: *1610 connect() failed (111: Connection refused) while connecting to upstream, client: 37.164.93.176, server: epn.siberry.fr, request: « GET /favicon.ico HTTP/1.1 », upstream: « http://172.18.0.5:3000/favicon.ico », host: « epn.siberry.fr »
2019/09/27 00:25:37 [error] 6#6: *1613 connect() failed (111: Connection refused) while connecting to upstream, client: 37.164.93.176, server: epn.siberry.fr, request: « GET /favicon.ico HTTP/1.1 », upstream: « http://172.18.0.5:3000/favicon.ico », host: « epn.siberry.fr »
2019/09/27 00:28:03 [error] 6#6: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 37.164.93.176, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.19.0.5:3000/ », host: « epn.siberry.fr »
2019/09/27 00:28:06 [error] 6#6: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 37.164.93.176, server: epn.siberry.fr, request: « GET / HTTP/1.1 », upstream: « http://172.19.0.5:3000/ », host: "epn.siberry.fr

Vous auriez d’autres pistes… désolé …

Sylvain · Septembre 30, 2019, 2:15

À première vue je dirais qu’il te manque un rake db:seed (et donc peut-être aussi les autres commandes rake db:xxx), mais peux-tu nous donner plus de logs que les 10 dernières lignes ? Là, on ne voit pas le début de l’erreur.

Concernant le nom de domaine, ce n’est obligatoire que si tu met un certificat SSL avec let’s encrypt.

ths · Octobre 3, 2019, 1:27

Salut,

Je ne m’en sors pas… merci de ton aide !

error.log
ths@vps731349:/apps/fabmanager$ tail -n 30 log/error.log 2019/10/03 00:21:05 [error] 6#6: *1709 connect() failed (111: Connection refused) while connecting to upstream, client: 67.227.98.157, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "smartfold.fr" 2019/10/03 00:45:31 [error] 6#6: *1711 connect() failed (111: Connection refused) while connecting to upstream, client: 185.191.105.25, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 01:03:53 [error] 6#6: *1713 connect() failed (111: Connection refused) while connecting to upstream, client: 148.72.152.67, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "telephone-pliable.tech" 2019/10/03 01:56:19 [error] 6#6: *1716 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET /TP/public/index.php HTTP/1.1", upstream: "http://172.19.0.5:3000/TP/public/index.php", host: "51.77.210.51" 2019/10/03 01:56:21 [error] 6#6: *1718 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET /TP/index.php HTTP/1.1", upstream: "http://172.19.0.5:3000/TP/index.php", host: "51.77.210.51" 2019/10/03 01:56:21 [error] 6#6: *1720 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET /thinkphp/html/public/index.php HTTP/1.1", upstream: "http://172.19.0.5:3000/thinkphp/html/public/index.php", host: "51.77.210.51" 2019/10/03 01:56:21 [error] 6#6: *1722 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET /html/public/index.php HTTP/1.1", upstream: "http://172.19.0.5:3000/html/public/index.php", host: "51.77.210.51" 2019/10/03 01:56:23 [error] 6#6: *1724 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET /public/index.php HTTP/1.1", upstream: "http://172.19.0.5:3000/public/index.php", host: "51.77.210.51" 2019/10/03 01:56:24 [error] 6#6: *1726 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET /TP/html/public/index.php HTTP/1.1", upstream: "http://172.19.0.5:3000/TP/html/public/index.php", host: "51.77.210.51" 2019/10/03 01:56:29 [error] 6#6: *1728 connect() failed (111: Connection refused) while connecting to upstream, client: 120.92.12.108, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 02:13:14 [error] 6#6: *1730 connect() failed (111: Connection refused) while connecting to upstream, client: 128.14.134.134, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51" 2019/10/03 03:02:51 [error] 6#6: *1732 connect() failed (111: Connection refused) while connecting to upstream, client: 130.204.14.153, server: epn.siberry.fr, request: "GET / HTTP/1.0", upstream: "http://172.19.0.5:3000/" 2019/10/03 03:32:49 [error] 6#6: *1734 connect() failed (111: Connection refused) while connecting to upstream, client: 142.93.113.182, server: epn.siberry.fr, request: "GET /wp-login.php HTTP/1.1", upstream: "http://172.19.0.5:3000/wp-login.php", host: "telephone-pliable.tech" 2019/10/03 03:34:14 [error] 6#6: *1736 connect() failed (111: Connection refused) while connecting to upstream, client: 171.67.70.80, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51" 2019/10/03 03:56:23 [error] 6#6: *1738 connect() failed (111: Connection refused) while connecting to upstream, client: 103.81.84.140, server: epn.siberry.fr, request: "GET /wp-login.php HTTP/1.1", upstream: "http://172.19.0.5:3000/wp-login.php", host: "vps640080.ovh.net" 2019/10/03 07:02:43 [error] 6#6: *1741 connect() failed (111: Connection refused) while connecting to upstream, client: 124.158.6.218, server: epn.siberry.fr, request: "GET //phpmyadmin// HTTP/1.1", upstream: "http://172.19.0.5:3000//phpmyadmin//", host: "51.77.210.51:80" 2019/10/03 07:58:02 [error] 6#6: *1743 connect() failed (111: Connection refused) while connecting to upstream, client: 189.68.32.175, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 08:01:47 [error] 6#6: *1747 connect() failed (111: Connection refused) while connecting to upstream, client: 5.188.210.101, server: epn.siberry.fr, request: "GET http://5.188.210.101/echo.php HTTP/1.1", upstream: "http://172.19.0.5:3000/echo.php", host: "5.188.210.101", referrer: "https://www.google.com/" 2019/10/03 08:09:35 [error] 6#6: *1750 connect() failed (111: Connection refused) while connecting to upstream, client: 70.185.48.228, server: epn.siberry.fr, request: "GET //phpadmin// HTTP/1.1", upstream: "http://172.19.0.5:3000//phpadmin//", host: "51.77.210.51:80" 2019/10/03 08:45:04 [error] 6#6: *1753 connect() failed (111: Connection refused) while connecting to upstream, client: 177.94.255.211, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 09:12:02 [error] 6#6: *1756 connect() failed (111: Connection refused) while connecting to upstream, client: 194.67.174.190, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 10:29:24 [error] 6#6: *1760 connect() failed (111: Connection refused) while connecting to upstream, client: 181.114.128.223, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 10:32:41 [error] 6#6: *1762 connect() failed (111: Connection refused) while connecting to upstream, client: 152.165.53.192, server: epn.siberry.fr, request: "GET //myadmin// HTTP/1.1", upstream: "http://172.19.0.5:3000//myadmin//", host: "51.77.210.51:80" 2019/10/03 10:49:20 [error] 6#6: *1764 connect() failed (111: Connection refused) while connecting to upstream, client: 177.94.234.131, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 12:10:11 [error] 6#6: *1768 connect() failed (111: Connection refused) while connecting to upstream, client: 103.67.191.14, server: epn.siberry.fr, request: "GET / HTTP/1.1", upstream: "http://172.19.0.5:3000/", host: "51.77.210.51:80" 2019/10/03 13:17:24 [error] 6#6: *1770 connect() failed (111: Connection refused) while connecting to upstream, client: 82.98.51.51, server: epn.siberry.fr, request: "GET /cloud HTTP/1.1", upstream: "http://172.19.0.5:3000/cloud", host: "epn.siberry.fr" 2019/10/03 13:17:25 [error] 6#6: *1770 connect() failed (111: Connection refused) while connecting to upstream, client: 82.98.51.51, server: epn.siberry.fr, request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.19.0.5:3000/favicon.ico", host: "epn.siberry.fr" 2019/10/03 13:17:25 [error] 6#6: *1773 connect() failed (111: Connection refused) while connecting to upstream, client: 82.98.51.51, server: epn.siberry.fr, request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.19.0.5:3000/favicon.ico", host: "epn.siberry.fr" 2019/10/03 13:17:29 [error] 6#6: *1770 connect() failed (111: Connection refused) while connecting to upstream, client: 82.98.51.51, server: epn.siberry.fr, request: "GET /nuage HTTP/1.1", upstream: "http://172.19.0.5:3000/nuage", host: "epn.siberry.fr" 2019/10/03 13:18:30 [error] 6#6: *1777 connect() failed (111: Connection refused) while connecting to upstream, client: 93.174.93.178, server: epn.siberry.fr, request: "POST /editBlackAndWhiteList HTTP/1.1", upstream: "http://172.19.0.5:3000/editBlackAndWhiteList", host: "51.77.210.51"
std-err.log (j’ai des log.1->9 )
ths@vps731349:/apps/fabmanager$ tail -n 30 log/app-stderr.log from /usr/local/lib/ruby/2.3.0/tsort.rb:226:in tsort_each’
from /usr/local/lib/ruby/2.3.0/tsort.rb:205:in tsort_each' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/initializable.rb:54:in run_initializers’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/application.rb:352:in initialize!' from /usr/src/app/config/environment.rb:5:in <top (required)>’
from /usr/local/bundle/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in require' from /usr/local/bundle/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in block in require’
from /usr/local/bundle/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:240:in load_dependency' from /usr/local/bundle/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in require’
from /usr/src/app/config.ru:3:in block in <main>' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/builder.rb:55:in instance_eval’
from /usr/local/bundle/gems/rack-1.6.11/lib/rack/builder.rb:55:in initialize' from /usr/src/app/config.ru:in new’
from /usr/src/app/config.ru:in <main>' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/builder.rb:49:in eval’
from /usr/local/bundle/gems/rack-1.6.11/lib/rack/builder.rb:49:in new_from_string' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/builder.rb:40:in parse_file’
from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:300:in build_app_and_options_from_config' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:209:in app’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/server.rb:61:in app' from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:337:in wrapped_app’
from /usr/local/bundle/gems/rack-1.6.11/lib/rack/server.rb:273:in start' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/server.rb:80:in start’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:80:in block in server' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in tap’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:75:in server' from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands/commands_tasks.rb:39:in run_command!’
from /usr/local/bundle/gems/railties-4.2.11.1/lib/rails/commands.rb:17:in <top (required)>' from bin/rails:4:in require’
from bin/rails:4:in <main>

stdout
ths@vps731349:/apps/fabmanager$ tail -n 30 log/app-stdout.log => Booting Puma => Rails 4.2.11.1 application starting in production on http://0.0.0.0:3000 => Run rails server -hfor more startup options => Ctrl-C to shutdown server AuthProvider Load (0.4ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (1.7ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.3ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (4.2ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (4.7ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] Exiting => Booting Puma => Rails 4.2.11.1 application starting in production on http://0.0.0.0:3000 => Runrails server -hfor more startup options => Ctrl-C to shutdown server AuthProvider Load (0.4ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.5ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.4ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (1.9ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.5ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] Exiting => Booting Puma => Rails 4.2.11.1 application starting in production on http://0.0.0.0:3000 => Runrails server -hfor more startup options => Ctrl-C to shutdown server AuthProvider Load (0.6ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.5ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.3ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (5.5ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] AuthProvider Load (0.5ms) SELECT "auth_providers".* FROM "auth_providers" WHERE "auth_providers"."status" = $1 LIMIT 1 [["status", "active"]] Exiting

Sylvain · Octobre 7, 2019, 8:11

Tu peux mettre le fichier entier std-err.log ? Met le peut-être dans un pastebin car ça risque d’être gros