502 Bad Gateway nginx after restart server

Issues during installation and related to database
BranKo
Posts: 13
Joined: Fri Jan 13, 2017 1:07 pm

Re: 502 Bad Gateway nginx after restart server

Post by BranKo » Wed Mar 22, 2017 10:01 am

Hello I tried the same - document server on Xenial (16.04) but after restart I get only 502 bad gateway.
I have three indipendent servers with same failure.

But kernel on Xenial is not in support list http://onlyo.co/1PABPEI

If I tried the same config (with little change I use nodejs v7) on Trusty (14.04) after restart - everything was OK.
I don't think that kernel is the bloblem, it was changeg a lot of packages.

vicatus
Posts: 1
Joined: Sat Feb 08, 2020 10:08 am

Re: 502 Bad Gateway nginx after restart server

Post by vicatus » Sat Feb 08, 2020 10:24 am

First apologize my English, but this is a machine translation.

My configuration: Server yunohost Core I5, 8 GB of ram. HDD 500 GB. Debian 4.9.189-3 + deb9u2 (2019-11-11) x86_64 GNU / Linux

For my part the error was related to the fact that the rabbitmq-server did not start after the reboot.

To check :

Code: Select all

sudo service --status-all
and

Code: Select all

sudo systemctl status rabbitmq-server
I got this answer :

Code: Select all

rabbitmq-server.service - RabbitMQ Messaging Server
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
   Active: [b][i]failed [/i][/b](Result: timeout) since Sat 2020-02-08 10:48:21 CET; 17min ago
 Main PID: 533 (code = killed, signal = TERM)
      CPU: 3.268s
If this is the case for you too, simply relaunch the rabbitmq-server:

Code: Select all

sudo systemctl start rabbitmq-server

I hope it can be useful.
What I don't know is how to make the rabbitmq-server start automatically after a reboot of my yunohost server.

Post Reply