WebGUI, 502 Bad Gateway

axlf · Oct 25th 2017, 8:53pm

Hallo,

oh weh — ich hab meine WebGUI kaputt gespielt. Wollte auf dem Server noch zusätzlich ein Letsencrypt & PHP7 installieren, und jetzt läuft die GUI nicht mehr

Die angezeigte "502 - Bad Gateway" Seite ist aber immerhin SSL gesichert

Der Dienst läuft wohl, nur stimmt was mit Nginx nicht oder so...

Source Code

# service bloonix-webgui status
● bloonix-webgui.service - Bloonix WebGUI
Loaded: loaded (/lib/systemd/system/bloonix-webgui.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-10-25 21:38:27 CEST; 6min ago
Process: 3535 ExecStop=/bin/kill -15 $MAINPID (code=exited, status=0/SUCCESS)
Process: 3552 ExecStart=/srv/bloonix/webgui/scripts/bloonix-webgui --pid-file /var/run/bloonix/bloonix-webgui.pid --config-file /etc/bloonix/webgui/main.conf (code=exited, status=0/SUCCESS)
Process: 3540 ExecStartPre=/usr/lib/bloonix/bin/bloonix-pre-start /var/lib/bloonix /var/lib/bloonix/ipc /var/lib/bloonix/webgui /var/log/bloonix /var/run/bloonix (code=exited, status=0/SUCCESS)
Main PID: 3555 (bloonix-webgui)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bloonix-webgui.service
└─3555 /usr/bin/perl /srv/bloonix/webgui/scripts/bloonix-webgui --pid-file /var/run/bloonix/bloonix-webgui.pid --config-file /etc/bloonix/webgui/main.conf

Display All

Hier die /etc/bloonix/webgui/nginx.conf

Source Code

server {
listen 80 default_server;
server_name _;
location ^~ /.well-known {
alias /var/www/acme-challenges/.well-known;
}
return 301 https://$host$request_uri;
}
server {
listen 443 default_server;
server_name _;
access_log /var/log/nginx/bloonix-webgui.access.log;
error_log /var/log/nginx/bloonix-webgui.error.log;
location ^~ /.well-known {
alias /var/www/acme-challenges/.well-known;
}
location ~ /public {
root /srv/bloonix/webgui;
}
location /favicon.ico {
root /srv/bloonix/webgui/public/img;
}
location / {
expires off;
include /etc/nginx/fastcgi_params;
root /srv/bloonix/webgui/public;
fastcgi_pass 127.0.0.1:9000;
}
ssl on;
ssl_protocols TLSv1.2;
ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256';
ssl_prefer_server_ciphers on;
ssl_certificate /etc/letsencrypt/live/BLOONIXDOMAIN/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/BLOONIXDOMAIN/privkey.pem;
}

Display All

Dann noch netstat:

Source Code

# netstat -tulpe
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 localhost:submission 0.0.0.0:* LISTEN root 13172 676/sendmail: MTA:
tcp 0 0 0.0.0.0:http 0.0.0.0:* LISTEN root 8522193 3402/nginx: master
tcp 0 0 0.0.0.0:5460 0.0.0.0:* LISTEN bloonix 1807230 709/perl
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN root 12671 405/sshd
tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN root 13171 676/sendmail: MTA:
tcp 0 0 0.0.0.0:https 0.0.0.0:* LISTEN root 8522194 3402/nginx: master
tcp6 0 0 [::]:mysql [::]:* LISTEN mysql 7556936 14109/mysqld
tcp6 0 0 [::]:ssh [::]:* LISTEN root 12673 405/sshd
udp 0 0 BLOONIXIP.vultr:ntp 0.0.0.0:* root 13895 742/ntpd
udp 0 0 localhost:ntp 0.0.0.0:* root 13893 742/ntpd
udp 0 0 0.0.0.0:ntp 0.0.0.0:* root 13889 742/ntpd
udp 0 0 0.0.0.0:bootpc 0.0.0.0:* root 10712 394/dhclient
udp6 0 0 fe80::5400:1ff:fe38:ntp [::]:* root 13899 742/ntpd
udp6 0 0 localhost:ntp [::]:* root 13897 742/ntpd
udp6 0 0 [::]:ntp [::]:* root 13886 742/ntpd

Display All

Hat jemand eine Idee?

Danke

nunuika · Oct 26th 2017, 7:55am

Hatte ich auch, bei mir war das Problem das ich das LE SSL aus der Bloonix Server.conf wieder austragen musste, danach ging es und der 502 war weg...

Du hast vermutlich die Anleitung von Dominik genutzt...

axlf · Oct 26th 2017, 8:12am

Genau

Gut... ich probiers gleich mal...

axlf · Oct 26th 2017, 8:17am

Hm. Also ich hab die Server.conf wieder auf Originalzustand gesetzt, sehe aber immer noch den 502.

Im bloonix-webgui.error.log steht nur folgendes:

Source Code

2017/10/26 09:13:31 [error] 838#838: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 188.195.131.58, server: _, request: "GET / HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "BLOONIXDOMAIN"

Andere Anwendungen (wie z.B. eine PHP Seite) funktionieren.

nunuika · Oct 26th 2017, 9:12am

Alles restartet nach der Änderung?

axlf · Oct 26th 2017, 9:16am

Ja — habe auch nochmal den Server neugestartet. Keine Änderung...

nunuika · Oct 26th 2017, 9:31am

Also meine conf sieht so aus

Source Code

server {
listen 80 ;
server_name meinedomain.de;
location ^~ /.well-known {
alias /var/www/acme-challenges/.well-known;
}
return 301 https://$host$request_uri;
}
server {
listen 443 default_server;
server_name meinedomain.de;
access_log /var/log/nginx/bloonix-webgui.access.log;
error_log /var/log/nginx/bloonix-webgui.error.log;
location ^~ /.well-known {
alias /var/www/acme-challenges/.well-known;
}
location ~ /public {
root /srv/bloonix/webgui;
}
location /favicon.ico {
root /srv/bloonix/webgui/public/img;
}
location / {
expires off;
include /etc/nginx/fastcgi_params;
root /srv/bloonix/webgui/public;
fastcgi_pass 127.0.0.1:9000;
}
ssl on;
ssl_certificate /etc/letsencrypt/live/meinedomain.de/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/meinedomain.de/privkey.pem;
}

Display All

axlf · Oct 26th 2017, 9:33am

Könntest du mir mal dein `netstat -tulpe` zeigen?

nunuika · Oct 26th 2017, 9:36am

Source Code

Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name
tcp 0 0 0.0.0.0:http 0.0.0.0:* LISTEN root 16868 1175/nginx: master
tcp 0 0 0.0.0.0:5460 0.0.0.0:* LISTEN bloonix 76951 3258/perl
tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN root 14007 953/sendmail: MTA:
tcp 0 0 0.0.0.0:https 0.0.0.0:* LISTEN root 16869 1175/nginx: master
tcp 0 0 0.0.0.0: 0.0.0.0:* LISTEN root 471523 13411/sshd
tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN bloonix 17030 1065/perl
tcp 0 0 localhost:mysql 0.0.0.0:* LISTEN mysql 14127 952/mysqld
tcp 0 0 localhost:submission 0.0.0.0:* LISTEN root 14008 953/sendmail: MTA:
tcp6 0 0 localhost:9200 [::]:* LISTEN elasticsearch 16970 1139/java
tcp6 0 0 [::]:http [::]:* LISTEN root 16870 1175/nginx: master
tcp6 0 0 localhost:9300 [::]:* LISTEN elasticsearch 16914 1139/java
tcp6 0 0 [::]: [::]:* LISTEN root 471532 13411/sshd
udp 0 0 0.0.0.0:bootpc 0.0.0.0:* root 11623 650/dhclient

Display All

axlf · Oct 26th 2017, 9:39am

Danke.

Ich bin kein nginx oder perl Experte.

Aber nachdem in meiner nginx.conf

Source Code

fastcgi_pass 127.0.0.1:9000;

steht,

aber auf einem System kein Prozess an Port 9000 lauscht, könnte das der Grund sein.

Bei dir ist der Prozess perl vom Benutzer bloonix auf Port 9000

axlf · Oct 26th 2017, 9:43am

Sehr seltsam.

Source Code

# service bloonix-server status
● bloonix-server.service - Bloonix Server
Loaded: loaded (/lib/systemd/system/bloonix-server.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2017-10-26 10:13:43 CEST; 27min ago
Process: 481 ExecStart=/usr/bin/bloonix-server --pid-file /var/run/bloonix/bloonix-server.pid --config-file /etc/bloonix/server/main.conf (code=exited, status=0/SUCCESS)
Process: 392 ExecStartPre=/usr/lib/bloonix/bin/bloonix-pre-start /var/lib/bloonix /var/lib/bloonix/ipc /var/lib/bloonix/server /var/log/bloonix /var/run/bloonix (code=exited, status=0/SUCCESS)
Main PID: 722 (bloonix-server)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bloonix-server.service
└─722 /usr/bin/perl /usr/bin/bloonix-server --pid-file /var/run/bloonix/bloonix-server.pid --config-file /etc/bloonix/server/main.conf
Oct 26 10:13:41 BLOONIXDOMAIN systemd[1]: Starting Bloonix Server...
Oct 26 10:13:43 BLOONIXDOMAIN systemd[1]: Started Bloonix Server.

Display All

und

Source Code

# service bloonix-webgui status
● bloonix-webgui.service - Bloonix WebGUI
Loaded: loaded (/lib/systemd/system/bloonix-webgui.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2017-10-26 10:13:42 CEST; 26min ago
Process: 483 ExecStart=/srv/bloonix/webgui/scripts/bloonix-webgui --pid-file /var/run/bloonix/bloonix-webgui.pid --config-file /etc/bloonix/webgui/main.conf (code=exited, status=0/SUCCESS)
Process: 400 ExecStartPre=/usr/lib/bloonix/bin/bloonix-pre-start /var/lib/bloonix /var/lib/bloonix/ipc /var/lib/bloonix/webgui /var/log/bloonix /var/run/bloonix (code=exited, status=0/SUCCESS)
Main PID: 677 (bloonix-webgui)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bloonix-webgui.service
└─677 /usr/bin/perl /srv/bloonix/webgui/scripts/bloonix-webgui --pid-file /var/run/bloonix/bloonix-webgui.pid --config-file /etc/bloonix/webgui/main.conf
Oct 26 10:13:41 BLOONIXDOMAIN systemd[1]: Starting Bloonix WebGUI...
Oct 26 10:13:42 BLOONIXDOMAIN systemd[1]: Started Bloonix WebGUI.

Display All

Die Dienste laufen ja irgendwie — aber keine offenen Ports.

LukiTJ · Oct 26th 2017, 5:21pm

Source Code

location ^~ /.well-known {
alias /var/www/acme-challenges/.well-known;
}

Schmeiß mal den Kram in beiden Server Sektionen aus der config und lösch dein Browser Cache.

axlf · Oct 26th 2017, 8:43pm

Keine Änderung. Ich vermute wirklich dass Bloonix keinen Port aufmacht. Nginx dient ja nur als Proxy, der die Anfrage zum Bloonix Dienst weiterleiten sollte. Aber wenn Bloonix nicht lauscht, gibt es diesen Fehler.

Ich weiß jetzt aber nicht, warum die Dienste nicht lauschen wollen

NevaKee · Oct 26th 2017, 8:53pm

Was steht denn bei Dir in der /etc/bloonix/webgui/main.conf drin?
Was sagen die Logdateien von der Webgui? /var/log/bloonix/bloonix-webgui.log

axlf · Oct 26th 2017, 8:59pm

/etc/bloonix/webgui/main.conf

Source Code

heaven {
base /srv/bloonix/webgui/lib
model Database, REST
view Template, JSON
}
system {
user bloonix
group bloonix
timezone Europe/Berlin
}
proc_manager {
max_servers 10
min_spare_servers 5
max_spare_servers 8
}
fcgi_server {
port 9000
}
server_status {
enabled yes
allow_from 127.0.0.1
}
webapp {
sid_expire_time 3600
sid_refresh_time 300
chart_library other
html_path /srv/bloonix/webgui/templates/html
check_frequency low
allow_simple_usernames no
enable_user_tracking no
}
email {
sendmail /usr/sbin/sendmail -t -oi -oem
from root@localhost
to root@localhost
subject [BLOONIX-WEBGUI] %s
flags success-login, failed-login, password-request
}
database {
include /etc/bloonix/database/main.conf
logger {
file {
filename /var/log/bloonix/bloonix-webgui-database.log
filelock 0
maxlevel info
minlevel emerg
message_layout [%T] %L %P %t %X %Y %m (%C)
}
}
}
elasticsearch {
proto http
host 127.0.0.1:9200, 127.0.0.2:9200
timeout 60
mode balanced
}
template {
path /srv/bloonix/webgui/templates
}
logger {
file {
filename /var/log/bloonix/bloonix-webgui.log
filelock 0
maxlevel info
minlevel emerg
timeformat %b %d %Y %H:%M:%S
message_layout [%T] %L %P %t %X %Y %m (%C)
}
}

Display All

Im Log steht ziemlich oft das hier

Source Code

[Oct 26 2017 09:33:35] INFO 676 0.000263 n/a n/a rest: request 'http://127.0.0.2:9200/ (/usr/share/perl5/Bloonix/REST.pm, line 225)
[Oct 26 2017 09:33:35] ERROR 676 0.000281 n/a n/a rest: request failed to 'http://127.0.0.2:9200/': [599 Internal Exception], message: [Could not connect to '127.0.0.2:9200': Connection refused
] (/usr/share/perl5/Bloonix/REST.pm, line 319)
CALL(13): package(main) filename(/srv/bloonix/webgui/scripts/bloonix-webgui) line(11) subroutine(Bloonix::Heaven::run) hasargs(1)
CALL(12): package(Bloonix::Heaven) filename(/usr/share/perl5/Bloonix/Heaven.pm) line(40) subroutine(Bloonix::Heaven::__init) hasargs(1)
CALL(11): package(Bloonix::Heaven) filename(/usr/share/perl5/Bloonix/Heaven.pm) line(107) subroutine((eval)) hasargs(0)
CALL(10): package(Bloonix::Heaven) filename(/usr/share/perl5/Bloonix/Heaven.pm) line(115) subroutine(Bloonix::Heaven::__load_model) hasargs(1)
CALL(9): package(Bloonix::Heaven) filename(/usr/share/perl5/Bloonix/Heaven.pm) line(326) subroutine(Bloonix::Heaven::Model::load) hasargs(1)
CALL(8): package(Bloonix::Heaven::Model) filename(/usr/share/perl5/Bloonix/Heaven/Model.pm) line(56) subroutine(Bloonix::Model::REST::new) hasargs(1) wantarray()
CALL(7): package(Bloonix::Model::REST) filename(/srv/bloonix/webgui/lib/Bloonix/Model/REST.pm) line(23) subroutine((eval)) hasargs(0)
CALL(6): package(Bloonix::Model::REST) filename(/srv/bloonix/webgui/lib/Bloonix/Model/REST.pm) line(24) subroutine(Bloonix::REST::get) hasargs(1) wantarray()
CALL(5): package(Bloonix::REST) filename(/usr/share/perl5/Bloonix/REST.pm) line(182) subroutine(Bloonix::REST::request) hasargs(1) wantarray()
CALL(4): package(Bloonix::REST) filename(/usr/share/perl5/Bloonix/REST.pm) line(251) subroutine(Bloonix::REST::errstr) hasargs(1)
CALL(3): package(Bloonix::REST) filename(/usr/share/perl5/Bloonix/REST.pm) line(319) subroutine(Log::Handler::Levels::trace) hasargs(1)
CALL(2): package(Log::Handler::Levels) filename(/usr/share/perl5/Log/Handler/Levels.pm) line(271) subroutine(Log::Handler::Levels::__ANON__) hasargs(1)
CALL(1): package(Log::Handler::Levels) filename(/usr/share/perl5/Log/Handler/Levels.pm) line(227) subroutine(Log::Handler::Output::log) hasargs(1) wantarray()
CALL(0): package(Log::Handler::Output) filename(/usr/share/perl5/Log/Handler/Output.pm) line(87) subroutine(Log::Handler::Output::_add_trace) hasargs(1)

Display All

NevaKee · Oct 26th 2017, 9:04pm

Läuft bei Dir elasticsearch?

Vielleicht hat Dein Server Probleme mit der IP 127.0.0.2.
Kannst Du teilweise im elasticsearch Teil den Host 127.0.0.2:9200 rausnehmen?

axlf · Oct 26th 2017, 9:07pm

Boah... Ne. Der lief nicht.
Elasticsearch Gestartet, WebGUI neugestartet und jetzt geht es wieder...

Hm. Wär aber interessant wieso nicht. Sollten die ganzen Dienste bei einem Server-Neustart nicht auch mitstarten?

NevaKee · Oct 26th 2017, 9:14pm

Was sagt systemctl status elasticsearch?

axlf · Oct 26th 2017, 9:32pm

# systemctl status elasticsearch

Source Code

● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2017-10-26 22:05:03 CEST; 26min ago
Docs: http://www.elastic.co
Process: 23163 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 23166 (java)
Tasks: 40 (limit: 4915)
CGroup: /system.slice/elasticsearch.service
└─23166 /usr/bin/java -Xms256m -Xmx1g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOf
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at org.elasticsearch.action.search.AbstractSearchAsyncAction$1.onFailure(AbstractSearchAsyncAction.java:152)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:46)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:874)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at org.elasticsearch.transport.TransportService$DirectResponseChannel.sendResponse(TransportService.java:852)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at org.elasticsearch.transport.TransportService$4.onFailure(TransportService.java:389)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:39)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Oct 26 22:05:18 BLOONIXDOMAIN elasticsearch[23166]: at java.lang.Thread.run(Thread.java:748)
Oct 26 22:05:26 BLOONIXDOMAIN elasticsearch[23166]: [2017-10-26 22:05:26,238][INFO ][cluster.routing.allocation] [Black Dragon] Cluster health status changed from [RED] to [YELLOW] (reason: [shards st
lines 1-20/20 (END)

Display All

NevaKee · Oct 26th 2017, 9:44pm

Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)

Wird also nicht automatisch gestartet.

systemctl enable elasticsearch

WebGUI, 502 Bad Gateway

WebGUI, 502 Bad Gateway

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Source Code

Share

Users Online 4

Similar Threads