502 Bad Gateways - nginx upstream error about malcolm HOT 2 CLOSED

The nginx.conf file is inside the nginx container.

Usually, though, the issue with 502 errors is that one or more containers failed to start completely. If you run docker ps -a you should see a list of the docker containers of Malcolm. If any of them have Exited for the status rather than running, then those containers won't be available for nginx to proxy the connections to. In that case, run docker-compose logs xxxxxx and find the output of the container that exited prematurely.

It could be a resources issue: how much memory does the system have? How much have you allocated for Malcolm? You can run ./scripts/install.py -c to reconfigure the docker-compose.yml parameters dealing with memory allocation, for Elasticsearch and Logstash in particular. You should also run ./scripts/wipe.sh to reset everything to a clean state afterwards.

from malcolm.

The nginx.conf file is inside the nginx container.

Usually, though, the issue with 502 errors is that one or more containers failed to start completely. If you run docker ps -a you should see a list of the docker containers of Malcolm. If any of them have Exited for the status rather than running, then those containers won't be available for nginx to proxy the connections to. In that case, run docker-compose logs xxxxxx and find the output of the container that exited prematurely.

It could be a resources issue: how much memory does the system have? How much have you allocated for Malcolm? You can run ./scripts/install.py -c to reconfigure the docker-compose.yml parameters dealing with memory allocation, for Elasticsearch and Logstash in particular. You should also run ./scripts/wipe.sh to reset everything to a clean state afterwards.

Hey there,

Thanks for the reply. Looks like I was being a complete idiot and only assigning the box 4gb RAM and configuring it to need 6.5gb. Sorry for the time waste!

Cheers

from malcolm.