Hello,
1st I just updated to Graylog 3.3, and so far I am really enjoying the new interface. I am attempting to use a Cerebro container to gain insight to the Elasticsearch container. My ES container does not have ANY exposed ports, however graylog is still getting the data into ES. I have installed the Cerebro container, and I am not able to connect to http://localhost:9200. I exposed port 9200 in my ES container, and still not able to connect. Thoughts to what I need to change?
Thank you
Note that I am not on the docker host when trying to access the node via cerebro, I am on another host on the network and accessing the cerebro web gui from there. If in the cerebro web gui I try to access th node via http://10.10.100.25:922 (vs http://localhost:9200) I do not get a connection error, I get a spinning white wheel that says connecting.
he @brohan
as you do not shared your configuration I can only give you some general answer:
Cerebro does not work as server application that connects to your ES and serves that as web page. AFAIK it runs a browser application. This (your) browser need the ability to connect to the Elasticsearch servers direct.
I could be wrong but that is how I remember this works.
Thank you for your reply. I did open port 9200 on ES, and, when visiting it in a web browser, can get a response (this is on the Docker host). When I enter the same host address (10.10.100.25:9200) in the Cerebro webpage it has the spinning wheel and say connection, but never does (vs localhost:9200 which immediately says it can’t connect).
is your docker host also your local computer where your browser runs?
No it is not. My Docker host is Ubuntu server with no GUI. To access the ES port I must use the host address:9200 and not localhost:9200. Likewise in the Cerebro GUI localhost:9200 fails (as the localhost is the container I presume) but xx.xx.xxx.25:9200 will say that it is connecting, but never does. A redirect issue in the Cerebro container?
I do not know cerebro enough for that … but I guess you would need your address:9200 to connect from your browser to elasticsearch.
Which I can do from another machine on the network and I do see the ES response:
{
“name” : “pTz4sEl”,
“cluster_name” : “docker-cluster”,
“cluster_uuid” : “k3TRjgcySB-kFkDNtkB9Hg”,
“version” : {
“number” : “6.8.8”,
“build_flavor” : “oss”,
“build_type” : “docker”,
“build_hash” : “2f4c224”,
“build_date” : “2020-03-18T23:22:18.622755Z”,
“build_snapshot” : false,
“lucene_version” : “7.7.2”,
“minimum_wire_compatibility_version” : “5.6.0”,
“minimum_index_compatibility_version” : “5.0.0”
},
“tagline” : “You Know, for Search”
}
For some reason Cerebro isn’t able to do what it needs with that port exposed. I’m thinking that it may be an issue with the Cerebro container and how the connection is mapped.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
