java.net.ConnectException: Connection refused: /127.0.0.1:12900 to http://127.0.0.1:12900/system/cluster/node about graylog2-images HOT 7 CLOSED

The most common problem is that Elasticsearch is not running properly and as a side effect Graylog server can not start. That's why nothing is listening on port 12900. Did you make sure to give enough memory to the host system? You need 3-4 Gig to run all components.

from graylog2-images.

@mariussturm thanks for your reply. I was thinking it might be caused by the low memory, it was 3.75G. But I didn't get any error log related with this. I tried with another server with 7.5G memory, still failed with same error. If there is no other possible reasons, will try this again tomorrow. Though I have tried many times already... I tried to start the server container and web interface container separately, this time, I can find the 12900 port listening, but the web interface still failed to connect with the graylog server.

from graylog2-images.

Odd, tried with Centos 6 and everything went smoothly.

from graylog2-images.

I am using Amazon EC2, will this be different? Thanks. I can not use the amazon ami, as I didn't find any in ap-northeast zone

from graylog2-images.

Amazon machines are sometimes kind of slow. This can produce more problems than running Graylog on your own hardware. Maybe you can double check the Docker image with a local host e.g. boot2docker machine?

from graylog2-images.

Just tried on Mac OS with boot2docker, succeeded and can access with {boot2docker ip}:9000, though I still saw error once:

Connection refused: /127.0.0.1:12900 to http://127.0.0.1:12900/system/cluster/node

But it's a successful start, as you mentioned that amazon is slow, so I should configure graylog by myself without using docker and ami? Thank you.

from graylog2-images.

Yes, I think Docker on a AWS machine is the problem here. Please follow one of our normal install routines!

from graylog2-images.