Bonjour,

Je fais face à un problème récurrent sur 2 des mes machines virtuelles, je suis complètement coincé...

Les VMs concernées sont toutes les deux sur debian stretch et utilisent nginx en tant que reverse proxy

Aléatoirement dans la journée les Vm crashent complètement et je suis obligé de redémarrer "électriquement" la VM plantée.

Je possède un parc d'environ 40 VM, toutes sur Debian avec différents services installés qui ne rencontrent aucun problème, les 2 seules qui me posent soucis sont celles avec nginx. Le soucis doit venir de là mais je sèche...

Niveau log je ne sais pas trop où regarder hormis dans les logs nginx et voici ce qui est remonté c'est assez maigre

2019/05/14 09:56:04 [error] 615#615: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195.200.179.114, server: mondomaine.com, request: "GET /sockjs/info?cb=vi2l4tg77c HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=vi2l4tg77c", host: "mondomaine.com", referrer: "https://mondomaine.com/home"
2019/05/14 09:56:04 [error] 615#615: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 89.80.68.149, server: mondomaine.com, request: "GET /sockjs/info?cb=qbnpqbdc1d HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=qbnpqbdc1d", host: "mondomaine.com", referrer: "https://mondomaine.com/home"
2019/05/14 09:56:08 [error] 615#615: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 89.80.68.149, server: mondomaine.com, request: "GET /sockjs/info?cb=gb_ks__h1d HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=gb_ks__h1d", host: "mondomaine.com", referrer: "https://mondomaine.com/home"
2019/05/14 09:56:08 [error] 615#615: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195.200.179.114, server: mondomaine.com, request: "GET /sockjs/info?cb=_osdc4ylfk HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=_osdc4ylfk", host: "mondomaine.com", referrer: "https://mondomaine.com/home"
2019/05/14 09:56:18 [error] 615#615: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195.200.179.114, server: mondomaine.com, request: "GET /sockjs/info?cb=8r5bifv0hm HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=8r5bifv0hm", host: "mondomaine.com", referrer: "https://mondomaine.com/home"
2019/05/14 09:56:21 [error] 615#615: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 89.80.68.149, server: mondomaine.com, request: "GET /sockjs/info?cb=yn_mpyf9ha HTTP/1.1", upstream: "http://127.0.0.1:3000/sockjs/info?cb=yn_mpyf9ha", host: "mondomaine.com", referrer: "https://mondomaine.com/home"

Et ici mon fichier de configuration dans "sites-avalaibles"

server {
    listen 127.0.0.1;
    server_name mondomaine.com;

    location / {
        proxy_pass http://127.0.0.1:3000/;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/mondomaine.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/mondomaine.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    proxy_set_header Upgrade $http_upgrade; # to allow websockets obligatoire pour que applis IOS Android fonctionnennt
    proxy_set_header Connection upgrade;#Obligatoire pour que applis fonctionnent

}
server {
    if ($host = mondomaine.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;

    server_name mondomaine.com;
    return 404; # managed by Certbot


}

Si quelqu'un a une piste je suis preneur, merci d'avance!

-
Edité par alex504 14 mai 2019 à 10:30:55

Bonjour,

Il faudrait que tu regardes tes logs systèmes (commandes dmesg et journalctl) après le crash.

-
Edité par Anonyme 14 mai 2019 à 13:11:10

Bonjour,

Je vais jeter un oeil par là au prochain crash

Bonjour,

Crash de ma VM dimanche, ci dessous ce qui est remonté (lié à NGINX)

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

Faut voir tout les autres logs aussi. Surtout que là le service semble ne plus pouvoir binder les ports 80/443. Après le crash, regarde quel service écoute sur le port 80 et 443.

Rien de bien probant dans les logs malheureusement...

Dans les logs error de NGinx j'ai ça par contre 

2019/05/22 17:40:26 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

2019/05/22 17:40:26 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

2019/05/22 17:40:26 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

2019/05/22 17:40:26 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

2019/05/22 17:40:27 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

2019/05/22 17:40:28 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

2019/05/22 17:40:29 [error] 653#653: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 195$

On peut voir la config nginx ?

Bonjour,

Toujours aucune explication sur ces crashs en boucle ça me rend fou

Pour le nginx.conf ça donne ça 

user www-data;
worker_processes 2;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
	worker_connections 2048;
	# multi_accept on;
}

http {

	##
	# Basic Settings
	##
       
	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;
	keepalive_timeout 65;
	types_hash_max_size 2048;
	# server_tokens off;

	# server_names_hash_bucket_size 64;
	# server_name_in_redirect off;

	include /etc/nginx/mime.types;
	default_type application/octet-stream;

	##
	# SSL Settings
	##

	ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
	ssl_prefer_server_ciphers on;

	##
	# Logging Settings
	##

	access_log /var/log/nginx/access.log;
	error_log /var/log/nginx/error.log;

	##
	# Gzip Settings
	##

	gzip on;
	gzip_disable "msie6";

	# gzip_vary on;
	# gzip_proxied any;
	# gzip_comp_level 6;
	# gzip_buffers 16 8k;
	# gzip_http_version 1.1;
	# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

	##
	# Virtual Host Configs
	##

	include /etc/nginx/conf.d/*.conf;
	include /etc/nginx/sites-enabled/*;
}


#mail {
#	# See sample authentication script at:
#	# http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
# 
#	# auth_http localhost/auth.php;
#	# pop3_capabilities "TOP" "USER";
#	# imap_capabilities "IMAP4rev1" "UIDPLUS";
# 
#	server {
#		listen     localhost:110;
#		protocol   pop3;
#		proxy      on;
#	}
# 
#	server {
#		listen     localhost:143;
#		protocol   imap;
#		proxy      on;
#	}
#}